Testing broadcasting relays... 1, 2, 3
yakbak.app is super cool. It will definitely be on Amethyst.
Who cares about the timestamps hashes in the blockchain if you can't find the event that explains what they were referring to?
Also, the timestamps are for the group of events. So, you need to have the source events to even check if the timestamp includes that specific event or not.
If you can find it. You won't even find 75% of my events for your bullshit "immutability" tracker.
Yep, that's kinda the point of nostr. We like that feature.
The relay can still delete those timestamps and the events themselves.
Yep. You are right.
Yep. We verify everything that comes in.
This idea that Nostr is "immutable and verifiable", as in being a single source of truth, is the biggest lie in Nostr. So many people misunderstand it. Yes, you can verify **individual events** by their signature... **if you have them**. That's a big if. Authors can delete these events at any time, and once they do, your client will also delete them from your local database. They can ship new versions of replaceable events, and that will make things disappear in your local DB too. If your Client was not active, it would have never seen some of the changes in the first place. Once that happens, you can't "verify" anything anymore.
Nostr, as a database of events, is only "immutable and verifiable" if you have a special relay that can track and store all regular and replaceable events as they happen and reject all types of deletions at all times. There is no way around it. And that relay is a **trusted** entity, since there is no way to verify if that relay hasn't deleted anything it doesn't like. Events have never been "immutable". Events by themselves are only verifiable if you have them. A chain of events is not verifiable unless you secure the storage of the entire chain by yourself in real-time. Nostr doesn't do that for you automatically.
Nostr is not a blockchain. Stop thinking it is one. It was specifically designed to NOT be one. It's not a problem to be solved.
Turns out it's super easy to do with SQL lite. I can only imagine how much easier/faster/better, it would be with postgres.
I just finished a quick Event Store lib for Amethyst on Quartz just to remind myself that
1. SQL is awesome.
2. Nothing beats Amethyst cache speeds.
The db automatically manages addressable events (replaces/deletes old ones in favor of new), supports NIP-05 deletion, NIP-50 full text search, NIP-62 Request to Vanish, NIP 45 counts and NIP-40 event expirations. It indexes all single letter tags and some extra ones per kind.
The goal wasn't to be the fastest, but the one that never gets corrupted or loses data. Current speeds are at 45ms to insert 1000 events (with disk write to not lose it) and 1ms per query and about 25ms to load 1000 heavy GiftWrap events into full Kotlin objects. We could do 10x these speeds if we disable transaction logging. But that would make the DB corruptable.
A little more and we can have our own relay implementation as a lib.
It's still in the outbox branch, but Kotlin devs can play with it already.
Yeah, I think design was difficult to understand. We can make it better.
To talk to people without contaminating your feed with junk no one cares about.
Make any post that starts with @ user a Public Message that only shows up in that person's feed?
That's certainly possible, but I think it would be better handled by the app being used, not necessarily the #nostr protocol itself.
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9uq3wamnwvaz7tmkd96x7u3wdehhxarjxyhxxmmd9ukfdvuv could this be built into #amethyst?
Yep, but it is app per app, not a Nostr-level thing.
I think nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z created something like this.
but the challenge is to get slow legacy companies to adobt it.
The demo still works (web/desktop only): https://crafters.amethyst.social/?author=460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c
I get dozens of requests for new features every day. The users aren't apathetic, they just don't care about polls specifically. Only other devs talk about polls. It will come, but it is definitely not the priority.
Nice!
Me too, but the apathy towards the feature is quite telling. It will come in time.
Are you paying for nostr.build? Or is this the free account?
Fun tip: put some blueberries in sparkling water and watch some of them go up and down
like a lava lamp.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z are you going to take that, sitting down? Or are you going to shut this shameless, dastardly Nostrich right up
... by also implementing Freedom Polls.
Frankly, nostr:nprofile1qqsvyxc6dndjglxtmyudevttzkj05wpdqrla0vfdtja669e2pn2dzuqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszrnhwden5te0dehhxtnvdakz7lr3n5c has been the only user asking for it. So, it's in the pipeline, but very low priority.
Correct. Only the good ideas get somebody else to support it.
Because on a kind 1 your followers will see a post that doesn't make any sense for them to see. It's not a problem that it is public, it's just noise for them.
By luck probably. Because I don't follow what happens on Damus specs.
DM means "direct message". PM is private message. No one should expect any privacy from simply saying DMs.
WhiteNoise has that. You can only send messages to individuals that you got the message key for.
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309amxjar0wghxummnw3erztnrdakj7xcm2wk Is there a way to know the engagement on #nostr ? For example if someone looks at your post, can it be known only to the author ?
Not really on nostr, but you can have an image server that tracks everytime an app downloads it. Then you just need to make sure there is an image in every post.
That's ok, we can hide the sats. It's still sats though.
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9uq3wamnwvaz7tmkd96x7u3wdehhxarjxyhxxmmd9ukfdvuv is there no way to choose what becomes a notification with nfty? I see no config options in amethyst or ntfy for choosing the notification types.
Got zaps but no replies or likes so far.
In amethyst settings in android settings it only shows zaps recieved and now playing as options.
Correct. We only notify zaps and DMs on both NTFY and PlayServices. For the other notifications you must use Pokey.
When I select 2x, I don't want faster audio. I want the player to get rid of the irrelevant bits in the video that don't contribute to the story or the lesson.
1% more battery consumption
Less people downloading Pokey (more centralizing)
Weird. I use it everyday. Pokey uses less than 1% daily on my phone.
Have you tried pokey? It works really well
Cold-pressed olive oil is so tricky to pair with other food. It's so grassy that you can't put in salads without mixing with other stuff to mellow it out (which defeats the purpose). Even some breads don't go well with the oil. It's bizarre. It should work, but it doesn't.