• 1 Post
  • 37 Comments
Joined 3 years ago
cake
Cake day: June 9th, 2023

help-circle
  • 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:)






  • over the years of using matrix i’ve become convinced that the people behind it simply have different priorities than people who actually want to use it. they’re mainly interested in the tech parts as opposed to making communication tools.

    if you look at the “hype” behind matrix, it’s all about “the protocol”. federation, p2p “host a homeserver on each client”, encryption, bridging, complex state resolution algorithms, peppered with some vague marketing crap about owning your own data. nerd shit or, in the best case scenario, pipe dreams of a magic future that could come with all this flexible tech we’re building

    notice how there’s nothing about actual communities. little to any discussion on moderation tooling, or ease of use. it’s all tech. they only care about the tech. the communities? uh well they’ll happen somehow

    “matrix chat” is just a tech demo of the matrix protocol the same way https://github.com/matrix-org/thirdroom or that fucked up twitter clone they were building at one point is.

    this turned into a bit of a rant but the people working on matrix need to have a deep inner look and explicitly work out if they want to work on “cool tech” or work on tools for building communities. also stop working on so many useless side projects and focus on making one thing that works.






  • 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


  • In Logseq, everything is a nested list. This feels like a limitation, but I’ve been preferring it. The decision is made for you: you’re going to jot this information down as a list. So then you just start writing it.

    Oh - this sounds interesting.

    Whenever I needed to jot down any notes I’ve been finding myself just writing plain .txt files with bullet points, and trying tools like Obsidian or TiddlyWiki I always ended up being overwhelmed with the amount of stuff I could do (and with all the customization options) that I never got around to actually writing things down. I’m definitely gonna look into how Logseq works.

    (Although I have to say, their website does look a bit “too hype-y” for my liking. IDK how to explain it, just a gut feeling. Still, at least it’s FOSS so it can’t be too bad)



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



  • 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