this post was submitted on 26 Aug 2023
20 points (100.0% liked)

Beehaw Support

2796 readers
1 users here now

Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.

A brief FAQ for lurkers and new users can be found here.

Our September 2024 financial update is here.

For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.


if you can see this, it's up  

founded 2 years ago
MODERATORS
 

I just noticed my private instance, https://derp.foo/, was recently defederated by Beehaw. Thing is, I have no idea why. Was my instance accidentally included in some bulk defederation to get rid of spammers, or is there something specific to my instance?

all 15 comments
sorted by: hot top controversial new old
[–] LinkOpensChest_wav@beehaw.org 19 points 1 year ago

It doesn't look like your instance is defederated from beehaw

sent from my beehaw™ account

[–] Penguincoder@beehaw.org 14 points 1 year ago

Hey there, can you reach out to me on matrix? @penguincoder:hive.beehaw.org

[–] Lojcs@lemm.ee 10 points 1 year ago (1 children)

If they defederated your instance pretty sure this post won't reach them. Try making a post from another instance

[–] irdc@lemm.ee 25 points 1 year ago (1 children)

I'm posting from https://lemm.ee/, I simply set my display name to 'irdc@derp.foo'.

[–] Lojcs@lemm.ee 7 points 1 year ago (2 children)

Huh, it's impossible to tell from jerboa

[–] PlantJam@beehaw.org 6 points 1 year ago* (last edited 1 year ago)

Tap the username to see "irdc@derp.foo@lemm.ee".

[–] LinkOpensChest_wav@beehaw.org 3 points 1 year ago (1 children)

That tripped me out on jerboa too. I just clicked on their username, and then I could see that it's a lemm.ee account

[–] Lojcs@lemm.ee 2 points 1 year ago (1 children)

That doesn't work if you're from lemm.ee as well

[–] LinkOpensChest_wav@beehaw.org 1 points 1 year ago

True, I didn't think of that

[–] Seathru@beehaw.org 3 points 1 year ago (2 children)

Not blocked for me. https://beehaw.org/c/hackernews@derp.foo works just fine. And it wouldn't if it were defederated.

[–] MentalEdge@sopuli.xyz 20 points 1 year ago (2 children)

That's not the case. For viewing/posting to communities and messaging users to "stop working" they have to be "purged" as well as defederated.

You can still message a user or post to a community from a formerly federated instance. But those interactions will never make it off-instance. The message won't get delivered, and your post will only be seen when viewing the community from your instance. But you can do those things.

After defederation, content stops syncing, but without additional action (a purge), nothing else happens. The user profiles, communities and even local functionality, remains.

[–] Seathru@beehaw.org 5 points 1 year ago

Thanks for explaining that. I’ve been using links like the above to test if one instance is available from another rather than looking through the /instances list. I guess it’s a poor test (and probably not any less work than just checking the lists).

[–] irdc@lemm.ee 13 points 1 year ago

Indeed it does. However, comparing it to https://derp.foo/c/hackernews and sorting by new reveals that posts more recent than 5 days ago were never sync'ed. In addition, https://beehaw.org/instances shows derp.foo as blocked.

[–] DavidGarcia@feddit.nl 2 points 1 year ago

perhaps they started whitelisting?