• 0 Posts
  • 59 Comments
Joined 1 year 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









  • I’m not entirely sure if such an instance exists, but just letting you know that in case you can’t find any, a reasonable compromise would be to join an instance that’s enforcing authorized fetch (and is blocking threads)

    this will make it harder for facebook to read your data through federation alone (i.e. even if a post of yours get boosted by someone with followers from threads, it won’t “leak” there)

    there are ways to bypass this of course but if facebook is found to do something of that sort they would out themselves as actively malicious which would definitely get a reaction even from the “wait and see” crew



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



  • also remember just like how lemmy has it’s kbin, mastodon has it’s interoperable alternatives.

    i bet a fair bit of the complaints i hear from people on lemmy (low character count, wanting to follow topics instead of people) would be solved by trying out a misskey fork such as firefish, iceshrimp or sharkey.

    i don’t think there’s any instance out there with a char count lower than 1000, and antennas are really good (why limit youself to following a single hashtag when you can follow any number of arbitrary keywords?) if you’re in a well federated instance (provided you’re ok with them not feeding into your home feed and them not being retroactive (so after you set up an antenna you’ll need to wait for new posts to filter in))

    they aren’t as polished as mastodon since mastodon kinda ate everyone’s lunch in terms of developer attention (and upstream misskey is an almost one-man-show mess developed entirely in japanese which is why everyone prefers to fork instead of collaborating), but they’ve been getting really good.

    just avoid flagship instances (> 1k active users) for the time being. scaling is still something not many of them have solved just yet








  • 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