< ^ txt
Sat Aug 8 06:00:02 EDT 2020
========================================
Slept from eleven-thirty to seven-thirty without waking.
Sunny.
Highs in the mid 80s.
South winds up to 10 mph.
TODO
----------------------------------------
- Work on new homepage
A bit.
Digital slacker/stainless steel rat web hosting.
Host stuff on any place free — Wordpress, Pastebin, Github Gist, whatever.
If a free service goes away, just publish on some other free service.
Keep a manifest file listing your resources and their URL's.
Publish a DNS TXT record with the URL for the manifest.
Use an alternative DNS root for totally free hosting?
Run a local proxy service to automatically assemble all this?
It would also be possible to publish a GPG key by DNS TXT to validate authorship of published stuff.
https://en.wikipedia.org/wiki/Alternative_DNS_root
So, very light.
Identity is only GPG signing.
A site is a DNS record and a manifest/index.
But that's shouting into the void.
What about responses?
Again, keep it light.
I always liked the dynamic of academics responding to each other's papers (sometimes decades after the original author died);
blog posts sometimes had the same dynamic.
Pingbacks were cool, though abusable.
Pingbacks should be public, so spectators can follow the conversation.
Is there any way to do pingbacks without a persistent or centralized service?
Maybe responses are opt-in.
In my client, I can "follow" someone by adding their domain to my list.
My agent periodically grabs their manifest, and scans all their content for links to my site.
My client notifies me if it finds any.
Like/Interesting/bookmark flags aren't integral to the idea; this could be a separate thing.
You just publish a list of URL's you flagged as interesting.
The URL to this list could be another DNS TXT record.
Servings: grains 7/6, fruit 1/4, vegetables 1/4, dairy 2/2, meat 1/3, nuts 0/0.5
Breakfast: cookies, Cheetos
Brunch: macaroni and cheese with tomatoes and sausage
Lunch: banana
Dinner: Cheetos
< ^ txt