@BraveSirZaphod@kbin.social avatar

BraveSirZaphod

@BraveSirZaphod@kbin.social

This profile is from a federated server and may be incomplete. Browse more on the original instance.

BraveSirZaphod,
@BraveSirZaphod@kbin.social avatar

If you want to stay private, probably avoid a networking protocol like ActivityPub that inherently relies on essentially everything being public

BraveSirZaphod,
@BraveSirZaphod@kbin.social avatar

Mate I think people are just kinda lazy and don't really care that much about privacy relative to ease of use and the presence of people they're interested in.

BraveSirZaphod,
@BraveSirZaphod@kbin.social avatar

The point of the article is to appeal to people's hatred of Meta (which is well-earned, admittedly), not to actually say anything meaningful.

Having observed conversations about Threads here and on Lemmy, it's a pretty dependable tactic. I completely understand not wanting to associate with Meta and not trusting their intentions, but there are plenty of things to criticize them for without trying to whip up a fury over what's objectively not problematic. But this is the internet and people like being in a fury, so whip one up they will.

BraveSirZaphod,
@BraveSirZaphod@kbin.social avatar

I think there's something to be said for it being public. If someone's downvoting all of your content for no reason without engaging with it, that's obviously not someone worth your time and it may be a decent idea to just block them. I could also imagine some communities making it explicitly against the rules to downvote constructive comments for no reason, for instance.

At any rate, my understanding is that the actions must be at least publicly accessible in order for federation to work, so the only thing that Kbin could do is simply not openly display that data. Perhaps making it less accessible would reduce the temptation to look, but it'll always be available to anyone who truly wants to see.

Lemmy.ml is blocking all requests from /kbin Instances (kbin.social)

I discovered yesterday evening that Lemmy.ml is blocking all inbound ActivityPub requests from /kbin instances. Specifically, a 403 'access denied' is returned when the user agent contains "kbinBot" anywhere in the string. This has been causing a cascade of failures with federation for many server owners, flooding the message...

BraveSirZaphod,
@BraveSirZaphod@kbin.social avatar

I'm not sure how much you know about networking or HTTP, but from the evidence posted, this very much is not the kind of thing that just accidentally happens.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • meta
  • Macbeth
  • All magazines