Re:Status.github.com: “We're failing over a data storage sys...
by Fuzzwah on Sunday October 21, 2018 @10:34PM
(#18271745)
It is to ensure that the updates get mirrored onto twitter, where exact duplicates can't be posted.
[ Parent
| on HN ]
Re:Status.github.com: “We're failing over a data storage sys...
by hiccuphippo on Monday October 22, 2018 @01:01AM
(#18272299)
Isn't it enough to delete the older tweet? Or maybe just add a timestamp to the message.
Off-Topic: If it's not possible to write a twit with the exact text from a deleted twit, then a way to prove someone wrote a twit and then deleted it would be to have them try to write it again.
Re:Status.github.com: “We're failing over a data storage sys...
by askmike on Monday October 22, 2018 @02:37AM
(#18272623)
Deleting tweets is a terrible workaround. Once github start tweeting and people start linking to those tweets they can't go ahead and delete them 50 minutes later..
Re:Status.github.com: “We're failing over a data storage sys...
by owl57 on Monday October 22, 2018 @06:54AM
(#18273588)
Re: off-topic:
You have to do it fast. You certainly can tweet a lot of identical tweets if you aren't in a hurry: there is a "Rock in the forest"[1] that tweets "Nothing happened today" (in Russian) every day for several years, and most of the time the text is exactly the same. Interestingly enough, the time of tweet varies widely from day to day, so it looks like a human or a program specifically made to imitate one.
Re:Status.github.com: “We're failing over a data storage sys...
by hnarn on Monday October 22, 2018 @04:21AM
(#18273007)
If you include a unique hashtag, would the message be considered unique? In that case, you could include the epoch timestamp as a hashtag :-)
Re:Status.github.com: “We're failing over a data storage sys...
by drb91 on Monday October 22, 2018 @05:19AM
(#18273240)
Or even just prefix the tweet with the update ordinal.