writing a tweet deleter, ran into issue where the lib I was using, their api wrappers would return the response on 200 or throwM it on 4xx
-
-
Replying to @alicemazzy
thus halting. which sucks because I don't want to have to do two api calls to check every id first, and I want to run it overnight
1 reply 0 retweets 1 like -
Replying to @alicemazzy
so I'm like, ok, read about Control.Monad.Catch, cool I'll just catchAll with (\_ -> pure ()) whatever who cares
2 replies 0 retweets 1 like -
Replying to @alicemazzy
there are already apps / services that do this ICYDK. Unless you're tryna delete tweets based on criteria or something
1 reply 0 retweets 0 likes -
-
Replying to @BrennerSpear
I generally don't like giving read/write to random third parties tbh. regardless I already finished it anyway so
1 reply 0 retweets 1 like -
Replying to @alicemazzy
I think about the most damage they could do if malicious and... doesn't seem like that much. As long as no access to DMs
1 reply 0 retweets 0 likes -
Replying to @BrennerSpear @alicemazzy
would you mind sharing the repo w me?
1 reply 0 retweets 0 likes
it isn't anything special, I already have a list of the ids I want so I'm just looping through them https://github.com/alicemaz/twdelete …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.