Skip Navigation

Posts
37
Comments
68
Joined
3 yr. ago

  • Yep, all this ^^^

    This is also one of the reasons why I believe ActivityPub client-to-server failed and will likely never gain much traction. It either needs every single client to re-implement all the features it wants from scratch, or the entire ecosystem needs to be dumbed down to fit a single mold. Leave all the unique functionality in "uncommon" software like (streams) and friends, even software like Lemmy or PeerTube would likely be extremely difficult to build in a world where client-to-server actually became a thing.

    The only way I can see C2S actually taking off is as IPC protocol between an "app server" (which would be the equivalent of Mastodon or Lemmy or (streams)) and a "federation server" which is just a dumb pipe that distributes and receives objects and activities, and even that has it's fair share of concerns, both around efficiency and the same "dumbing down" problem.

  • most people on lemmy do not understand the tradeoffs both activitypub and it's implementors do, as evidenced by this exact community we're in. these memes wouldn't gain any traction even if they were funny to their intended audience (which i have doubts on if it's possible to do but idk i'm not creative enough)

  • id argue none of those are fun topics you can joke about but "memes as a form of outrage" (aside from, like, two) which is already a problem (see all the political memes on any of the meme communities for countless examples) we do not need to encourage imo

  • to be fair there isn't that much about the fedi in general that you can meme about. the closes you can get are in jokes but:

    a) lemmy doesnt have them because this place is uncreative and only serves as a dumping ground from memes from other places when they aren't bickering about politicsb) in jokes of different parts of fedi do not translate well just because they share a protocol, given the extremely little overlap on people herec) they're not really "fediverse memes" just because they happened in the fediverse, are they

  • iirc mastodon was implementing smithereen's flavor of groups. no idea if they ended up changing course or anything (not following masto dev tok closely) but the way they work is fundamentally different from how Lemmy and compatible groups work

  • from what i can tell (from the work in progress pull request) mastodons group implementation explicitly does not aim for compatibility with lemmy

    other than that, i agree on activitypub being crap in terms of making interoperability easy

  • the specs are so open ended that i doubt real interoperability will ever happen. you can break interoperability with basically every other current software out there and still be compliant with the specs

  • that post will have been a text post, not a link (those are likely broken now, and certainly were broken a year ago due to a bug in the misskey 12 codebase inherited by firefish and forks. modern versions of misskey just fixed that a couple months ago)

    the username thing does not completely break federation, but it will randomly confuse instances. there's a 50/50 chance whether an instance will get the correct user it asks or not, and once an instance resolves a user once it'll have a similar 50/50 chance for each profile update (icon change, sidebar change, etc.). of course, if there's no conflicting user for a community (or vice versa) then federation will be fine.

  • my condolences

  • oh no that's not a new change afaik it was always like this

  • I also wish there was an app that let me browse/post/comment on Lemmy using a Firefish/Iceshrimp account so I could theoretically consolidate accounts.

    that'll be difficult. Lemmy killed interoperability when they first decided that users and groups could share the same username, and now itd be a breaking change in order to solve this on Lemmy's end.

    each software willing to federate with Lemmy correctly needs to be modified to handle multiple "users" having the exact same username, and i suspect most have more important priorities to tackle before getting to that

    (misskey 12 derived software also has their own interoperability bugs regarding Lemmy, but those are usually not as big of a refactor as the username thing)

  • It was never unusable beyond the stability issues large instances (from 1k to howevermany people ff.social had) had. For smaller instances it worked fine and continues to do so. The issues with large servers were the result of it being based on an ancient codebase (Misskey v12) with extremely questionable changes thrown on top (muting enough words could cause the entire instance to slow down), and the issues with ff.social were specifically caused by throwing everything at the wall to try to duct-tape that ancient codebase to function (ScyllaDB was the nail in the coffin i believe...?)

    Firefish itself is still going (see firefish.dev), there are forks like Iceshrimp which reigned in the issues enough for larger servers to not fall over every few seconds (iirc both the infosec.exchange hosted Firefish instances migrated over which caused the main issues to be found and fixed). I wouldn't be surprised if "Modern" Firefish took the most important changes over from Iceshrimp (the devs are friendly, and the Mastodon API implementation and some security fixes were shared between both)

    If you want something a bit lighter, Misskey itself is still ongoing, and there are forks like Sharkey that do some of the modifications Firefish and similar forks did to tailor it towards a non-Japanese audience.

    (And Iceshrimp.NET is a project worth keeping an eye on, which aims to get rid of the technical debt of the Misskey codebase by completely rewriting it, but is not ready for much more than a single user instance just yet considering it's been a thing for just about a year)

  • Iceshrimp is a fork, yes, but Iceshrimp.NET (the repo you're linking to) is not, being a complete rewrite unassociated with any Firefish or Misskey code beyond keeping the database schema (for easier migrations).

  • No. They changed hands after the original developer decided to leave for good (and start some crypto scheme which, AFAIK, went nowhere). The repos are now at https://firefish.dev, and no official flagship exists (which IMO is the right way to develop a fedi software)

  • Simply by choosing a lesser used fedi software you're helping keep the fediverse from being dictated by a single software's whims. So that's a big plus there. Federation issues with kbin/mbin/azorius/other lesser used instance software will inevitably happen as people only test against the largest player in the field (in the ""threadiverse"" that's Lemmy, in the microblogging fedi that's Mastodon). So simply by not picking the largest you're, even if in a small way, helping not only mbin but all the lesser used fedi software as a whole.

    Your own local communities being "dead" mainly boils down to communities themselves having a network effect around them where the largest one keeps growing larger as everyone focuses on it. And the largest communities are usually on lemmy.world (or occasionally other Lemmy instances). There isn't that much you can do there.

    In my experience, it's always the smaller software that innovate. The same is true in the microblogging fedi (emoji reactions, quote posts, markdown, nomadic identity, reply permissions) just as it's true in the ""threadiverse"" (combining communities together, the ability to follow people, polls apparently (?)).

    So really, don't worry about the size of your own instance's communities. As long as you trust your instance's staff to keep you safe there's no real reason not to get on a smaller instance, or on different software. Especially on here, where "discoverability" is not as much of an issue as it is in the microblogging fedi.

  • Am I understanding right that this has a low percentage chance of triggering on every tick

    yes!

    but will release a bunch of angry Enderman when it finally does?

    no. you'll get teleported to where the enter pearl is and the potions will be shot towards you, killing you instantly.

  • Mastodon moves also take your following with you. You'll still have to reimport followers, but you don't lose your ""audience"".

    There are software out there (Sharkey for microblogging (Firefish also had it but theirs was broken and leaked DMs), PixelFed for images from Instagram specifically) that allow some form of post imports, but these are only brand new posts that happen to have the same content as the old ones, and not "replacing the author of a post".

    There are work going on regarding nomadic identity and more seamless account migrations across instances, but hell will freeze over before any of the mainstream fedi software implement anything close to that, mainly due to how significant of a conceptual change that is.

  • Mastodon's WIP implementation uses the conventions of Smithereen semi-standardized as FEP-400e. It's not something "incompatible with any other platform" (it's not commonly implemented, but it's not bespoke for no reason either). FEP-1b12 used by Lemmy also has it's own quirks (why are we Announceing activities?) and the specific implementation used by Lemmy will likely not interoperate far without breaking changes that will upset one or the other party, mainly the fact that users and communities can use the same webfinger handle.

    Either every single other software needs to have specific quirks for Lemmy in order to handle this as most (reasonably) assume the username@domain combo will be globally unique, or Lemmy instances need to go on an account or community deletion spree to make this non-unique. You can easily DoS a user or community's federation outside the threadiverse bubble by setting up one of the other with the same username on the same instance.

    PS: Lemmy is the only platform that has had an exploit that overshadows Mastodon’s success

    what? I'd like to remind you Lemmy is the third most largest open AP server software. After Mastodon, and Misskey. (by a not insignificant margin, with Misskey having 8.6% of all known users by FediDB, and Lemmy having 3.8%) Just because they're Japanese doesn't make them any less a part of the network, and they do have their own innovations (MFM, and emoji reactions are just the ones that federate. They also had quotes before many others but I think they're not the first on that one).

  • There's no real reason to. Your own instance (in this case, lemmy.world) has the real view of the thread by the virtue of being the instance starting the thread. lemmy.ml only has it's own copy of this thread that's likely reasonably accurate (compared to any other random instance out there, considering it hosts the community), but it's not the original version, which is what the fediverse link points to.

  • rule

    Jump
  • self described meme communitylook insideunfunny political screenshot

    many such cases

  • MEOW_IRL @sopuli.xyz

    meow_irl

  • tumblr @lemmy.world

    anxiety tips

  • Today I Learned @lemmy.world

    TIL about the existence of Wikipedia's Nearby page, a list of pages tagged with coordinates nearby where you are

    en.wikipedia.org /wiki/Special:Nearby
  • 196 @lemmy.blahaj.zone

    rule

  • 196 @lemmy.blahaj.zone

    rule

  • 196 @lemmy.blahaj.zone

    fresh rule template hot off the presses

  • 196 @lemmy.blahaj.zone

    rule

  • tumblr @lemmy.world

    Situations

  • tumblr @lemmy.world

    Latency

  • 196 @lemmy.blahaj.zone

    breakrule bulletin board

  • AnarchyChess @sopuli.xyz

    Latency

  • 196 @lemmy.blahaj.zone

    cuddle rule

  • Software Gore @lemmy.world

    Got it!

  • 196 @lemmy.blahaj.zone

    ruletific method

  • 196 @lemmy.blahaj.zone

    tiny rule

  • 196 @lemmy.blahaj.zone

    dazed and rulepilled

  • Selfhosted @lemmy.world

    What's your "base" stack of choice?