This is also why you see Chome being used as a core in all kinds of applications and frameworks - AFAIK it has the necessary API for this.
Another issue would be permissions: if I wanted to restrict access to a file to a subset of users, I’d have to make a group for that subset. Linux supports a maximum of 65536 groups, which could quickly be exhausted for a nontrivial number of users.
That way, when you need to use sed for editing text containing it, your pattern can be more interesting:
sed 's/SSH\/HTTP\/3/SSH over HTTP\/3/g' sed 's:SSH/HTTP/3:SSH over HTTP/3:g'
At least with GNU sed, you can use different separators so dodge the need for exscaping. | works as well.That actually seems just as bad to me, since the URL often has enough data to figure out what was being pointed to even if the exact URL format of a site has changed or even if a site has gone offline. It might be like:
kmart dot com / product.aspx?SKU=12345678&search_term=Staplers or /products/swingline-red-stapler-1235467890
Those URLs would now be dead and kmart itself will soon be fully dead but someone can still understand what was being linked to.
Even if the URL is 404, it's still possibly useful information for someone looking at some old resource.
Some banking apps just work - two with warning on first launch, and one just doesn't care at all.
Two refuse to run and I have an old unrooted phone for them. Resulting in me being a good customer of those three banks that are not fussy.
So try and see, perhaps things just work!