Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I Made a Self-Quoting Tweet

oisinmoran.com

Post reply on HN
Print view View original

101–110 of 145 posts

Re: I Made a Self-Quoting Tweet

#101

Post by est31 »

cortesoft wrote: post #98
estebank wrote: post #96

Earlier quoted context omitted.

What you're seeing is an available tweet with an embedded tweet that is kept from being displayed. Because the embedded tweet is itself, it is handled by showing the same UI as any embedded tweet that is not available.

Right, but my point is the behavior is the same on Twitter and nitter

"tweet unavailable" is a different error from the "This is not available to you" message. Got that message earlier today when I tried to open a different linked tweet. Changing to nitter fixed it for me.

Re: I Made a Self-Quoting Tweet

#102

Post by nullsense »

meowface wrote: post #77
OisinMoran wrote: post #75

Earlier quoted context omitted.

The tweet Closi is referring to: https://twitter.com/noradio/status/1333558513314922497

And the content, for anyone too lazy to click: Commenter >what's really amazing is that twitter programmers thought about this edge case and made sure the tweet would not display itself Twitter Engineer >We didn't think of this edge case. Someone did this about 7 years ago and the recursive hydration would make a tweet service crash by simply loading the tweet in a browser. It took a principal engineer an entire day…

TIL: debugging via memory dumps is a Principal Engineer level skill.

Anyone here actually do this? I read about it in Release It and it sounds by far like the closest thing there is to a super power when it comes to solving production incidents. I've never actually seen anyone do it though.

Recently saw a video on this technique from Dotnet Conf. Piqued my curiosity again, and now this. I've really gotta learn this.

Re: I Made a Self-Quoting Tweet

#103

Post by voltagex_ »

nullsense wrote: post #102
meowface wrote: post #77

Earlier quoted context omitted.

And the content, for anyone too lazy to click: Commenter >what's really amazing is that twitter programmers thought about this edge case and made sure the tweet would not display itself Twitter Engineer >We didn't think of this edge case. Someone did this about 7 years ago and the recursive hydration would make a tweet service crash by simply loading the tweet in a browser. It took a principal engineer an entire day…

TIL: debugging via memory dumps is a Principal Engineer level skill. Anyone here actually do this? I read about it in Release It and it sounds by far like the closest thing there is to a super power when it comes to solving production incidents. I've never actually seen anyone do it though. Recently saw a video on this technique from Dotnet Conf. Piqued my curiosity again, and now this. I've really gotta learn this.

I have done it once successfully in 10 years (.NET dev). Would recommend having any other kind of logging or instrumentation in place so you don't have to do it. It's still worth learning WinDbg and sosclr.

Re: I Made a Self-Quoting Tweet

#104

Post by voltagex_ »

nullsense wrote: post #102
meowface wrote: post #77

Earlier quoted context omitted.

And the content, for anyone too lazy to click: Commenter >what's really amazing is that twitter programmers thought about this edge case and made sure the tweet would not display itself Twitter Engineer >We didn't think of this edge case. Someone did this about 7 years ago and the recursive hydration would make a tweet service crash by simply loading the tweet in a browser. It took a principal engineer an entire day…

TIL: debugging via memory dumps is a Principal Engineer level skill. Anyone here actually do this? I read about it in Release It and it sounds by far like the closest thing there is to a super power when it comes to solving production incidents. I've never actually seen anyone do it though. Recently saw a video on this technique from Dotnet Conf. Piqued my curiosity again, and now this. I've really gotta learn this.

Any chance you remember which video this was? I can't see it in the dotnet conf 2020 playlist.

Re: I Made a Self-Quoting Tweet

#105

Post by viraptor »

nullsense wrote: post #102
meowface wrote: post #77

Earlier quoted context omitted.

And the content, for anyone too lazy to click: Commenter >what's really amazing is that twitter programmers thought about this edge case and made sure the tweet would not display itself Twitter Engineer >We didn't think of this edge case. Someone did this about 7 years ago and the recursive hydration would make a tweet service crash by simply loading the tweet in a browser. It took a principal engineer an entire day…

TIL: debugging via memory dumps is a Principal Engineer level skill. Anyone here actually do this? I read about it in Release It and it sounds by far like the closest thing there is to a super power when it comes to solving production incidents. I've never actually seen anyone do it though. Recently saw a video on this technique from Dotnet Conf. Piqued my curiosity again, and now this. I've really gotta learn this.

The fact the principal engineer was doing this does not mean doing this is a principal engineer skill. There's lots of software engineers who can deal with coredumps which is pretty much the same idea.

Re: I Made a Self-Quoting Tweet

#106

Post by slyall »

showerst wrote: 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.

Way back (probably around 2000) I created a Usenet News message that referenced itself (pretty trivial).

Turns out that a bunch of news reading software didn't like this and crashed when it tried to load that newsgroup.

Re: I Made a Self-Quoting Tweet

#108

Post by enw »

nullsense wrote: post #102
meowface wrote: post #77

Earlier quoted context omitted.

And the content, for anyone too lazy to click: Commenter >what's really amazing is that twitter programmers thought about this edge case and made sure the tweet would not display itself Twitter Engineer >We didn't think of this edge case. Someone did this about 7 years ago and the recursive hydration would make a tweet service crash by simply loading the tweet in a browser. It took a principal engineer an entire day…

TIL: debugging via memory dumps is a Principal Engineer level skill. Anyone here actually do this? I read about it in Release It and it sounds by far like the closest thing there is to a super power when it comes to solving production incidents. I've never actually seen anyone do it though. Recently saw a video on this technique from Dotnet Conf. Piqued my curiosity again, and now this. I've really gotta learn this.

How else do you debug C/C++ programs that crash?

Re: I Made a Self-Quoting Tweet

#109

Post by cortesoft »

est31 wrote: post #101
cortesoft wrote: post #98

Earlier quoted context omitted.

Right, but my point is the behavior is the same on Twitter and nitter

"tweet unavailable" is a different error from the "This is not available to you" message. Got that message earlier today when I tried to open a different linked tweet. Changing to nitter fixed it for me.

Ah, I get tweet unavailable from both, thus my confusion.

Re: I Made a Self-Quoting Tweet

#110

Post by patates »

anonytrary wrote: post #40
eyelidlessness wrote: post #21

Earlier quoted context omitted.

But you wouldn’t do that if your assumption is that the graph doesn’t cycle. Edit: child comments are correct and I regret my oversight

Graph doesn't need to cycle to hit a node twice. Good code does not visit the same node twice.

When doing recursion (Postgres recursive CTE) I keep a path on the latest edges and check to see new edges aren't already visited, so same nodes can appear in multiple branches but not on the same branch. Works flawlessly.
Post reply on HN