Elon Musk’s remaining staff have open-sourced Twitter. Or, at least, they’ve put some of the code onto GitHub.
This is the crucial-to-some ranking algorithm. It’s responsible for promoting tweets from people you’re not following and hiding stuff you might not want to see.
Or stuff Twitter doesn’t want you to see. In this week’s Secure Software Blogwatch, we ponder the unintended consequences of “transparency.”
Your humble blogwatcher curated these bloggy bits for your entertainment. Not to mention: Marty Cooper FTW.
Blue bird b0rked
What’s the craic? A week ago, Jon Brodkin reported — “Twitter obtains subpoena forcing GitHub to unmask source-code leaker”:
“On GitHub for months”GitHub user “FreeSpeechEnthusiast” posted Twitter source code in early January, shortly after Elon Musk bought Twitter and laid off thousands of workers. Twitter reportedly suspects the code leaker is one of its many ex-employees.…With the subpoena now issued, GitHub has until April 3 to provide all identifying information, “including the name(s), address(es), telephone number(s), email address(es), social media profile data, and IP address(es), for the user(s) associated with” the FreeSpeechEnthusiast account. GitHub was also ordered to provide the same type of information on any “users who posted, uploaded, downloaded or modified the data” at the code repository posted by FreeSpeechEnthusiast.…The code was apparently on GitHub for months before Twitter executives became aware of the leak. … Twitter executives are concerned “that the code includes security vulnerabilities that could give hackers or other motivated parties the means to extract user data or take down the site.”
Is ..
Support the originator by clicking the read the rest link below.
