• 53 Posts
Joined 1 year ago
Cake day: June 9th, 2023


  • Which instances did you try? I want to check if it was the background radiation of USpol inherent to most online communities you’re sick of (which there really isn’t a solution beyond keeping up with the newest buzzwords to add to your filters for from what I can tell) or the dot-social/kolektiva/twitter-like “my political happenings are too important for a content warning and must be boosted to everyone’s eyes 24/7” variety of USpol (which there is a ton of in Lemmy as well but i don’t think most people are ready for that debate yet)

    The second one can be ameliorated a little by picking a smaller, sillier instance (hint: the weirder the domain, the better) and not following The Same Large Accounts Everyone Does.

    In fact, I would advise against Mastodon the software altogether and instead point you towards instances of Akkoma or one of the not-Japanese Misskey forks such as Sharkey, Firefish, or Iceshrimp. The vibes of most instances I’ve seen seem to be cozier, and the Bubble timeline (called Recommended Timeline by some software) helps with discovering people to follow beyond the said Large Accounts.

  • Lemmy’s cross posts are separate posts that just happen to link to the same thing. so only replies to the original post would be sent with the current design.

    that said, i severely doubt Lemmy will gain anything from this. publishers will not be sending out their posts to any communities, and i highly doubt they will expose any fep-1b12 group actors you can subscribe as a community.

    kbin/mbin with it’s ability to follow users may work better, assuming people test their federation with software other than mastodon, and accept any of the interoperability bugs as actual bugs instead of ignoring them. (lemmy itself is no stranger to this: the fact that users and communities can share the same username break quite a bit)

  • while i don’t have any specific opinions about this that other people haven’t addressed, i just want to flag up something;

    How this could be enforced? No voting from the All and/or Local feed. Seems easy and straight forward.

    this seems unenforcable. as in, you can’t really tell where someone discovered a post from. yeah you can just remove the buttons from those views clientside and it’ll probably work for the majority of cases, but alternate clients or modifications to lemmy-ui can simply put the buttons back in (or in cases of unmaintained or differently opinionated clients, just not remove the buttons at all). the backend can’t really differentiate which view a vote comes from. federation especially can’t differentiate which view a vote comes from.

  • I mean, there’s only so much you can do when your upstream is developed exclusively in Japanese (to the point the code comments are also in Japanese) with a focus on adding Reversi and a Suika Game clone into the software instead of refactoring so the same piece of code isn’t duplicated in 10 different files split across the frontend and the backend and refuses to implement editing because they find it too hard when both major fork families (Firefish/Iceshrimp and Sharkey) have it and it works fine enough (alt text edits don’t federate, but that’s comparatively rare)

  • I’m also very curious to see how (if at all) you migrate an existing server with all its existing ActivityPub keys and subscriptions to a new piece of software, on the same domain, without unfixably breaking its federation with every other instance. My guess is that they will switch to a different beehaw.(whatever) domain but I’m curious if there’s a good solution I’m not aware of.

    If the software you’re migrating to is built to allow that to happen, it’s absolutely possible. In the microblogging side of the fedi migrating between software isn’t uncommon, though in nearly all cases they’re forks from the same “family tree” so things work out mostly due to that, (Misskey is infamous for having a LOT of forks with most being capable of migrating to most, Mastodon can migrate to/from it’s forks Glitch-soc/Chuckya/Hometown, and Pleroma and Akkoma can migrate between each other…).

    There are software being built from-scratch to be migratable from other software (aside from Sublinks, Iceshrimp.NET comes to mind as a total rewrite of Iceshrimp, which started out as a fork of Firefish and therefore is in the Misskey family tree, but found the existing codebase to be un-salvagable) but it’s definitely a rare case.