"We've known for a while that the Internet has ossified as a result of the race to optimize existing applications or enhance security" -- this paper from 2011 is the earliest academic reference I can find to Internet protocol ossification https://dl.acm.org/doi/10.1145/2068816.2068834

gm, thinking of ways a client can bootstrap a list of relays and test that they're minimally trustworthy in some way. maybe we end up defaulting to nip-05 relay recommendations - if that happens, would providers injecting their own relays into a user's records be helpful or viewed as an attack vector? maybe a canary bot that tries to send restricted samizdata - 3D PDW files, politcally sensitive speech, financial transactions to blacklisted addresses - through a list of relays and testing end-to-end delivery would be useful?

"Further resentment was created on the Net side by AOL's habit of advertising itself as "the Internet, and a whole lot more," further confusing where the boundary, if any, might lie...." Re-reading Chapter 3 of Wendy Grossman's net.wars, starts off with a bang:

I've added the word 'canary' to the description field for for wss://nostr.relayer.se. So, if for some reason, you wanted to run this command in your terminal: curl -H 'Accept: application/nostr+json' https://nostr.relayer.se ...and check whether the word 'canary' is in the description, or if the word 'canary' was for some reason removed? You can do that now.

The real flippening is upon us: as of today my expectations are that I'll encounter more random bugs when using Twitter than any given Nostr client.

gm, I'm almost at the point where I can talk about the Eagles Super Bowl loss. Almost.

Finally set up my lud16 address, just gonna start zapping randos

eep, had a busy couple of days away from nostr and somehow lost all my follows? adding errybody back now....

A semantic interpretation that I'm coming around to as I work through Clark's 'Designing an Internet': if you're not running your own autonomous system, peering with other ASs, and administering your own DNS servers *at minimum*, then it isn't reasonable to consider yourself an 'Internet user'. Most people who think of themselves as 'Internet users' are actually *customers* of Internet users - it's the ISPs that are actually using the Internet, and their customers are getting exactly as much access to the Internet (read: Netflix, Gmail, social media) as the ISPs deem acceptable.

me: ordinals pass the bar for rough consensus and running code, you can do as you please with your sats, there are no protocol police also me: the decline of usenet began when users figured out how to use it to store data

Tedium: The Dull Side of the Internet.

Usenet History: How Binaries Took Over Newsgroups

How Usenet—a protocol intended for conversations—was forever changed once the public figured out you could transfer binary files through it.

Question for relay users (so, everyone on nostr): So far I've been focusing on making my relay as private as possible - Onion Hidden V3 Service, running in njal.la, top level domains registered in privacy friendly jurisdictions, etc. What other features would you like to see in a privacy-focused relay?

If you're a nostr client developer looking to play around with a relay that's available as a Tor Onion v3 Hidden Service: wss://nostr.relayer.se in clearnet is now also reachable at: geeafhmczfy5jmfc36ud2vgfotsrdnc2vwrp2kczjka4afx42quc3qqd.onion

I wonder if there's any inteset in something like moa.party but for crossposting tweets a set of nostr relays instead of mastodon toots

GitLab

FedStoa / moa · GitLab

New home of Moa. Cross post between Mastodon, Twitter, and Instagram. Original repo on GitHub