It is built for the task, and assuming worse case scenario of sunset, it would be ingested into the Wayback Machine. Note that both the Internet Archive and Cloudflare are supporting partners (bottom of page).

(https://doi.org/ is also an option, but not as accessible to a casual user; the DOI Foundation pointed me to https://www.crossref.org/ for adhoc DOI registration, although I have not had time to research further)

afandian 3 hours ago | parent | next [-]

Crossref is designed for publishing workflows. Not set up for ad hoc DOI registration. Not least because just registering a persistent identifier to redirect to an ephemeral page without arrangements for preservation and stewardship of the page doesn’t make much sense.

That’s not to say that DOIs aren’t registered for all kinds of urls. I found the likes of YouTube etc when I researched this about 10 years ago.

	▲	toomuchtodo an hour ago \| parent [-]
		Would you have a recommendation for an organization that can register ad hoc DOIs? I am still looking for one.

▲

ruined a day ago | parent | prev | next [-]

perma.cc is an interesting project, thanks for sharing.

other readers may be specifically interested in their contingency plan

https://perma.cc/contingency-plan

▲

Hyperlisk a day ago | parent | prev | next [-]

perma.cc is great. Also check out their tools if you want to get your hands dirty with your own archival process: https://tools.perma.cc/

▲

whoahwio a day ago | parent | prev [-]

While Perma is solution specifically for this problem, and a good one at that - citing the might of the backing company is a bit ironic here

▲

toomuchtodo a day ago | parent [-]

If Cloudflare provides the infra (thanks Cloudflare!), I am happy to have them provide the compute and network for the lookups (which, at their scale, is probably a rounding error), with the Internet Archive remaining the storage system of last resort. Is that different than the Internet Archive offering compute to provide the lookups on top of their storage system? Everything is temporary, intent is important, etc. Can always revisit the stack as long as the data exists on disk somewhere accessible.

This is distinct from Google saying "bye y'all, no more GETs for you" with no other way to access the data.

▲

whoahwio a day ago | parent [-]

This is much better positioned for longevity than google’s URL shortener, I’m not trying to make that argument. My point is that 10-15 years ago, when Google’s URL shortener was being adopted for all these (inappropriate) uses, its use was supported by a public opinion of Google’s ‘inevitability’. For Perma, CF serves a similar function.

	▲	toomuchtodo a day ago \| parent [-]
		Point taken.