자유게시판

• 목록
• 답변
• 글쓰기
• 게시판 리스트 옵션
  • 수정
  • 삭제

I'm unsure this conduct is constant after all with how blocking works on X-Twitter; it was not my understanding that blocking someone could be public information. Especially as a result of proper now quite a lot of people are working on this data out of belief in and hope for the longer term. The reason for this is very simple: we have seen individuals who make the most of blocklists be retaliated against for blocking someone who is indignant about being blocked. So direct messages on Bluesky are centralized, and while Bluesky does say so in their blogposts (previous the point at which most people have learn), most customers I've talked to have assumed they labored the same way that the rest of ATProto works. Zooming out, once again, the message passing system merely has 5 new messages sent. But as both alice and Bryan Newbold have identified, using a devoted server would be a lot cheaper. The server Should stop the blocked user from interacting with any object posted by the actor. The Block exercise is used to point that the posting actor doesn't want one other actor (defined in the thing property) to have the ability to interact with objects posted by the actor posting the Block exercise.

Servers Shouldn't deliver Block Activities to their object. I discovered this very shocking; in ActivityPub's improvement, I remember a dialog between Amy Guy and myself where we decided it was very important to not deliver Block activities between servers. A single machine doesn't look like it generally is a viable answer for very long, so pointing to dedicated servers which might at the moment handle a complete relay (when not actually relied upon by any variety of customers) is not particularly convincing to me. The fediverse currently hosts around 27,000 servers (many extra customers, but let's focus on servers). Things are sometimes more decentralized in degrees, and i actually suppose the fediverse could possibly be extra decentralized than it's. More anti-spam / anti-harassment tooling constructed on high of capability security foundations. Which is to say, not non-public enough for a lot of sorts of safety issues these days: your administrator can learn your DMs but hopefully does not in the overall case, but messages usually are not end-to-finish encrypted at present. And he has a few surprising messages on this entrance. So certainly not all data is publicly accessible, as a result of in any other case else direct messages would simply not work!

It's true that looking at a blocking account from a blocked account on most social media programs or observing the outcomes of interactions can reveal details about who's blocked, however this is not the same as this being brazenly queryable data. But the lack of understanding of those detail by many customers and media coverage is a bit maddening from someone like myself who actually actually does look at and care about decentralization, and I do know it is a bit maddening to a lot of the fediverse too. That is actually a very good purpose, and account migration support is one thing we should see extra broadly (together with on the fediverse). There may be a big distinction between "you possibly can look at someone's publish and see who's being blocked" to "you can question the community for every individual who is blocking or is blocked by JK Rowling". The presumable answer is: Bluesky needed to supply a characteristic-complete platform from the perspective of a consumer who's on the lookout for an exit from Twitter now. And that is truthfully a good choice to make in some ways, since as I have mentioned beforehand, while I don't see Bluesky as an excellent decentralized Twitter, I do see it as a good substitute for Twitter, which is what most customers are in search of instantly.

I've already mentioned above that I'm glad the alternate has been a positive one and I'm grateful to see that my writing was properly obtained. ’ repositories contains a file of an interaction that shouldn't have been allowed due to the block, then the App View drops that interaction so that nobody can see it in the client apps. If you discover this shocking, so did I, but then again, this data was publicly out there even when direct messages were announced. It was our opinion that sharing such data might result in harassment. But blocks are indeed public data on Bluesky, and anyone can query who is blocking or being blocked by anyone. The issue, after all, is that this placeholder is now the idea of identifiers for many customers who've already joined the system right this moment. Who can participate here? Even though the majority of Bluesky providers are presently operated by a single company, we nevertheless consider the system to be decentralized because it provides credible exit: if Bluesky Social PBC goes out of business or loses users’ trust, other suppliers can step in to provide an equal service using the same dataset and the identical protocols.