nah, there are plenty of truth wannabes (freeze peach bigotry safe havens) that actively federate. just look at literally any competent server’s blocked instances list and you’ll see a few examples. there’s a reason why nobody* runs completely open federation
*: aside from people who’re friendly with that crowd ofc
mastodon doesn’t “discover” akkoma content and won’t show anything unless you’re following a user from there, which kinda sucks.
I mean – that’s how all of them work. Even Lemmy. Unless your instance administrator joins relays (which have tradeoffs between privacy / effectiveness of blocking) your instance is only ever aware of posts from followed people (and reply threads followed people are involved in)
(also MUCH lighter on server resources, compared to most other twitter-like alternatives)
Mastodon is just unusually heavy, really. Even Misskey & forks are lighter than Masto on the server side (preferring being bloated on the client instead)
Mastodon feels like a fucking funeral.
You’re clearly nowhere near the good parts, then.
In my experience, once when you find your way into the correct circles the microblog-verse makes the “shitposting” of Lemmy look like r/memes. I do agree that discoverability could be better though, it took me 4-5 months before I got the hang of it. And now I barely check Lemmy despite my Lemmy account being older than my earliest microblog account (under this name, anyway).
One important thing is that your instance matters quite a bit more than here. Starting on a large general purpose instance (especially if it’s mastodon.social) and just following Large Accounts and Nobody Else like most people recommend for some reason is just setting yourself up for disappointment. Instead, get on a smaller interest-specific instance (rule of thumb: the weirder the domain the better your experience will be!) and follow the local timeline (and on good software, the bubble/recommended timelines). And post stuff/interact with people. Don’t be that one person that does nothing but boost news bots and occasionally butt into replies of people asking rhetorical questions they already know the answer for.
(Perhaps Lemmy is better at news or whatever, I wouldn’t know as I block all news communities I can find – I just don’t see the point as all the discussion around most news ends up predictable, unproductive (not that internet communities necessarily need to be “productive”), and unnecessarily angry)
Also in a world with usable™ Misskey forks and Akkoma I think the limitations of Mastodon the software are really starting to show, and I urge anyone who’s been disappointed in Mastodon to try other microblog software. (Quotes are already a thing if you know where to look! So are emoji reactions, because people have more emotions than :star:)
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?
the 0.19 implementation is so half-assed I genuinely think the Lemmy devs just don’t want that functionality but expected quite a lot of backlash if they outright said as much, so they decided to implement something that ticks the box in the “wanted features” list without having any effect
afaik it only blocks communities and explicitly lets users from blocked instances through
(talking about microblog fedi here, Lemmy/threadiverse is it’s own thing)
don’t do hashtags. hashtags (especially common ones like #memes) are overrun by repost bots and low quality garbage.
the trick is to be on a small-to-medium instance you vibe with (1k active users seems to be the sweet spot. anything larger than 2k I’d avoid. do NOT join any flagship instances like mastodon.social), follow fun people from your local timeline, and see who they boost. and follow up the boost chain until your timeline is sufficiently fun.
WHATS THAT PUSSY-ASS VOICE WHEN YOUR WITH THE PACK YOU SPEAK UP AROO
so, are you paying for it?
git commit -m $(date)
I’m mildly worried I know (as in, am aware of their existence, thankfully not having interacted with them) who you’re talking about
well I just checked and while “sync contacts” did not turn itself on, “allow contacts to add me” did. there’s definitely something going on
TLDR of linked gist: wayland is not X therefore it is bad. end of.
Wayland breaks Xclip: As you said it yourself, Xclip is an X11 application, so it doesn’t work on Wayland. Of course it wouldn’t work on Wayland. With Wayland, we’re trying to prevent what happened with Xorg from happening again, or am I wrong?
also, https://github.com/bugaevc/wl-clipboard. perhaps all OP (of gist) needs is a simple shim that can convert calls to xclip to wl-copy/paste? that doesn’t seem too hard to make compared to keeping X.org alive I’d say (perhaps they should try making it if it’s that much of a problem)
Wayland breaks screensavers: Yeah, that seems to be the case.
from the dev of xscreensaver at https://www.jwz.org/blog/2023/09/wayland-and-screen-savers/ :
[…] Adding screen savers to Wayland is not simply a matter of “port the XScreenSaver daemon”, because under the Wayland model, screen blanking and locking should not be a third-party user-space app; much of the logic must be embedded into the display manager itself. This is a good thing! It is a better model than what we have under X11. […]
[…] Under X11, you run XScreenSaver, which is a user-space program that tries really hard to keep the screen locked and never crash. It is very good at this, but that it needs to try so hard in the first place is a fundamental design flaw of X11. […]
other people can comment on the parts they know about, these are two i know of off the top of my head
the rule of thumb here is that you should really just use one browser ad blocker. having multiple will conflict especially regarding anti-adblocker prevention (as uBO will try to hide itself and redirect to a “defused” version of an ad script and whatever other ad blocker you have will think that’s an ad and block it)
not entirely sure how well DNS ad blockers fit into this. there is a chance they could make your ad blocking detectable by blocking a request uBO intentionally lets through (possibly in a modified state), but as far as i’m aware there haven’t been too many issues stemming from combining DNS blockers with uBO and the likes.
https://tildes.net/invite should let you generate some
Every time a site update/announcement/whatever happens everyone with an account older than like a week (iirc?) gets topped up to 5-10 invites. You can (could?) also just go to r/tildes or email and ask. They use invites more as a way to slow registrations down than to be an exclusive club so it’s really not that hard to get your hands on one.
if this were to happen trust me when i say pluton’s role in enforcing it will be little to none.
as far as i can tell this particular image is fake. and as far as i know pluton does not work like that.
while i don’t have any specific opinions about this that other people haven’t addressed, i just want to flag up something;
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.