Admin

Just for posts (in your user settings) not comments yet.

True, but if Meta (or anyone) wanted to "directly" get that data, it would be as trivial as setting up an instance on something as small as a Raspberry Pi and subscribing to a community here. We would have no way of knowing who it is or stopping them. Defederation is a tool to prevent brigading, not lurking.

If (if) Meta wanted to set a lemmy-style platform, preemptively defederating from it would be a largely symbolic gesture. Doesn't mean it's not worth doing, like I said we'll cross that bridge if and when it becomes relevant.

The "user data" (comments, posts, votes, etc) that would be available to a hypothetical instance owned my Meta is already public for anyone, so not much we have control over there. "Defederating" essentially just means "blanket banning" a bunch of users at once.

You are most welcome 🖖

That's a great point! Also I'm very happy to hear we were your entry into the "threadiverse". We'll look into some options.

We're aware of the pact and will cross that bridge when (or if) it ever really happens. We're certainly no fans of Meta (or Reddit,or Twitter). So far it seems more likely to affect Mastodon than Lemmy/Kbin.

I installed some community made themes (like darkspace) just to play around and give users some options, but yeeeah... none of them are very good. Thankfully the admin team knows a bit of CSS from their redditing days so a theme improvement is definitely on the to do list.

If anyone wants to have a go at making one, be my guest, I'd be happy to add it to the options.

You're most welcome!

True, but following the instance directly can be a bit of a firehose of information since you get ALL posts and comments. We wanted to have a place to alert for scheduled maintenance, events, and stuff like that.

Thanks for the update, you might want to try clearing your DNS. I'm a Firefox user as well and it's working fine.

The world just isn't ready for us yet.

We haven't been able to replicate this. Have tried this recently? Or is it an error from a few weeks ago? I ask because we had a brief issue that gave a similar error but has since been fixed.