I’m a #SoftwareDeveloper from #Switzerland. My languages are #Java, #CSharp, #Javascript, German, English, and #SwissGerman. I’m in the process of #LearningJapanese.

I like to make custom #UserScripts and #UserStyles to personalize my experience on the web. In terms of #Gaming, currently I’m mainly interested in #VintageStory and #HonkaiStarRail. I’m a big fan of #Modding.
I also watch #Anime and read #Manga.

#fedi22 (for fediverse.info)

  • 0 Posts
  • 144 Comments
Joined 2 years ago
cake
Cake day: March 11th, 2024

help-circle




  • federation and instances is a confusing prospect

    Which is why we shouldn’t frontload people with that stuff. They don’t need to understand decentralization from the start, let them familiarize themselves with the fediverse first before throwing that at them. Just recommend a default instance, maybe change which every few posts if centralization is a concern. They’ll pick up the idea of instances as they interact with the fediverse.






  • This article’s core argument seems to be that Pixelfed is violating the ActivityPub protocol by not displaying posts that do not contain images. That’s just not true at all. I’m interested to know where the protocol ever has such a requirement.

    The principle behind a communication protocol is to create trust that messages are transmitted.

    And they have been transmitted. They’ve been filtered out after transmission, but the protocol did its job.

    If a message is not delivered, the sender should be notified.

    Perhaps. But that’s not in the spec. There’s no obligation to notify iirc that a post got filtered out on the target instance.

    Even if Pixelfed sent Reject(Note) back for every post without an image, would Mastodon even display that to the user anywhere? Would most users want to see that for every post not containing an image multiplied by every Pixelfed instance it got federated to? I’d personally interpret that as spam.


  • Lemmy doesn’t really target compatibility with Mastodon. It does have some of it by using the same federation protocol, but it’s all incidential and not actually directly supported.

    If you wish for proper support, I recommend switching to Mbin instead. It’s a Lemmy-like project that aims to work with both Lemmy and Mastodon.

    When it comes to communicating between Lemmy and Mastodon though, this is what I know:

    Contacting specific Mastodon users

    You can mention any Mastodon user the same way you’d mention a Lemmy user. They will get your mention and will see the post or comment you mentioned them in. Your instance doesn’t need to be federating with the Mastodon instance in question for this to work, as long as you’re not explicitly defederated from each other.

    Federation to Mastodon

    Lemmy communities show up on Mastodon as users, so Mastodon users can browse and follow them. They basically function by boosting (retweeting) every post made to them. So all you need to do for your posts to show up on Mastodon is to have a user on there follow the community you’re posting in.

    Posting to Lemmy from Mastodon

    Mastodon users can post to Lemmy communities by mentioning them, as if they were a user. Lemmy will display them as threads despite them being microblog posts, Mbin separates Lemmy-style threads and Mastodon-style microblog posts in your feed.

    Discoverability

    Interacting with Lemmy communities directly isn’t too common for Mastodon users, hence the low amount of contact between the two. If you want to increase your discoverability, add hashtags to your posts. Mastodon iirc mainly relies on hashtags for discoverability.

    Lemmy does NOT let you browse Mastodon posts or follow users on there. Mbin does though. So again, if this is something you want, do consider switching instead.





  • If you don’t want to see mention soup, just limit the number of mentions per post on your instance.

    Doesn’t Mastodon require mentions though to function correctly? Imo instances should just not display leading or trailing mentions / hashtags. That should get rid of the problem without imposing limitations on Mastodon users.

    Definitely agree with you on your first two points.


  • So what if Lemmy, Piefed, Mbin, and NodeBB made it so that only the first matching community gets the post?

    I’m pretty sure Mbin already does that with sorting posts into communities based on their hashtags. Does it not do it with mentions too? I can’t really test it since 99% of federated posts only mention one community, if any. So I’m struggling to find a post that mentions two communities, let alone two that are active enough on my instance to compare them.

    But like, is it actually an issue? I always get the impression Lemmy users have more of a problem with the hashtags and mentions in general, not with the fact the post appears in multiple communities. Which would be easily solved by having their instance remove those from microblog posts.

    We can already tell which posts come from threadiverse software and which don’t (because we use audience, Mastodon doesn’t.)

    I honestly don’t think that’s a good way to decide between threadiverse and others in general. There’s no guarantee non-threadiverse software won’t make use of it in the future.



  • reluctance to stop dealing with Russia

    Can you name examples?

    We did always implement all the EU sanctions afaik.

    In case you meant us not using Russian assets to help Ukraine like the EU does, iirc they’re using interest, not the actual assets, for that. Which I remember reading (but don’t have a source right now) isn’t possible for Switzerland due to how they are stored in commercial banks rather than central repositories. And just seizing them would be illegal. It’s not like we don’t want to (though that’s probably a factor too), but more like we can’t.