3M electric toothbrushes were not used in a DDoS attack(bleepingcomputer.com)
bleepingcomputer.com
3M electric toothbrushes were not used in a DDoS attack
https://www.bleepingcomputer.com/news/security/no-3-million-electric-toothbrushes-were-not-used-in-a-ddos-attack/
2 comments
Comments moved thither. Thanks!
Can you help me understand the problem that cropped up with that original URL? as described at https://news.ycombinator.com/item?id=39296868 and https://news.ycombinator.com/item?id=39305426?
Can you help me understand the problem that cropped up with that original URL? as described at https://news.ycombinator.com/item?id=39296868 and https://news.ycombinator.com/item?id=39305426?
As proactivesvcs commented under the other article, I think it was just insufficient down-scrolling. The Mastodon web UI on a phone can make for a very long page.
Edit: wait a sec... something IS weird here
I now have the same URL showing in two different tabs, one of which shows the follow-up and one which does not. It's a UI matter of which part of the tree of follow-ups is being displayed, and it's not encoded in the URL.
(Still editing) OK, if you are in the state where it does not show the entire thread down to the finale, click on the text of the first follow-up by the OP ("The toothbrush thing has gone viral despite it being total bollocks") and the rest of the thread is revealed.
Except it's not. That's another part of the tree with the same screenshot in reply to a different subthread.
All this goes to show that I don't understand how the web UI of Mastodon works, and I'm not alone. "When you're in a hole... stop digging"
(I didn't stop digging)
Starting at https://cyberplace.social/@GossiTheDog/111886558855943676
First reply is from the OP, and the visual "thread" (vertical line) on the left side is broken. Click on that reply ("The toothbrush thing has gone viral despite it being total bollocks.").
Now again scroll down through posts by the OP until the "thread" on the left side breaks. Click on that last reply ("Fortinet also declined to comment to me.").
Finally, the target post appears as a reply to that ("Fortigate have issued me a statement.")
Navigational issue. One might ask what is the difference between the follow-ups that show up automatically and the ones that don't show up until you navigate. I don't know.
Edit: wait a sec... something IS weird here
I now have the same URL showing in two different tabs, one of which shows the follow-up and one which does not. It's a UI matter of which part of the tree of follow-ups is being displayed, and it's not encoded in the URL.
(Still editing) OK, if you are in the state where it does not show the entire thread down to the finale, click on the text of the first follow-up by the OP ("The toothbrush thing has gone viral despite it being total bollocks") and the rest of the thread is revealed.
Except it's not. That's another part of the tree with the same screenshot in reply to a different subthread.
All this goes to show that I don't understand how the web UI of Mastodon works, and I'm not alone. "When you're in a hole... stop digging"
(I didn't stop digging)
Starting at https://cyberplace.social/@GossiTheDog/111886558855943676
First reply is from the OP, and the visual "thread" (vertical line) on the left side is broken. Click on that reply ("The toothbrush thing has gone viral despite it being total bollocks.").
Now again scroll down through posts by the OP until the "thread" on the left side breaks. Click on that last reply ("Fortinet also declined to comment to me.").
Finally, the target post appears as a reply to that ("Fortigate have issued me a statement.")
Navigational issue. One might ask what is the difference between the follow-ups that show up automatically and the ones that don't show up until you navigate. I don't know.
Yeah I definitely scrolled to the end... thanks - I'll check back here in a bit :)
Edit: thanks for doing all that so the rest of us didn't have to.
Edit: thanks for doing all that so the rest of us didn't have to.
More discussion: https://news.ycombinator.com/item?id=39281939
https://news.ycombinator.com/item?id=39296438