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

deleted by creator

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

alternatively: why are you linking to an image at all and not just making a text post

if you were to focus this on just Lemmy itself as opposed to the wider fedi (“Especially given that there was just an update allowing for individuals to block instances they don’t like” implies that’s the case) you already have nothing to worry about as you encountering a threads user here will be even slimmer than encountering a mastodon user.

threads is primarily targeting the microblog/personal side of fedi. the incentives and privacy expectations are quite different compared to this side of fedi

re active users: they’re a large open registration instance, they likely have a fair chunk of twitter people who joined during one of the many migrations and decided not to stick around.

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.

DNS blocking is the most unreliable way of blocking youtube ads you can imagine.
you could write a script to OCR your entire screen and click skip ad and it’d be more reliable than DNS blocking

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

One of the reasons I use containers instead of installing things directly is that i can completely uninstall a service by deleting a single directory (that contains a compose.yml and any necessary volumes) and running a docker/podman system prune -a

or that i can back up everything by backing up a single “containers” dir, which i could have on a subvolume and snapshot if i wanted to

systemd/quadlet on the other hand makes me throw files in /etc (which is where you’re supposed to put them, but ends up resulting in them being tangled together with base system configuration often partially managed by the package manager)

The Solution™ to this is configuration management like ansible or whatnot, which needlessly overcomplicates things for the use cases i need (though they’re still useful for getting a base system “container ready” wrt ssh hardening and such)

tldr: i want my base system to be separated from my services, and systemd integration is the exact wrong tool for this job

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

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.

my predictions are:

• explicit freeze-peach a la exploding heads (the so-called “alt fedi” over on mastodon)
• reddit-style free-for-all with just enough moderation to not be voat 2 (the current default of the threadiverse)
• strictly moderated “traditional fediverse with proper groups”
• porn

of course there will be parts that overlap, but i absolutely expect a split to occur between the “reddit migratees” and “people who want a mastodon with threading” groups, if the second half hasn’t given up on the threadiverse and returned to mastodon already

the piracy drama was good actually because most of the reasonable people from .world will move to smaller instances (and take their communities with them) which will make it easier to block .world and take out a huge chunk of Redditors™ in one fell swoop

the problem is freeze peachers are also moving away from .world onto the same “smaller” instances.

we need more instances with stricter moderation, which is way easier said than done