Started a new pencil drawing….. this is going to be interesting 😊
Wip: first layer of gray charcoal and highlights with eraser https://video.nostr.build/3933ad2db7434f7c1a1a194a4eb307afe2bd572f25757f57a70b87a95dc6a5e2.mp4
😍 have you seen the creator residency you are running on Nostr? I would love to see you be a part of it. https://www.nos.social/creator-residency
The way this renders in Nos 😂
An interesting experiment in Nostr moderation: a personal LLM that will run on your device and tag events for you.
😮 I have seen the NIP but I didn’t know a majority and clients of servers have implemented it. Is there a list of these somewhere or do you know a few off the top of your head?
nostr:npub1nxy4qpqnld6kmpphjykvx2lqwvxmuxluddwjamm4nc29ds3elyzsm5avr7 what are you all thinking about the Blossom stuff? Any plans to adopt this or another decentralized file storage protocol at Nostr.build? https://github.com/hzrd149/blossom/blob/master/Server.md
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 when do we move the nips repo to ngit or similar?
I get really angry when an org gets hacked and my data is stolen and in return they give me “1 year of identity theft monitoring” as if that’s going to do anything. The thieves can just wait a year to sell or use the data.
However nowadays my data is stolen so frequently that by the time one year of free coverage ends there is another year of free coverage available from some other company. It’s funny in a way.
I found 24 that support it on https://nostr.watch/relays/find but I’m not sure how big or reliable any of them are. I don’t see relay.noswhere.com on that list though, and I haven’t heard of that one before. I’m adding it to the list for consideration, thanks!
nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy I would love to make it nostr.band, it’s actually already on our default relay list but it sends way more rate limit errors than any other relay so it’s hard to rely on it. Are the current limits something you have found necessary or would it be possible to raise them?
Are most nostr clients using NIP-50 for search or something else? The two most popular relay implementations, strfry and nostr-rs-relay, don’t support NIP-50. We are looking for a big, reliable search relay to add to the default list in Nos.
Are you a DevOps engineer? Come work with us at Nos! https://www.nos.social/career/devops
nostr:npub16zsllwrkrwt5emz2805vhjewj6nsjrw0ge0latyrn2jv5gxf5k0q5l92l7 nostr:npub1j60x528w2g2vkq5kae5uhh8y7sezjyj20zcsg0v9muc72cmdpu0s0md7ua maybe this helps for the safety minded user and use case
Thanks! We actually have a more basic web of trust feature that will put content warnings on replies more from people more than two hops away from you. I’m a big fan of this kind of social filtering.
Hm, ok. Idk maybe these people are following it and then getting mad when it reports them? Here’s one: nevent1qqs84syt7crsa2kv778r5arsze98y65wxps9tz7fhcccq0zzlwjv5pq57qdm2
Would Amethyst show a notification if someone you don’t follow mentioned you in a report?
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z what logic does Amethyst use to decide whether to show a content warning on reported content? We have a AI bot (nostr:npub14h23jzlyvumks4rvrz6ktk36dxfyru8qdf679k7q8uvxv0gm0vnsyqe2sh) going around labeling stuff and we’ve had several complaints and some targeted harassment towards our employees from Amethyst users who don’t like it.
In Nos we only listen to reports from people you follow, but it sounds like Amethyst is doing something broader?
There's a few that you could consider potentially integrating that doesn’t require adopting the NostrEvent data model if you already have your own:
Public and private key creation:
https://github.com/nostr-sdk/nostr-sdk-ios/blob/main/Sources/NostrSDK/Keys.swift
Unrecommended DM spec:
https://github.com/nostr-sdk/nostr-sdk-ios/blob/main/Sources/NostrSDK/DirectMessageEncrypting.swift
Event verification:
https://github.com/nostr-sdk/nostr-sdk-ios/blob/main/Sources/NostrSDK/SignatureVerifying.swift
NIP-05 validation:
https://github.com/nostr-sdk/nostr-sdk-ios/blob/main/Sources/NostrSDK/NIP05Validating.swift
Relay metadata and validation:
https://github.com/nostr-sdk/nostr-sdk-ios/blob/main/Sources/NostrSDK/RelayURLValidating.swift
https://github.com/nostr-sdk/nostr-sdk-ios/blob/main/Sources/NostrSDK/RelayInfo.swift
Web socket and relay management (though we haven't integrated the outbox model yet, and it has some coupling to the NostrEvent data model):
https://github.com/nostr-sdk/nostr-sdk-ios/blob/main/Sources/NostrSDK/WebSocket.swift
https://github.com/nostr-sdk/nostr-sdk-ios/blob/main/Sources/NostrSDK/RelayPool.swift
For further integration with our data models, we haven’t thought through what that might look like with a persistence framework. We’re leaving room for flexibility so that the developer can choose. With that said, it’ll be good to get an idea of what that might look like. I’ll start thinking about it. Tagging in nostr:npub1qlk0nqupxmlyxravg0aqscxmcc4q4tq898z6x003rykwwh3npj0syvyayc as well as he has much more Apple development experience than I do. I know about Realm, SQLite, and Apple recently introduced SwiftData. Though, I don’t know the tradeoffs.
That’s a nice list! We already have our own versions of each of these in Nos, but maybe it will make sense to convert to yours at some point. If we were starting an app like Nos from scratch I would definitely pull these in first thing.
sweet. We don’t do encrypted mutes yet, but we should. Do you?
Good point - how do yall implement mute on Nos?
I dont think currently damus imports / checks for mute lists generated on other clients - nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 lmk if I am wrong.
This should be added. Checking backlog.
I think Damus is still using the old kind 30000 mute list which has been deprecated and everyone is standardizing on 10000. We are using 10000 in Nos. See https://github.com/nostr-protocol/nips/blob/master/51.md#deprecated-standard-lists
nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf I'm curious, since you have some experience with our codebase, do you see any high value areas in Nostr SDK that we could take advantage of in Nos? Besides the NIP-44 stuff of course. And do you have any ideas on how you would integrate Nostr SDK with a persistence framework? Is there one other than Core Data that you like?