this post was submitted on 18 Jun 2023
33 points (100.0% liked)
/kbin meta
200 readers
2 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yes - it is likely down to the lack of a standard. Upvotes are federated out as the same ActivityPub schema as liking something. Boosts are federated out as boosts. So if someone on Mastodon saw your comment for example, liking it - is typically a way to say to the poster "I like this", but when you boost it you want other people to see it - so the sentiment is roughly the same here. Because if your reputation could be increased by someone on a different platform simply liking your comment - that would be fine - but there is no currently available federated ability to downvote - so people would have an artificially high reputation, because only the people on kBin platforms can downvote you. (I don't actually know if downvotes from lemmy platforms affect us here)
Seems kinda wonky. I'm working on writing my own flavor of an ActivityPub client. Is there somewhere you know of that this is being discussed, developed, etc? Iirc ActivityPub itself doesn't define this, right? I figure what we're talking about here is just the data model some apps have created within the ActivityPub spec - and by keeping it consistent apps can federate with each other. I'm curious on advancement of that model to introduce new concepts and features but retain some compatibility.
ActivityPub specs are discussed and I believe extended here: https://socialhub.activitypub.rocks/c/activitypub/5