There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

Mr_Blott , to lemmyshitpost in One day šŸ‘

#I for@ am quite @I donā€™t @look @ comments @this all day

e569668 , to fediverse in "ActivityPub not suitable for implementation as the base federation layer in diaspora"
@e569668@fedia.io avatar

There's some relevant discussion here and in the thread linked by ernest in that post here. I don't want to give any wrong information, but I don't think activitypub has a spec for downvotes/reduces/dislikes, just likes and shares (boosting). So on mastodon dislikes definitely aren't federated. I believe for lemmy, they federate between lemmy instances that have them enabled, but for kbin they are local to your instance.

dukk , to youshouldknow in YSK: Your Lemmy activities (e.g. downvotes) are far from private

If that is a solution youā€™d need to change the ActivityPub specification. You are more than welcome to submit your idea.

AFAIK, the ActivityPub specification has no requirements on how likes should be stored. The two things that is requires are that likes are added to the userā€™s liked collection, and that the postā€™s like count is updated.

This is also not compatible with the ActivityPub spec but even if it were youā€™d win nothing because as soon as you fetch the post it is still on the server.

Mastodon actually just stores all this data on the server containing the post itself. Instance admins get as much information about the post as the client does. Both Lemmy and Mastodon use the same protocol, but Mastodon chooses to only to trust the server the user is using, and not the third-party servers.

Iā€™d first have to create 2000 users, then Iā€™d have to send 2000 upvotes. And then Iā€™d get blocked by all instances.

Creating that many users wouldnā€™t be hard to do(you donā€™t need to use the GUI, just a little SQL is all thatā€™s needed). And you donā€™t need to ā€œsendā€ the upvotes; you can sidestep the protocol entirely and just update the database. Thatā€™s the problem.

And while yeah, the instances would block me, they probably wouldnā€™t notice if I did it at a much smaller scale. In fact, thereā€™s no real easy way to check whether these upvotes from an instance are actually real.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • ā€¢
  • random
  • lifeLocal
  • goranko
  • All magazines