• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: July 18th, 2023

help-circle



  • The walled garden social networks have a serious downside compared to fediverse networks and that’s the registration wall. If you’re primarily publishing press releases and announcements, people will be unable to effectively share through links what you’re publishing. Mastodon let’s you bypass that while still allowing for the engagement that the other platforms do. And you don’t have to play pay to win with the algorithm to get your stuff to actually show up on feeds of the people already fucking following you.












  • Two services that are very interoperable (because kbin is designed to be, specifically able to bring in microblogging content while lemmy can’t) and still have problems. Did you know boosts are what make comments appear higher on kbin while favorites work that way on Lemmy? That’s the sort of thing I’m taking about. Every implimentation of activitypub kind of makes its own rules on what tokens mean and if you want to be compatible, you have to change your service as they change theirs (which is what happened, lemmy changed and kbin hasn’t gotten around to it yet since it’s not a big priority).



  • I don’t really know what the dev’s roadmap is, but I do think that reccomendations shouldn’t even be a part of the instance beyond recommendations from your “community” or people who you follow. I think it should be a seperate service/website that imports your goodreads/bookwyrm data and algorithms it while serving ads(meaning their revenue will come from publishers/authors). It can then push recommendations over to your bookwyrm home instance with activitypub. Otherwise each instance will need the data from every other instance just to give you recommendations based on what other people like you enjoyed. It also allows the service to be easily replaced once it starts to go to shit, since there’s not a single “this is the recommendation engine”.