Nitter is an alternative frontend for Twitter/X. It's been around for a while, but its instances been slowly dying off due apparently to Twitter API changes and/or extreme rate-limiting. As of the time of writing, it's still around, but barely - only one or two(!) of the 55 instances listed at https://status.d420.de work at any given time.
This market resolves NO if it is possible for me to view at least one tweet using Nitter on or after Sunday, March 31, 2024 (which is Easter). I will check the instances listed on status.d420.de that are marked as "healthy" and/or have a checkmark in the "RSS" column until I find one that works, just to be sure. Resolves YES if no such instances work on March 31, 2024. Resolves early to YES if all instances are simultaneously marked as dead on status.d420.de at any point before March 31, 2024, and at least 5 instances I check don't work. As with my other markets, this one destroys N/A if humanity is destroyed as a whole before Nitter is destroyed specifically.
To avoid April Fool's Day-related hijinks, I will not resolve this on April 1st, 2024, no matter what else might happen on that day.
EDIT: fixed directionality to match title (thanks @thiagovscoelho!)
Related questions
🏅 Top traders
| # | Name | Total profit |
|---|---|---|
| 1 | Ṁ173 | |
| 2 | Ṁ148 | |
| 3 | Ṁ133 | |
| 4 | Ṁ31 | |
| 5 | Ṁ26 |
@duck_master in case of rate-limiting being intermittent on resolution day, does resolution depend merely on whether you can view tweets upon the first attempt you make on or after March 31st? Or will you continue to retry over the day and resolve NO if it works even once?
@duck_master over what timeframe? As many attempts as you feel like making on March 31st in a specific timezone? If so, which timezone?
Trying to rule out the possibility that you attempt for many days after market close, for example.
@chrisjbillington As I specified in the description, I will try at least 5 instances before resolving YES. If anything Nitter works on resolution day (likely it'll come down to nitter.privacydev.net/ESYudkowsky I think), I will stop early and resolve this NO instead.
As a sidenote, I think this market is almost certainly down to whoever has privacydev.net as their personal website.
... I was almost gonna resolve this YES, but nitter.privacydev.net just sputtered back to life in time. (Here's a screenshot.) Also, FYI, I'll still check instances if the "healthy" column is marked with "❓".
@duck_master But your condition said "Resolves early to YES if all instances are simultaneously marked as dead on status.d420.de at any point before March 31, 2024, and at least 5 instances I check don't work." Didn't that happen?
@HarrisonNathan Oh, nevermind, I understand. Should have read "all 5 instances" instead of "at least 5" but that's the only reasonable interpretation.
To be clear: I checked nitter.privacydev.net and it worked, so I stopped there.
(To be clear: I'll count an instance as "dead" if it shows me the rate-limiting thing after I look up a profile and/or is a 404, and if status.d420.de lists it as either crossed out or a question mark in both the "Healthy" and "RSS" columns.)
Important to note that the project is still being discussed at github, just in a different direction, either focused solely on RSS or sharing data between instances, which should cause each individual account being used for nitter to access twitter less often, potentially making the project viable again without the guest account method.
Really stupid of Elon to just ruin twitter without any reason except that he fired >half his staff and has since flailed about wildly without a hint of competence in his losing war against bots and scrapers.