Ah got it, it's under the notification tab. One has to tap at the top. 🤗

Is this again for the google version only? I can't seem to find it.

KM! Ela, ela! 🚀

Any hardware wallet seems to be a bigger security risc than any raspbery pi.

Idk. Amethyst can show pow of a note, but I am not sure how to post with pow 😅 Probably some web clients have that functionality.

How about POW restrictions for npubs and notes?

Why not? It's a reproducible build.

IDK, I like to think that trusting family not to rob you works in most cases.

Interesting ideas for a dead man switch with bitwarden https://community.bitwarden.com/t/emergency-access-only-upon-death-feature/31706

Do you think a more distributed setup could work: relays send a pre-filtered feed based on public data for your account and then you can fine tune the feed on a device with private data and preferences?

Yes, but LLMs are not everything. Much simpler models can be sufficient for a great recommender system.

Would it not be possible even on the client side to iterate trough global feed and mark posts based on recommended ratings and local settings? Depending on a device that could take more or less time, but should still be doable.

Yes simple algorithms are important and it makes sense that relays provide some of that functionality.

Still it would be great to have a recommender system for nostr to filter for you content, e.g. from the global feed. Zappable posts, news, songs, movies, or whatever else you can think of. For privacy and controllability reasons it should bebetter to have it run on the client side.

The opaqueness of NNs can be made more transparent with probabilistc ML. For example https://dl.acm.org/doi/abs/10.1145/3383313.3412225

I am looking for nostriches that would like to cooperate on such project 🤗

For example an ANN based recommendation system. NNs can be much sympler than what is used in LLMs. RAM memory is the biggest constrain, so that the complexity has to be adjusted to the device.

Image from the future past

I believe that it should be possible to train algorithms or fine tune them on the client side. However that would make any algo client specific. Althogh it should be possible to share algo parameters between clients that would require some kind of standardization via NIP.

The NIP approval implies that this algos should be implemented on relays, is that right? Many sofisticated algos could work on the client side, and simply filter one of the lists for you, like all follows or global. No need for relays to take the computational burden.

Debt was quite interesting, now working my way through The Dawn of Everything. A fascinating perspective on early societies and their socioeconomic dynamics. Specially the suggested impact of Native Americans on the age of enlightenment.

Gold. At least you can hide it.

Sad but good to know.

Code design advice would also be useful. Like design patterns for modularity and interoperability with other apps and services. Best practices for a FOSS project design with multiple contributions.