Web devs: please, PLEASE, learn the difference between History.pushState() and History.replaceState(). It's the latter you want. Please do not spam my browser history just because I have interacted with your app; it's rude.
I get this issue on YouTube every time (well, other way). On mobile, go to front page, search, hit a search result. Go back and you're on the front page...
If Google can't get it right (or don't care to) I think it's a lost battle.
Well, the whole API is bad and the name is wrong. It has nothing to do with history, because you can ever only manipulate the top entries. You don't get an array of objects or simply some kind of list of URLs/ strings, you have to know the specific API to do head of stack manipulation basically.
And no, this has nothing to do with security. The browser could easily filter the list for same origin even with the list/ array approach. People just need to invent things that could've been just another data structure perhaps with some kind of Compare And Swap wrapper for concurrency.
In case somebody is a second class Internet citizen like me and has no IPv6 support yet, you can set up a tunnel courtesy of Hurricane Electric if you want to play around: https://tunnelbroker.net/
This is often tricky because not all home routers will let you set up the protocol forwarding you need.
Another option is to use a cloud provider that supports IPv6. For example Google's GCP gives you a completely free VM, the drawback is that enabling IPv6 is a bit of a puzzle. https://cloud.google.com/free/docs/free-cloud-features#compu... (create a dual-stack VPC with a dual-stack subnet in a region, add firewall rules, create dual-stack VM)
You can also use the one.one.one.one app from Cloudflare; only works on one machine at a time. Tunnelbroker's great, but streaming services consider it an untrusted VPN.
The sender address of a packet is specified by the sender. So the game would be the same, you would just encode the pixel data in a different area of the same packets. Security folks call this "spoofing" but its just an aspect of how networking works.
You can prevent spoofing by using HTTP requests or similar, instead of ICMP echo. Similar to https://ipv4.games/ (but with a canvas and color selection)
This reminds me of the IPv6 enabled Christmas Tree[1].Unsurprisingly, the original address has been offline. When I checked the archives, I saw the archives from January 7, 2017[2]. Could it be that some guy is celebrating Orthodox Christmas? :)
I thought I was just looking at a landing page and you had to use IPv6 to view the canvas yourself. I think someone just put Hubble deep field at (0,0), though. It looks different now.
Reminds me of the Pixelflut LED display. The hacker camp SHA2017 had one above a bar, 36C3 had one as well. Their traffic peaked at 4 Gbit/s and 30 Gbit/s respectively.
The "no drawing over others people drawings" rule seems kind of pointless, or is nobody supposed to use the website anymore, now that the whole site is covered with a drawing of cat and a lady in a pond?
Readit News
https://developer.mozilla.org/en-US/docs/Web/API/History/rep...
If Google can't get it right (or don't care to) I think it's a lost battle.
Also, pretty cool app!
And no, this has nothing to do with security. The browser could easily filter the list for same origin even with the list/ array approach. People just need to invent things that could've been just another data structure perhaps with some kind of Compare And Swap wrapper for concurrency.
Dead Comment
Another option is to use a cloud provider that supports IPv6. For example Google's GCP gives you a completely free VM, the drawback is that enabling IPv6 is a bit of a puzzle. https://cloud.google.com/free/docs/free-cloud-features#compu... (create a dual-stack VPC with a dual-stack subnet in a region, add firewall rules, create dual-stack VM)
Obviously it would be a really really big canvas but you could strip some leading or trailing bits.
(If we give 8x8 pixels per /64 and considering that only 2000/3 is used, that's 2^67 pixels)
- [1] https://news.ycombinator.com/item?id=13186051 - [2] https://web.archive.org/web/20171201000000*/http://ipv6tree....
I wanted to complain, but then I remembered the ol' Hacker News guideline:
> Please don't complain about tangential annoyances—e.g. [...] back-button breakage.
https://news.ycombinator.com/newsguidelines.html
https://hackaday.com/2020/08/01/playing-the-pixelflut/
https://pixeleb.be/