nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9uq3kamnwvaz7tmgdajxccn0vshxxmmjv93kcefww3hk7mrn3mpe85 is on fire. 👀
Here's a discord/slack Nostr client:
https://flotilla.coracle.social
Are these definitions clear enough to non-devs out there? Do they make sense?
- Super Clients merge vastly different domains into just one application, generally providing some basic support for read, write, configuration and data management of each use case inside of each domain. Example: when Marketplace and Live Streams are placed into the same app.
- Clients provide complete support for a single domain and its many use cases, including read, write, configuration and long-term data management. Examples: A marketplace app that help users manage product catalogs, manage orders, collect payment, manage fulfillment and tax reports.
- Mini Clients provide read and write support for single use cases, including configuration management and all actions related to the use case. Example: A fulfillment app that helps users view orders placed from another Client, pack and ship them.
- Micro Clients are single interface apps that execute only one action. Viewing some record and creating the same record are separate micro apps. Example: An app that simply scans the QR code of an order and marks as shipped.
Here's where I stand:
- Super Clients merge vastly different use cases into just one app.
- Clients provide complete support for the many actions in a given use case, including read, write, configuration and long-term data management.
- Mini apps provide read and write support for single actions, including configuration management related to the action.
- Micro apps are single interface apps that execute only one action. Viewing some record and creating the same record are separate micro apps.
Nada muito difícil, mas meio que vai contra a arquitetura que montamos. A ideia era que o feed se atualizasse automaticamente. Até temos o pull to refresh para atualizar o feed, mas normalmente o feed já está no mais atual possível.
What's your version of Why Nostr Matters?
nostr:nevent1qqsqd8exd6x5f37q6qhv7rag6ygtx97yzwelmu7zhms499t7a0520dspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqyey2a4mlw8qchlfe5g39vacus4qnflevppv3yre0xm56rm7lveypsgqqqqqqsap32vc
I wouldn't use this logic. There is always something better. I am sure after MLS gets coded and merged a new DM protocol will emerge and then nobody is going to code anything because we are all waiting for the perfect spec.
My point is that we shouldn't just dismiss the state of DMs as you suggested in the first reply. Devs should implement NIP-17 as it stands today even though NIP-104 is in the horizon.
Considering that NIP-17 took about 1.2 years to be developed, audited, implemented by 2+ clients and merged, MLS will take another year to be ready.
What's your version of Why Nostr Matters?
nostr:nevent1qqsqd8exd6x5f37q6qhv7rag6ygtx97yzwelmu7zhms499t7a0520dspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqyey2a4mlw8qchlfe5g39vacus4qnflevppv3yre0xm56rm7lveypsgqqqqqqsap32vc
Yes, there can only be one Amethyst. 😎
nostr:nevent1qqsqqqp2zrs7836tyjlsfe7aj9c4d97zrxxqyayagkdwlcur96t4lasprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsygpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5psgqqqqqqs2juafc
I said this before and will say it again: Nostr's long-term goal is to make sure an AI can create a fully-functional Nostr client from scratch with minimal instructions.
True freedom is freedom from devs. 💀
> Nostr is the infrastructure behind an app ecosystem, equivalent to Android/iOS/Gnome
nostr:nprofile1qqsrx4k7vxeev3unrn5ty9qt9w4cxlsgzrqw752mh6fduqjgqs9chhgppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hsxct838
This NIP creates the equivalent of NIP-96 media servers but for push notifications. Users will be able to choose which servers are watching their events are sending notifications down to the Google/Apple/Ntfy systems.
If other people start implementing it, Amethyst will kill our last server. 🚀
https://github.com/nostr-protocol/nips/pull/1528
nostr:nprofile1qqsrmpp2lmx4u2fl9zmxy7fnwp9rlwxwz5a2j8tep2c376n494z2gtgpzamhxue69uhkxetvd3shytnwdaehgu3wwa5kuegpzamhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuegpzpmhxue69uhkummnw3ezuamfdejsumlnkj nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgwwaehxw309ahx7uewd3hkctc58hv2s any chance you guys can offer this service for the authed relays, like inbox.nostr.wine and auth.nostr1.com ?
Since an external service, like push.amethyst.com , cannot login with the private key of the user because it doesn't have it, the only way to get DM notifications working is if you implement something like this.
When AIs throw the truth in your face...
> Is Nostr Web3?
ChatGpt: Nostr can be considered part of Web3 due to its decentralized nature, user ownership of data, and censorship resistance, aligning with core Web3 principles. It enables users to control their identity and messages via cryptographic keys, fostering privacy and interoperability. However, unlike many Web3 projects, Nostr does not rely on blockchain or native token economies, making it a distinct, lightweight approach within the broader Web3 landscape.
Gemini: Yes, Nostr is a decentralized social media protocol that aligns with Web3 principles. Unlike traditional social media platforms, Nostr doesn't rely on blockchain technology or tokens. Instead, it uses a network of independent servers to ensure user privacy and control. This decentralized approach makes Nostr resistant to censorship and aligns with the core values of the Web3 movement.
Hank makes the case for nostr:nprofile1qqsgydql3q4ka27d9wnlrmus4tvkrnc8ftc4h8h5fgyln54gl0a7dgspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg5waehxw309aex2mrp0yhxgctdw4eju6t0qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyfehcpn to buy the Twitter brand out of X.
https://youtu.be/NyV54qfSZwg?si=aYa2mHakLMEJLOsy
My next goal is to get users to reduce their relay lists from an average of 20 to 3.
You don't need to trust 20 relays. You just need 1. But 3 adds redundancy in case 2 of them are busy at the same time.
And remember: Relays can see what you are looking at in real time because the app is requesting the post, likes and replies from them as you scroll. They can even count which posts captured more of your attention.
So, make sure you trust your relay operators.
GM.
If know how to make videos and want to help Nostr, doing a Why Nostr Matters video is the way to go. Here's nostr:nprofile1qqsftzm4fgwnmed4ajs0uvwj642lg5fjt7zf32pa5xvhkl7dtsu73rqpz4mhxue69uhkummnw3ex2mrfw3jhxtn0wfnszynhwden5te0wahhgtn4w3ux7tn0dejszxmhwden5te0wfjkccte9e3xjarrda5kuurpwf4jucm0d5nggkmy's version:
nostr:nevent1qqs0tlx9e32djz50hqkf8pyxf938g32el0n24fp6m6amlvr3vnw2xcqpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7q3qjk9h2jsa8hjmtm9qlcca942473gnyhuynz5rmgve0dlu6hpeazxqxpqqqqqqzje3hj8
Oddbean new post about login | logout
Notes by Vitor Pamplona | export