kopper [they/them]

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.

What I’m more worried about are posts relating to news mainly. Where even if the immediate first level comments are fine, there are threads that get out of hand really quickly.

I agree that while posts inherently designed to be controversial may not benefit from Active considering the influences voting has (though me being on an instance that has downvotes disabled may be influencing my view here!), Active may make it significantly easier for an otherwise innocent post to devolve into a flame war.

The main excuse for this kind of algorithm seems to be around “promoting discussion”, but in my experience tech that’s intended to promote discussion does inherently promote flame wars too, as they’re extremely difficult if not impossible to distinguish without a human in the loop. I’ve attempted to write something about this on the microblogging side of the fedi, directly influenced by this post

I’m just throwing this out there but having the default sort incentivize comments seems like it’d highlight posts meant to cause flame wars… Is that what we want out of this platform?

To be fair join-lemmy also advertises the software as “blazing fast” with “powerful mod tools” and if there are two phrases I’d associate with Lemmy those aren’t it.

(OK compared to Mastodon Lemmy is blazing fast, but that’s cheating considering of how slow Mastodon is)

i’d say 6-7k users would be a better figure, but i do agree with your overall point. anything above 10-15k just hurts the health of the federation in the long term and ends up creating “untouchable” servers. even worse on lemmy where communities are also bound to instances.

though now that i’m thinking about it, a better metric would be active users rather than total users

I’m not sure on if we’re talking about the same thing here but as someone who disables JS by default, any federated service without some form of SSR is inherently clunky to use. Half my allowlist is Masto instances I’ve barely visited once or twice because website boy is a jerk and ruined a reasonably well functioning SSR UI.

I don’t get why the language would make a difference in how you deploy the frontend. You can already host the BE and FE on different hosts with the right reverse proxy config. This just replaces the Node in lemmy-ui with Rust+Leptos.

tbf compared to masto/“microblog fediverse”, the “threadiverse” barely had any culture beyond a few exceptions so this place is almost guaranteed to get “redditized” if you’re not on an instance that moderates with the same strictness you’d expect on masto (partly why i picked this instance among others)

i’ve seen my fair share of freeze-peach warriors in the comments here. all you have to do is to drop the word “defederation” anywhere and they’re all raging to “debate”

Izzy directly sends over the APKs from GitHub releases. F-Droid does their own builds which is partly why they’re so slow to update.

Hot and Active are broken, Use different sorts. Depending on how recentiy I checked I personally use New Comments or Top of 6 Hours.

Let’s take lemmynsfw as a rather difficult example. Nobody wants to moderate porn which makes it even harder to decentralize it, but even at 6k users should something happen to it, all the porn in the entire network bar effectively private communities on the few instances that allow it (or the l*licon filled and hopefully defederated burggit) goes away. Not because of its users but because of its communities.

With most instances being general purpose, this will be less of a problem, as for nearly all other communities, there is 0 incentive to centralize in this way beyond “the initial creator had their account here”

The thing with Lemmy in particular is that unlike Mastodon, communities need one instance. dot ML’s and dot world’s potential future “untouchability” is, in part, because communities will also centralize there. Spreading users very “thin” among the network should also indirectly spread new communities off the big several instances.

And of course. the 5k number I mentioned is both

• out of my ass with no real proof, but also
• a soft cap with a theoratical invitation system (or other way to not lock registrations completely) complementing it

While the numbers themselves likely need adjustment, it definitely should be “lower than you expect”

Eventually, some day, we’ll have established no-brainer options like gmail and proton are for email.

Thanks but having yet another “too big to fail/block” mastodon.social/online or matrix.org should not be our goal. dot ML and dot world are already “dangerously large” with beehaw and shit just works being close contenders (if not already up there with those two).

Right now it might make sense to centralize just so we can accomodate Reddit folk who don’t want to choose, but too much centrailzation is already starting to show it’s cracks with e.g. the whole Beehaw situation.

IMO most instances should have a soft-cap of about 5k people or so, after which an invite system (should one be developed at some point) can still bring a manageable amount of people over every so often. Most Masto servers right now that don’t suck seem to be running on a similar premise, otherwise it would be hell to moderate, especially with the immaturity/nonexistence of moderation tools.

These tweaks are definitely not for everybody. I just made it for personal use and wanted to throw it out there just in case anyone else wanted to try them out.

If your instance shuts down, you won’t be able to use that account, and your existing content will be in a limbo of pre-shutdown instances knowing about them and post-shutdown ones not. I assume a similar limbo will happen to the communities hosted on your instance, but I’m not entirely sure on what specifically will happen.

Not sure if you’ve thought about it yet but consider modifying Lemmy’s source (shouldn’t be too hard of a patch) to show NSFW tagged posts to logged out visitors. (And maybe force-tag all outgoing federated stuff as NSFW? Though that might be difficult for very little gain) It looks like a ghost town from the outside and that’s not gonna be helpful if you want any content

Speaking of content, good luck on the moderation. You’re gonna need it

with how much .ml is struggling to handle the load I would’ve expected even more to pick different instances, though the situation seems better than how mastodon.social was during the twitter migration

the upcoming centralization issue sounds like it’ll be the communities themselves all being hosted on .ml, not accounts. can’t want to see how that one is gonna play out