big update, awful.systems is now a federated lemmy instance. let me know if anything looks broken! here’s what to expect:

  • to pull up an awful.systems community on another instance, just paste that community’s URL into the other instance’s search bar
  • federation with other lemmy instances should work, and probably kbin too? there’s no way I can find to pull in pre-federation posts on remote instances though, so send your friends here to read the backlogs
  • we can’t federate with most of mastodon right now because lemmy doesn’t implement authorized_fetch, which is a best practice setting for mastodon instances. if your instance doesn’t use it, try entering something like @sneerclub@awful.systems into your mastodon search; lemmy communities are represented to mastodon as users
  • this is pretty much an experimental thing so if we have to turn it off, I’ll send out another post
  • reply to this post with ideas for moderation tools and instances you’d like to see blocked (and a reason why) and we’ll take action on anything that sounds like a good idea

federation was made possible by

  • lemmy’s devs skipping their release process and not telling anyone 0.18.2 was released on friday? so we’re on 0.18.2 now
  • updating all of the deployment cluster’s flake inputs just in case
  • @dgerard@awful.systems shouting yolo
  • @selfOPMA
    link
    English
    311 months ago

    that’s as expected I think — lemmy most likely only pulls community data on demand instead of propagating it from one instance to another automatically. searching for another community by its full URL should (after a couple seconds) make our instance download that data, though I’m not sure if the data’s kept permanently if the remote community has no subscribers on our end