Avatar
balas
9ec7a778167afb1d30c4833de9322da0c08ba71a69e1911d5578d3144bb56437
Full Stack Sats Dev at https://alphaama.com

'.mov' videos have no place on nostr, this is madness and I don't understand why it's still happening in 2024

I'm forging my own path and exploring how I can interact with the protocol without nanny rails and glossy buttons. it's very difficult at the moment because the protocol is still in it's infancy and keeps changing with new features added continuously. I had to rewrite my client a bunch of times because when I think I have a good base, suddenly the big clients start to adopt a new NIP that renders my code unfit (bech32, rpe, outbox, etc...), the paradigm of what a client should do keeps changing, so there's no time to sit and design with a clear focus because users keep expecting their client to adopt whatever the other clients have. IMO, good design will only arise when a client can confidently stay in a fixed set of features, but for now it's been more on having all the features functioning than having them be designed properly.

I know, but it's not really churning all the time, it's basically only my notes and maybe 1 or 2 crazy people I don't even know about..

and I don't know where to begin with rust crates and all that shit.. so it's the best I can do for now :)

not as it stands, because I purposefully left out kinds:[0,3,7] because those are automated in the UI, but it can easily be added too

alphaama now has pow. you can use a global for all posts or apply as needed per post.

if we don't have reactions with their own kind, then people will use kind:1 to write a single emoji without a way to single them out. are kind:1 notes with one or 2 characters spam or wasteful?

at least this way we can choose to not download reactions if we don't want to (or zaps or any other kind).

now, regarding note aggregation, this is a practice that doesn't work well with nostr, because there is no central database. every relay has it's own count and trying to merge all this is pointless, what value do people get from an open count? this number can be faked or inflated and is only used by people manipulating the masses by bragging their own numbers. notes with 3 / 4 likes sometimes come from the same account that made the post in the first place, and because clients aggregate and don't show who did what and when, they distort the value of the note and burden the relays. that's why advocating for more of this is going the wrong way, clients will just show meaningless numbers to people.

reactions aren't likes, they're full blown replies using a single character and can convey way more meaning than a 1000 bs words note.

I'm not because I don't use the feature. but if you're going to ask for everything just for a count, might as well trust the relay for that, because it's meaningless anyway and the relay doesn't have to send everything and you don't have to download everything just to discard it afterwards. but just because I don't use it doesn't mean that other don't as well, so if clients will do it because they can, they will, and in that scenario, it is best to have a better solution with tradeoffs both agree.

no, because the notes are external content not generated by the relays, the relays cannot be trusted ever, the client needs to verify everything. you're advocating for clients to "just trust me bro" which is completely wrong. the practice of displaying a single integer count is the problem, and clients downloading tons of events just for that are the problem. anyway, there's a COUNT nip since a long time ago that I helped shape precisely to unburden relays from this bad practice.

I don't need to do that because I don't tally anything, I display all the reactions like any other reply, but I would use relays to count if I needed to use that feature.

just download the reactions of people you want, just like you do with kind:1

it was always dumb to ask for everything, either reactions or any other note, but clients decided to go the dumb route.

hi alvin, the microapps have no relay connectivity, they are just simple forms that translate things into JSON format. to send that note you need to have https://alphaama.com setup with at least one relay, then you can use the command `.aa e mk ` (replace with the event you made) this will create a draft event that you can then send.

Also, the tags are not really like you wrote them, you need to include `t,` at the beginning of the line as tags in nostr can be a lot of things and are defined by the first value, in this case, it looks like you want to use hashtags, so those should start with a `t` then a comma `,` then the value you want.

relay passes all the tests except strange ones that i don't really understand

https://relay.lol

the tests that don't pass i think they actually do what is required but because the message in the OK envelope is not expected they fail

anyway, so, the main thing is that it fully supports all methods of requesting event deletion, both delete by ID and delete by a-tag (kind/npub/parameter d-tag), and it writes tombstones now so if an event is deleted it stays deleted, it won't save the same event ID again until the tombstone is deleted (have yet to work on adding back the garbage collection)

going to put together a configuration system for it that uses ONLY environment variables (because fuck complexity) and mark a minor release bump 1.1.0 soon

getting this: