Ivan MoscosoIt looks like #threads is relying heavily on instagram's internals. Text for posts & replies are 'caption' attributes.
Miss_Aranel
- 4 Followers
- 42 Following
- 43 Posts
Baltimore, UK, Japan. Interested in news of the day with a focus on law, theology, immigration, anti-fascism & ex-evangelical/homeschool. Loves art, literature, nature, video gaming, & film.
KreigThe Zuck suck is in full swing. In the few short hours since I started using #Threads, #DuckDuckGo has already blocked over 200 data tracking attempts. These include things like "headphone status" and "screen density."
EDIT for clarity: The 200+ attempts *may* have been overcounted as DDG hadn't tooled their VPN for Threads yet.
#DataPrivacy #Meta #ThreadsApp
EDIT: To anyone who is using this post to bash anyone and everyone who is using Threads, please read this https://writing.exchange/@kreig/110673494921536371
Kreig Durham (@[email protected])
Since my post about the #DuckDuckGo app and #Threads is still getting lots of attention, I want to be clear about how I actually feel about #DataPrivacy. It's a lot like #recycling. Yeah it's a good thing to protect your own personal data, but if we're being honest, it's not effective on an individual scale. We need good legislation at a national level to meaningfully change the game for the benefit of us all. Until then, no matter how careful you are, you're still being negatively affected.
Darnell Clayton 
Threads by Instagram will launch on July 6th (thanks for the heads up @dansup!) & I noticed Meta collects a lot of data. So much data!
Threads is rumored to adopt ActivityPub later on (in October maybe‽ We will see), but when it joins the Fediverse (if not on launch day), it’s data collection policies will make it easier to convince some (but not all) to migrate over to Misskey, Pixelfed, Mastodon & Pleroma.
Note: Uploading on Misskey as my Mastodon account @darnell is being fixed server side right now.
#Threads #Instagram #Meta #Facebook #Misskey #Pixelfed #Mastodon #Pleroma
Threads is rumored to adopt ActivityPub later on (in October maybe‽ We will see), but when it joins the Fediverse (if not on launch day), it’s data collection policies will make it easier to convince some (but not all) to migrate over to Misskey, Pixelfed, Mastodon & Pleroma.
Note: Uploading on Misskey as my Mastodon account @darnell is being fixed server side right now.
#Threads #Instagram #Meta #Facebook #Misskey #Pixelfed #Mastodon #Pleroma
Babs 💙🐝⌛️🦋🔻@sysop408 This looks like a good explanation. https://threadreaderapp.com/thread/1675331352584134658.html
John Minnihan@mmasnick my current theory is that someone was told to limit any use of the API (in the [x]/api namespace) so they did something truly clownish like throw a regex match on all incoming api requests to return a 429, which is a legit rate limit status code.
if you look at all those requests when loading /home, you'll see that /home fails because it uses /i/api/[x] while /notifications loads because it is a first-class endpoint of its own.
i really think this is as ridiculous as a regex.
SheldonSo I had a really fun day writing up about Twitter trying to DDOS itself. I didn't expect it to blow up the way it did here, but even more amusing is that someone took a screenshot of that post and cross-posted it to Twitter and now that post is blowing up on Twitter too!
Poor Twitter. Can't catch a break. It's down and even the holdouts want their turn to give it a good kick.
Update: I have to add a screenshot of that screenshot because someone just reminded me that most people can't view the tweet unless they have a Twitter account to login to. It's ironic of me to forget because that's how today's circus got started.
It also shows how a seemingly innocent change like this can snowball into an avalanche of unintended consequences.
Anyway, 4500 retweets later and the party continues.
Hahaha back in my moderator days the only time the owner would do stupid shit like this is when *he* caused something to break really bad and didn't want to admit his mistake. DDOSing yourself though, whew boy! 
This is hilarious. It appears that Twitter is DDOSing itself.
The Twitter home feed's been down for most of this morning. Even though nothing loads, the Twitter website never stops trying and trying.
In the first video, notice the error message that I'm being rate limited. Then notice the jiggling scrollbar on the right.
The second video shows why it's jiggling. Twitter is firing off about 10 requests a second to itself to try and fetch content that never arrives because Elon's latest genius innovation is to block people from being able to read Twitter without logging in.
This likely created some hellish conditions that the engineers never envisioned and so we get this comedy of errors resulting in the most epic of self-owns, the self-DDOS.
Unbelievable. It's amateur hour.
#TwitterDown #MastodonMigration #DDOS #TwitterFail #SelfDDOS
Lest anyone doubt that Twitter was idiotic enough to release code that would cause a race condition and result in its own users executing a DDOS attack on it, here's the network console readout from Firefox showing all the network requests blasting away.
Of course I immediately closed out my connection because I'm a good person.
...but wait! It's the weekend and Evil Sheldon is in control so I kept the party going for a while since Twitter insisted on it.
#TwitterDown #Twitter #MastodonMigration #DDOS #TwitterFail #SelfDDOS
Missing The PointBreaking: US Coast Guard detects “banging” noises from hermetically-sealed Twitter.