paulgorman.org

< ^ txt

Sat Nov 20 06:00:01 EST 2021 ======================================== Slept from midnight to seven. Cloudy. Highs in the lower 40s. South winds 5 to 15 mph. ## To Do * ✓ 4 PM pick up groceries * ✓ play with Theuth https://github.com/fiatjaf/nostr > The simplest open protocol that is able to create a censorship-resistant global "social" network once and for all. > It doesn't rely on any trusted central server, hence it is resilient; it is based on cryptographic keys and signatures, so it is tamperproof; it does not rely on P2P techniques, therefore it works. > Everybody runs a client. It can be a native client, a web client, etc. To publish something, you write a post, sign it with your key and send it to multiple relays (servers hosted by someone else, or yourself). To get updates from other people, you ask multiple relays if they know anything about these other people. Anyone can run a relay. A relay is very simple and dumb. It does nothing besides accepting posts from some people and forwarding to others. Relays don't have to be trusted. Signatures are verified on the client side. Not sure why they're doing this with websockets and subscriptions. Maybe it gains some performance benefits, but it make design of clients and servers substantially more complicated. Maybe then intend for the cadene of sending and receiving to be more chat-like than blog-like, or at least ot allow for that use. You'd have to be careful to prevent abuse of relays. Imagine a relay implementation that was kind of only did caching, a bit like [the null pointer](https://ttm.sh/). Cache management options might include: * Limit the total outbound bandwidth per day or month. * Limit the total inbound bandwidth per day or month. * Limit the maximum upload amount per day per signature/user. * Limit maximum upload amount per day per IP address. * Limit the total data stored, stop accepting new uploads until old things expire out of the cache. * Count the number of downloads of a resource. Resources with a low download count might be deleted after some time. * Note the most recent download of a resource. Resources that have not been downloaded in a long time might be deleted. Servings: grains 5/6, fruit 1/4, vegetables 3/4, dairy 3/2, meat 2/3, nuts 0.5/0.5 Brunch: cheese curls Lunch: carrots, orange Afternoon snack: frozen pizza, green tea Dinner: ice cream, soba noodles with broccoli and peanut sauce

< ^ txt