Just because you wish to talk about your own country does not mean I want to listen to the politics of a country I am not a citizen/resident of nor have ever set foot in. That’s what content warnings and other functionality allow me to do. Unfortunately, Lemmy.

(Also notice how I specifically single out “US politics” and not “politics” in general. That is a different thing where “politics” is sometimes used to mean “anything I don’t like not from a white cis het from the upper middle class person”. That is not the case here. I am simply tired of hearing about Trump and Biden and Harris and whoever the new VP is or whoever the Republican Main Character of the day is or the Democrat Main Character of the day is)

True, that will at least let you figure out what is a fediverse link and what isn’t. Most implementations I know either use the same URL for both the AP representation of a post and it’s HTML one (differentiated by the Accept header), or have a redirect from the HTML view to the AP representation when an AP type is requested (or, very rarely, the via Link header/<link> html tag), which means you can reuse code used for the “search URL to load community” feature in order to make this possible.

Given the list of fedi instances your instance is aware of is already present in the API, clients already have the tools to do this, I believe.

How do you expect for that auto-detection to work? Just a regex on example.com/c/community? What happens when some other instance software decides to use a different URL format? Or do you just assume Lemmy is the only thing out here?

Doesn’t help. Everything from the meme/joke/fun communities you’d expect people to use to tune out The Horrors™ to discussion about the ActivityPub standards (what little exists that doesn’t conflate it with Just Lemmy or Just Mastodon) devolve to US politics in like two comments. For me at least this entire section of fedi is a US politics-radioactive one I try spending as little time as possible (that includes posting non-politics!)

I find myself having significantly more fun on the microblogging side of the fedi, ruining jokes to ground in like 4 minutes with my oomfs and making followup meta jokes about how jokes only last 4 minutes. People actually use content warnings to hide away The Horrors™ when they want to talk about it, which means filters actually work. (Things like alt text for images also helps with word filters!)

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:)

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

git commit -m $(date)

https://gitlab.freedesktop.org/mstoeckl/waypipe

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

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.

I swear fossbros lose reading comprehension skills faster than Tumblr once you ask for any kind of software recommendations

i was thinking of attempting something of that sort but i quickly realized that it’d be even more useful as a generic “list of communities for/about [thing]”, and people could then use that generic list both as a subscription list AND as a block list, depending on their interests

and then i swiftly gave up realizing the scale of it all so if anyone wants to run with this idea feel free to do so

Sounds a bit too centralized for me

You can turn it off however that makes join times to any channel with history (say… the dendrite release announcements channel for example) unbearably slow to join.

I think more matrix users should consider using smaller instances tbh

Matrix on smaller instances suck because of how bad the protocol is. It “re-plays” the entire history of the channel on first join because channels need to be consistent between all instances because Matrix isn’t just a mediocre chat protocol but a generic data protocol that’s been beaten into the shape of a mediocre chat protocol.

It tries contacting every instance in a channel for their keys. Even the dead ones. And yes it takes exactly as long as you think it does for them to time out. Dendrite solves this by asking matrix.org for everyone else’s keys by default.

But because channels are completely synchronized at least you get to easily migrate channels between instances just by assigning an alias and telling people use the alias to join instead.

Security? Probably. I wouldn’t expect any measurable improvements to performance but the with compiler being able to do more checks it might enable some clever optimization trickery that would be harder to maintain in C.

Still, Rust on the kernel probably won’t leave the realm of drivers any time soon, so it all depends on if you have the hardware that will use a driver written in Rust.

There are instances that bump up the max length. The word you’re generally looking for is “glitch” (instances will say they’re running “the glitch fork” or “glitch edition” or will have version numbers ending in +glitch, which has a few features on top of regular Mastodon), although some regular Mastodon instances may also increase the char count the hard way.

Alternatively, Firefish/Misskey by default has ~3000 characters but it’s a completely different experience altogether (although it still federates with Mastodon (like kbin and Lemmy)). I’m not exactly sure on how Akkoma instances are usually set up but that’s worth taking a peek as well.

Of course this doesn’t address the politics stuff but that’s more on you to curate your own experience.

Learn about reverse proxies such as Nginx or Caddy. The various selfhosted communities on Lemmy should be able to help with your questions. That’ll fix the port conflict problem. (Though I recommend wiping your Lemmy DB and starting from scratch when changing domains. Federation is really finicky in situations like that)

My second recommendation would be to use blocklists to deny the crap parts as opposed to allowlisting as that will impact your view of the threadiverse. (Which by itself isn’t a bad thing, but is the wrong tool for the job in most cases I’ve seen people asking about it)

There are instances that disable downvotes, you may want to migrate to one that does. https://github.com/maltfield/awesome-lemmy-instances#all-lemmy-instances has a column that indicates if an instance has them turned on or off.