Beruflich Web-Entwickler, privat ein Ober Nerd und Links-Grün versifft…
Musik Liebhaber, von #kpop bis #metal alles dabei
Ansonsten bin ich auch gerne mit der Kamera unterwegs.
Entwickler und Maintainer für #mbin

ich bin auch auf mastodon: @BentiGorlich

Ich betreibe thebrainbin.org, gehirneimer.de und wehavecookies.social

  • 28 Posts
  • 335 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle

  • I think we are getting there. Currently the biggest problem I see is that melroy and I are currently the main contributors with other experienced contributors gone or at least not regularly active (which is of course their right, but its just how it is). I do have a whole lot of ideas and plans for features and I am working on a lot simultaneously, though I wouldn’t say that it is a burden, more like a fun hobby. Admittedly this hobby takes a lot of time though 😅

    I am very happy that new contributors are currently dipping their toe in the water and I hope they do stick around. Also a lot of the server admins are active in the matrix chat to help others out. So in this regard we are not alone.

    I was honestly shocked that debounced left so suddenly and basically completely vanished… I didn’t think that anyone would do that… So honestly we cannot promise anything, but I think melroy will stay around and I certainly will as well 😇





  • We can look at PeerTube for an example of a system that could be shaped into what I meant: when you look at a post (video) from peertube it links lists for likes, dislikes and shares (so basically upvotes, downvotes and boosts). These collections contain a totalItems property, but also list the peoples identities, but just imagine that it wouldn’t be there. When a user now likes the video, the creator of the video now sends out an Update acitivity to all subscribers. Now all subscribers can update the counts for likes, dislikes and shares. Only the “home instance” of the creator account knows about all votes, nobody else does, but nevertheless everybody else can now how many likes, dislikes and shares there are.

    If we compare that to mastodon the first part of the statement is still true:

    Only the “home instance” of the creator account knows about all votes, nobody else does

    But that means that most instances just show 0 likes for most of the posts, because your instance only knows about likes originating from your instance…


    As for your proposition: I couldn’t follow for some of it. However I think the risk of an actor abusing the creation of fake accounts and fake upvoters is not really a risk, that is what defederation is for… I would argue very much agains a lemmy specific protocol and some judge instances simply because then big instances would just have pretty much all the data again and it would definitely hurt interoperability because lemmy devs can then just take the easier route instead of implementing something according to AP spec


  • You cannot make votes completely private, one instance has to have the authority over which votes do exist. This instance should be the origin of a post or comment.

    At the moment it works like this: you upvote a post, this upvote gets send to the author of said post AND the magazine and that magazine then broadcasts your upvote to all subscribers of said magazine.

    I could imagine that the process looks a lot different: you upvote a post, this upvote gets send to the author of said post, the author of the post then sends an update to the magazine saying how many people have now upvoted their post and the magazine then broadcasts this info to every subscriber of the magazine.

    With that you would of course have new limitations concerning moderation and maybe there are trust issues regarding the correct reporting of that upvote count, but only the author of the post (and their instance ofc) could technically know who upvoted their post. As in everything here this is a compromise and whether the gained privacy is worth the other limitations, I don’t know