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
  • Madbrad200@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    I think kbin is a bit slower than lemmy-to-lemmy communication

    You can ignore the “subscription pending” message, for all intents and purposes you are subscribed. Consider it a UI quirk.

    • self@awful.systemsOPM
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      huh, I need to check back on it but I felt like the behavior we were seeing was severely broken:

      • on prod, it stayed on subscription pending and after waiting quite a while, we didn’t see anything come from kbin into our instance
      • on dev, subscribing succeeded right away (and showed joined after a UI refresh) and eventually it started receiving posts from kbin