@jb55 listened to a podcast you did a few months ago, where you talked about leveraging follow-packs as an on-boarding method. I think in second instance, follow-packs are a great thing, but new users should start at curated relay feeds first, instead of curated follows; The user selects interests, so showing them stuff that aligns with those interests is indeed what you want; but whether the user actually wants to follow those people or not is a second thing altogether; and if it turns out they don't, they are forced to take some action. Whereas with relays feeds, they just pick another feed and are not attached to anything; the only action the user is ''forced'' to make is this learning moment that they can change perspectives. You could always offer associated follow-packs consisting out of the npubs the relayfeed is made out of. With a relay feeds you can curate on the event level, instead of getting all of what npubs publish. Also, these topic-(sub-)relays could be read only, scraping stuff from other places; users interacting with those events will do so using outbox anyway.

Spring preview 2

Why do we go to the same places in order to interact and make sense of things, if we can just go to wherever the other person is, and make sense of things ourself? Nostr.

Spring preview

You almost had it, but i think you still missed a crucial insight. First let me just note that the whole 'dumb server' thing just relates to the handfull of query commands ensuring interoperability between every client and every relay. The expectation always was that relays would leverage the powerposition they are in (i.e. accepting events, and under what condition, retaining events, and under what condution, handing over events and under what condition). Second, and for my actual point: you mentioned that email centralized noting the reputation system. And THATS where the difference is. Its not just your ability to exit a server/relay, but the fact that insofar people are interested in you/npubs, the reputation of the relay does not matter at all. A relay could host the most terrible gore, spam and filth or whatever, and outboxing clients would still just fetch your nice catpicture posts, ignoring the crap just fine. Ergo, the reputation friction is not on the relay level, but on the user level. Good outbox implementations exist and as a result the relay, as such, does not matter (ofcourse things like latency, consistency, etc still do)

#asknostr Is someone working/has anyone worked on a Nostr-''onedrive''? I.e. take my local files, turn them into blossomblobs, create a Nostr event with all the relevant meta-data surrounding the file, such that i can go and fetch my stuff on other systems, and share files with others? I vaguely recall stuff like this

Obvious path is obvious; Ideas a being floated, bills are proposed and laws are being signed to force age verification on the OS level. Once you go the top-down permissioned route for safety the final stage is everyone ending up in a cage to account for all variables. This is the reason i am working on TEPP, to provide parents permissionless tools to create permissioned environments for their children (or agents/bots). Nostr keys at the OS level would be great, not just for this stuff, and TEPP would fit nicely; but it also means i just have to enter my keys/bunkerlink into the OS, and it can initialize with all my apps, settings and files right then and there.

Tom

California introduces age verification law for all operating systems, including Linux and SteamOS — user age verified during OS account setup

AB 1043 also requires OS providers to pipe a real-time age checker to every app developer who requests it.