41–50 of 125 posts
Earlier quoted context omitted.
The search results counter is 12,385...is that really all (or "nearly all") of what Vid.me had for content? I mean I know it failed at dethroning Youtube, but 12,000+ videos is barely anything.
That's roughly one hour of new uploads on YouTube as of 2016.
Earlier quoted context omitted.
SRI/hashing works for static content. Though it's worth mentioning it's a SUB-resource feature (images, scripts, etc.). It doesn't work for hyperlinks to other pages. Even if it did, it's a different use case. Say I link to an article by Author A that has comments in it (or even a footer, relative timestamp, sidebar, etc.). Hashing won't work as the page is always changing. I want the link to always go to Author A bu…
Good points. I would guess that for something to be implemented, it would have to be easy for browsers and API tools to check once per domain and cache the response and should probably be something that already exists and has been adopted. Maybe a page could have a meta tag or header that contains a hash of the destination sites DANE signature? Something like "targetref:somedomain.tld expectsig:39726a2fe2bb052cf00e6b…
Earlier quoted context omitted.
On mine, I can pay for up to 10 years, but I think I can just pay twice and get 20. Edit: It seems to vary. Some places cite an ICANN limit of 10 years.
Most registries limit domain lifetimes to 10 years. You can't renew a domain if doing so would put the lifetime beyond 10 years -- the registry will refuse to perform the operation.
We can't and shouldn't expect people to keep their old domains forever. We need a way for pages to be signed and hyperlinks to enforce authorship. When we link to stuff, we should have a way to say whose stuff we're linking to. It's no different from installing signed software and using trusted repositories. This is one of the reasons I created a proof-of-concept web extension that verifies links and pages using PGP.…
One solution is to have a unique URI per file that is independent of DNS. Decentralized file storage (e.g. FileCoin / IPFS) might serve this purpose...
Also, while IPNS covers the issue of linking to dynamic content, it's worth mentioning IPFS will have similar issues with DNS as DNSLink and similar domain-driven solutions are used to cover its usability issues (long, random URIs).
Earlier quoted context omitted.
Most registries limit domain lifetimes to 10 years. You can't renew a domain if doing so would put the lifetime beyond 10 years -- the registry will refuse to perform the operation.
Clearly there are companies that offer extension as a service, you pay 20 times as much and they promise to extend your domain 10 times.
We can't and shouldn't expect people to keep their old domains forever. We need a way for pages to be signed and hyperlinks to enforce authorship. When we link to stuff, we should have a way to say whose stuff we're linking to. It's no different from installing signed software and using trusted repositories. This is one of the reasons I created a proof-of-concept web extension that verifies links and pages using PGP.…
In a lot of the peer-to-peer distributed hash table designs, all you need to retrieve a file is its hash.
At least it's only pr0n. As a vector for malware / spyware injection, this could be even more interesting.
Relevant xkcd, of course: https://xkcd.com/1698/
h/t Elda King @ Mastodon https://weirder.earth/@eldaking/106626603001624730
4 years ago, Archive Team backed up "nearly all" of Vidme (according to Jason Scott). It was uploaded to the Internet Archive here https://archive.org/details/archiveteam_vidme so you can fix your vid.me URLs by pointing them to the Archive. (And you can help keep them there, too https://archive.org/donate But honestly, using the Archive more keeps the bigger donors involved, so don't feel guilty or anything. Just us…