< ^ txt
Tue Jun 21 06:00:01 EDT 2022
========================================
Slept from nine to six.
Mostly sunny.
Highs in the mid 90s.
West winds 5 to 10 mph increasing to 10 to 15 mph in the late morning and afternoon.
# Work
CTO standup call, AWS training.
# Home
Ten-minute walk in the morning before work.
Pale moon in the blue sky.
Already getting hot, but not yet unbearable.
Heard a mourning dove.
https://lobste.rs/s/m5d4xo/old_school_blogging_retro_computers
> I’m doing a lot of work on decentralized blogging (i have a pre-alpha protocol and implementation), but IMO, looking back to old-school blogging is the wrong direction.
>
> True decentralization has to start at the architecture and design level, and blogging just built on the normal Web 1.0 stack, so it was only decentralized in that personal websites are independent of each other. But setting up and running your own website is nontrivial. So the vast majority of bloggers used hosted systems like Blogger or LiveJournal or WordPress.com. That’s no longer decentralized IMO. Same is true of Mastodon et al. You have to give up a lot of trust and control to whomever runs your server. And the more “social” features like comments and pings were never secure and so were very vulnerable to spam.
>
> Truly decentralized blogging has to build from a secure P2P architecture, even if it’s not strictly run that way. Servers can and will exist, but their role is to help with discovery, connectivity and availability; they should have nothing to do with trust or identity — that’s controlled by the peer and the user, using cryptography. Scuttlebutt is an example of a system like this.
Servings: grains 6/6, fruit 2/4, vegetables 2/4, dairy 2/2, meat 4/3, nuts 1/0.5
Brunch: banana, tomatoes, cucumber, two hot dogs, coffee
Lunch: apple, egg and bean sandwhich
Afternoon snack:
Dinner: Chinese
< ^ txt