Live data from Hacker News

I Made a Self-Quoting Tweet

oisinmoran.com

61–70 of 145 posts

Re: I Made a Self-Quoting Tweet

#61
post #54

Earlier quoted context omitted.

This is actually much cooler in my opinion! I love your progress indicator too. How did you go about doing this one? And what are the four parts you are referring to? Do you think a 3-cycle is doable?

AFAIK the tweet id has four moving parts, a datacenter id, a worker id, a sequence number, and a timestamp (original poster mentions three). 3-cycle is definitely doable, it may take a week posting 100 tweets per hour or something like that. The biggest problem is twitter blocking the account (even when you stay under the API rate limit). Code is here if you are interested, I ran it using GitHub Actions: https://gith…

Ooh that's very interesting! I've just presumably subsumed one of those into one of the others.

Seems like there's a cycle-3 game of life creature called a pulsar that would be perfect for this: https://en.wikipedia.org/wiki/Conway%27s_Game_of_Life#/media...

Re: I Made a Self-Quoting Tweet

#64
post #17

To save people some time, here’s the tweet: https://twitter.com/quinetweet/status/1309951041321013248 In essence, the approach was: * Find out what the tweet id is of a recent tweet * Find out what a tweet is shortly after * Estimate the rate of new tweets appearing * Publish a tweet with a reference to a tweet with a now+guess id The write up is well done and interesting but a little long winded.

Thank you! The reason for experimenting with a sort of blow-by-blow report style here and detailing the full and true journey of the idea was that I feel the whole process from idea to artifact is not written about enough. That said, it can often be hard to fully pinpoint the actual inception of an idea and just thinking about this one yesterday I realised that the idea likely came up while traversing a long chain of…

I loved the write up, especially those basic things all experienced programmers know but sometimes makes newer ones scared, like sometimes you don't quite know how the answer works exactly at first, or sometimes you have a big idea and a lack of double quotes is your problem, etc etc

Re: I Made a Self-Quoting Tweet

#65

I especially enjoyed the M.C. Escher Drawing Hands background you chose for your Twitter account.

Thank you! It's quite apt isn't it? I'm a really big fan of his and have a print of his Tetrahedral Planetoid on my wall!

Although the self-drawing hands are probably more apt for this even more Escher themed one that I've since been made aware of from the author in the comments here: https://twitter.com/mauritscorneIis/status/12668346972560875...

Re: I Made a Self-Quoting Tweet

#66
post #48

Earlier quoted context omitted.

sure, if you want to give your twitter credentials to some random company based in the caribbean.

What? https://nitter.net/quinetweet/status/1309951041321013248 doesn’t ask for credentials and AFAIK there’s no place to enter them on the whole site, unless you type them into the search bar.

It still shows up as "tweet unavailable" for me, though, in this link

Re: I Made a Self-Quoting Tweet

#69
post #5

> And for anyone at Twitter who was depending on the network of tweets being a Directed Acyclic Graph, I'm so terribly sorry. I love the idea that there's someone out there with code that resolves retweet chains recursively, who's about to be in for a great head scratcher of a bug.

Recursion isn't the problem. Not keeping track of seen tweets is the problem. Recursion can be used to detect cycles and traverse a cyclic graph in a way that doesn't blow up.

Irritation would probably better in terms of not blowing up your memory requirements. Just keep hashes of all visited nodes and a stack or queue of to-be-visited nodes and loop until you have no more to-be-visited nodes.

Re: I Made a Self-Quoting Tweet

#70
>Fundamentally the challenge is just correctly guessing what ID a given tweet is going to get, then appending that onto the URL for our profile and tweeting it.

Reminds me of that program for referring to a future git commit, which operates on the same principle: iterate through guesses of the future commit’s hash prefix until you have a (long enough prefix-)collision.

https://github.com/hundt/git-time-travel

Post reply on HN