Edits on Amethyst implement this NIP. It allows users to replace the content of their posts but not the extra metadata - they can't move an existing post to a new thread, for instance.
The entire history is kept. Clients can show the history, starting with the latest edit.
Other users can propose edits by sending it back to the original author. The author accepts by creating a new edit by themselves.
https://github.com/nostr-protocol/nips/pull/1090
Lol just 4 days in.... 🤪
nostr:nevent1qqs0z4nj602pz63vf4fc4nwlcqhu0ww8vnykt7h9h90dn8wvej5zs9gpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7q3q8ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqxpqqqqqqzl0k6x6
Are relays blocking multiple connections per IP?
Because now with Pokey, there will always be two connections, one from Pokey and another for the client in use.
Sure, but the change in the client won't change anything. Anyone can watch your notifications if your inbox relays allow them to. Especially if you use public/free relays.
I am waiting for pokey to be approved to update mine. let's go nostr:nprofile1qqsxg45ph8gx0vdrvtzta6xal7v86frx6jvstsnvhrlvtehmwwh4epqpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0qydhwumn8ghj7mn0wd68ytnnv968xarjv9kxjcfwvdhk6tc79x08a
Relay devs, I need a sort procedure by the euclidean distance of the deltas between each post's geotag and create_at from the filter's lat-long and time.
Big relay crew is going to love this.
ohh nice idea. I am not sure how to blend time and distance, though. Otherwise, you might see posts from last year.
Maybe an euclidean distance with distance in one axis and time in another?
nostr:nprofile1qqsfnz2sqsflkatdssmeztxr90s8xrd7r07xkhfwaa6eu9zkcguljpgprdmhxue69uhkummnw3ezuur0wf6x2mt0dejhymewvdhk6qgjwaehxw309ac82unsd3jhqct89ejhxqgcwaehxw309akxjemgw3hxjmn8wfjkccte9e3k7mg2kf0ae nostr:nprofile1qqsglv2qkn5dmmuhee9cy8fywfu2rfp4xd3xy0myqg2gfvmjl9yqqrqppamhxue69uhk2tnwdaejumr0dsq3qamnwvaz7tmwdaehgu3wd3skueqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduekf372 any chance you have a log of what's bad with the nip-98 token?
We have Tor and we also use scheduled IO threads. So if the app/OS is doing other things in the IO thread, the upload might be delayed a bit. But it shouldnt be that long. So I think it is mostly a slow connection + wrong date time of the phone.
Yeah, so much better that Nostr has it's own app store: zap.store
Android is open source. You can just install Graphene OS if you don't trust your phone manufacturer's version of it.
"doesn't surveil a persons"
Are you kidding? Apple knows everything about you. They surveil you in every single device, in every single connection. They even have an ad-platform that Facebook was forced to use and share data with so that Apple can know you better to sell ads.
Don't think for a second that the two companies are any different. Google is just upfront about it.
Oh I did.. I know their differential privacy stuff... That doesn't change anything. Apple only offers privacy against everybody else. Not against themselves.
It's called privacy theater. They only apply differential privacy in 0.1% of their products. They only go to court in a few very public cases for marketing. Meaning while everything else is traced. 99.9% of their apps, services, devices call their servers in the open web without any privacy to you.
Why is Pokey so good?
Pokey connects directly into your inbox relays and keeps the connection open at all times.
Every other notification system is using a server that watches relays for new events and sends them down via Google/Apple/UnifiedPush systems.
It's WAY faster than ANY of these push systems.
There is no restriction on message sizes or frequency. No payment plans for servers and no algorithmic delays from push providers.
It can authenticate in your Private Inbox relays for DMs because it can get Amber to sign as of you. No watching server can do that.
It also decentralizes notifications from Clients. There is no need to run 15 different notification systems, one for each client you want to use.
Once notifications are downloaded, it can pass those events to the appropriate apps to display. You can choose a default app per event kind. And if you don't have an app registered for the event, it can display the notification itself.
It's a win-win-win-win-win situation.
Pokey connects directly with your inbox relays at all times. Every other notification system is using Google/Apple/Unified Push servers.
It's WAY faster than ANY push system.
lol. This is just 3 days old and is already my preferred way to get notifications.
nostr:nevent1qqsrqggqrn775wm5hvrpn4rx6pf7jg6p9gc9h3cphndqptae7mhjungpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgsxg45ph8gx0vdrvtzta6xal7v86frx6jvstsnvhrlvtehmwwh4epqrqsqqqqqpq7zr0k
lol. This is just 3 days old and is already my preferred way to get notifications.
nostr:nevent1qqsrqggqrn775wm5hvrpn4rx6pf7jg6p9gc9h3cphndqptae7mhjungpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgsxg45ph8gx0vdrvtzta6xal7v86frx6jvstsnvhrlvtehmwwh4epqrqsqqqqqpq7zr0k
MLS for large encrypted group chats is coming!
nostr:nevent1qqs92vwt83v4u0ggth29x2pwsz7ssg3s0v4r2rl934vza9lp0gfg2zcpzemhxue69uhhyetvv9ujumn0wd68ytnwv46z7q3qzuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsxpqqqqqqze7m60u
I heard that even MLS struggles with anything over 100,000K users to keep keys in sync. At some point the overhead of the protocol breaks it's own hability to send messages.
We can't control how implementers code. This is nostr. There is weird stuff everywhere. There are evil relays tracking users, evil clients tracking users, relay devs not knowing any better, clients not knowing any better. Most of the nostr code out there doesn't even think about privacy. We can't design a protocol expecting that everyone will have good entropy, good code or an authed service. All we can do is to offer primitives that makes sense even if everything else isn't there.
Everything you said has been said during the NIP-44 debates and they culminated with NIP-44, NIP 59 and NIP17. But feel free to offer an updated variant of all of the above.
At least 500ms slower due to the push system pings. But much more if the phone is locked. Push is VERY slow. Especially if the device is sleeping.
You also don't see reactions from other relays, especially DM relays that require auth.
Notes by Vitor Pamplona | export