The Death of Infosec Twitter
11–20 of 89 posts
Re: The Death of Infosec Twitter
#12[flagged]
Re: The Death of Infosec Twitter
#13Re: The Death of Infosec Twitter
#14Has any of the OSINT/INFOSEC crowd moved to mastodon or somewhere other then twitter?
Re: The Death of Infosec Twitter
#15[flagged]
There are things I’ll give credit for. I suspect the “community notes” feature is overall beneficial (though I haven’t seen it much firsthand because I use a very outdated version of the application, which doesn’t support it.). Also, making the code for the recommendation algorithm publicly readable was very cool, and I appreciate it.
The way that verification was replaced with the current system, was, I think, rather poorly designed. That’s not to say that the critiques of the previous system were illegitimate. But the way the change was done threw the baby out with the bath water. Ideally, the system should work as follows: paying-users and associated features, should be independent of verification. Anyone should be able to pay a one-time (unless they change display name too much) fee to have their account verified, where this verification should be an actual verification, not just “did this person pay money”. (This might have to cost a fair chunk in order to be viable, due to labor costs of verifying, but I think it could still be reasonably cheap..) There could be an option for paying subscribers to have some icon display by their name, like the checkmark does currently, but this should be optional, and should be distinct from the verification icon.
Also, there’s all the stupid stuff, like blocking links to competitors, and seemingly not having a competent rollback system for updates when they break stuff, etc.
Re: The Death of Infosec Twitter
#16this is so sad rip
Re: The Death of Infosec Twitter
#17Has any of the OSINT/INFOSEC crowd moved to mastodon or somewhere other then twitter?
What about Threads? Isn't that supposed to be the Twitter-killer?
1. Both high quality and high quantity posts instantly available
2. Reasonable API access, maybe not directly but they want their niche workflows to be supported
3. Clear and consistent moderation. Eliminate disruptive content while giving reasonable people a clear understanding of whether something will be removed before they post it.
Threads has made vague promises to these three but not yet delivered.
Re: The Death of Infosec Twitter
#18Re: The Death of Infosec Twitter
#19Re: The Death of Infosec Twitter
#20Earlier quoted context omitted.
What about Threads? Isn't that supposed to be the Twitter-killer?
The people leaving Twitter want: 1. Both high quality and high quantity posts instantly available 2. Reasonable API access, maybe not directly but they want their niche workflows to be supported 3. Clear and consistent moderation. Eliminate disruptive content while giving reasonable people a clear understanding of whether something will be removed before they post it. Threads has made vague promises to these three bu…