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

help-circle
  • i’m pretty excited for fedify since i’m unsure if there has been any other activitypub abstraction that feels as comprehensive as it seems right now (from a brief skim, anyway).

    one thing i had in mind ever since i first skimmed the docs some time ago is this:

    federation.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
    

    i would really recommend you to NOT tell people to use handles here. i assume this is just naming and the framework doesn’t actually require a handle there, but documentation matters and if you follow on the footsteps of mastodon, pleroma, lemmy, and friends everyone who follows your docs will lose the ability to change usernames down the line without more pain than it’s worth (and yes, there are software out there that allow it right now! please do not build fedi software assuming usernames are immutable jsut because mastodon doesn’t let people do it)

    just like how you wouldn’t use a natural key in a database, you should tell people to use a surrogate key like an autoincrement id or a uuid on the actor IDs, as they’re effectively permanent. while it may be probably fine for a quickstart thing like this to omit that, a lot of permanent codebases do start up by following these kinds of guides, and nudging people to do the correct thing when it’s not that hard is always a good idea IMO






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






  • 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


  • I imagine the most “ideal” outcome would be “whatever link the default webui shows as the fediverse link (the colorful icon on all posts / comments)”, as that’s the “canonical” link (technically, the ActivityPub ID, which is I think required to be a link as per the spec) of that specific post or comment.

    It’d be the most accurate in terms of visibility (could be deleted by OP and the delete might not reach your instance), latest edits, vote counts, and replies for that specific thing, that said it’s definitely not as convenient as just copying the link in your URL bar and pasting it to wherever.

    Also depending on the exact software running on an instance, that link may not point to a human readable page, but that’s a pretty rare edge case that even the most incomplete real life implementations I’m aware of handle reasonably well (even if it ends up doing a redirect)





  • Another thing I would like to suggest is a change in recruitment strategy. At this point it seems like we are unlikely to pull a significant amount of users from Reddit without more reddit-policy-driven migration, but there are tons of highly educated and engaged users over on Mastodon that would make serious positive contributions to the tone and quality of the discourse over here. For some reason there seems to be minimal overlap between the two communities and that blows my mind. Not only that but I actively see folks disparaging Mastodon in fediverse related communities on a regular basis (and even sometimes in the Mastodon communities themselves). As far as I can tell, these are largely lingering sentiments from a Reddit/Twitter dichotomy. Remember, as things develop the lines between threaded social media and microblogging are likely to blur. A significant number of Mastodon apps already provide a threaded view and one of kbins explicit goals is very much to bridge the gap. With this in mind, Mastodon (and federated microblogging more generally) seems like the best source for new potential users.

    A thing to look out for is that the microblog fedi (outside the big handful of instances that fill .world’s role there) is strongly in favor of stricter instance-level moderation compared to the more “individualistic” view a lot of the Reddit migratees tend to have. If we want people from the microblog fedi to participate we (collectively) need to up our moderation game. (And in my personal opinion instances like .world have grown too large to accomodate any reasonable expectation of moderation, except for select individual communities set up there)