Avatar
codevski
0fa082834b2996b1dd9ce6ed3c0be73b3205a3eab2d097e8886c37de75418cd5
Software Developer.

Yeah notice a bug where it created 3 chat connection to the same user and noticed I cannot delete chats hopefully this get added soon

so im using ndk, fetching a particular event with filter. The filter pretty much has the eventid, with kinds (7, 1984). Weird thing is for example: https://yakihonne.com/videos/naddr1qvzqqqy9hvpzqraqs2p5k2vkk8weeehd8s97wwejqk374vksjl5gsmphme65rrx4qq2567phd3j8gmtg2p5xwwrwv4zhsanz0pt8vnze8cd my video shows 3 likes but when I click on whos liked the video I only see two people .... so not sure how reaction / likes are shown

Replying to Avatar jb55

Pretty impressed with https://linear.app so far. Performance is very fast. auto-imports from github which makes managing all of the damus issues a breeze. Even supports pull requests. Much easier to manage issues across teams and projects than github. Timeblocking calendar integration in morgen is a bonus.

How does this differ compare with plane? https://plane.so/ has selfhost option as a bonus

Been pulling my hair out on wondering why NDK was not returning the amount of likes for a nip71 then tried it on nostr-tools and get the same results but viewing the same post vid on other clients showing 3 instead of the two i see... not sure if im missing something...

Testing a comment on a video

Are there more major changes coming? Experimenting with a short vid like client mmm...

Replying to Avatar hodlbod

Take the NINO quiz! Here's how flotilla fares:

- [ ] There's no NIP for your data format

- [ ] There's a NIP, but no one knows about it

- [ ] Your NIP imposes an incompatible/centralized/legacy web paradigm onto nostr

- [x] Your NIP relies on trusted third parties

- [ ] There's only one implementation of your NIP

- [ ] Your core value proposition doesn't depend on relays, events, or nostr identities

- [x] One or more relay urls are hard-coded into the source code

- [ ] Your app depends on a specific relay implementation to work

- [ ] You don't validate event signatures

- [ ] You don't publish events to relays you don't control

- [ ] You don't read events from relays you don't control

- [ ] You use legacy web services to solve problems, rather than nostr-native solutions

- [ ] You use nostr-native solutions, but you've hardcoded their pubkeys or URLs into your app

- [x] You don't use NIP 89 to discover clients and services

- [ ] You haven't published a NIP 89 listing for your app

- [ ] You don't leverage your users' web of trust for filtering out spam

- [ ] You don't respect your users' mute lists

- [ ] You try to "own" your users' data

That's a 3 on the NINO scale. The "trusted third parties" thing is debatable; in this case I'm counting relay operators, most of which are nip29 multi-tenant relays and relay.tools currently, but ideally that will improve as people run their own infrastructure.

How does your app fare?

nostr:nevent1qvzqqqr4gupzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcqyqzeszjv7rh8fflpeua9q644a32usvwd0cu7cze9lxy4grjy2y7rwtcw9gv

Mmm i cant seem to get flotilla to work seem to always get a permission error on my relay when sending messages in a channel...

Lookng to get lnd dockered to work with alby hub. Ran into issues i think config isnt correct with lnd hoping to give it another try again. Dod you happen to follow a particular guide or just reading a particular node doc?

Replying to Avatar Bee Aye

alright...

nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug i cant see the note from UTXOs original post. im using amethyst 0.94.1 downloaded from zapstore. i use graphene OS pixel 6a.

if you need other details let me know

Similar setup, took about 30mins before showing up

Replying to Avatar StellarStoic

Just look at the [NIPs](https://github.com/nostr-protocol/nips) and add what you need. I'm not a dev and with a help of an AI, even I can build on top of nostr.

Cheers, interesting ill keep it in mind perhaps a rating nip might be useful not jusr for my usecase but rating articles etc

Its already ts, tho never played with nostr on a dev level was trying to find active ts packages to speed things up

Sorry, early stages to see if it would work out similar to trakttv but for games to auto log/journal (with a decky plugin). Atm using services like backlogged to manualy log things

Is it worth implementing nostr to an existing project to handle social side of things? (Comments, leave reviews, potentially walkthroughs/guides?) So users can decide to stack sats? #asknostr