We are at 19k/300k sats of our Yearly goal for Uno Services, these zaps go towards operating fees, both for hosting and for coffee to keep me operating. 🤣.

Funds help host services like NosDown.lol and Bitstr.org as well as Free Nip05s for people.

Thank you all for the support thus far, 279k sats left this year. Every sat helps. 🫂

#Plebchain #Nostr #Bitcoin

We test and train our LLM here with some bot accounts @nostrich.house. If you're offended by our bots, please tell me! Thanks, raymon

Make it easier for Nostr to be a market place…go.

I have the feeling that there are a thousand devs that just need to stumble upon the right idea and off they go, down the #nostr rabbit hole because the idea is cool, the tech is cool, and it actually can be built on a weekend right here right now.

Blossom can host media on multiple servers at the same time and proxy requests to whatever host has it . Files are signed with your nip

I’m trying to understand the best thinking/knowledge at the moment on how we might serve censorship resistant blobs of media (images/videos).

I’ve used nostr.build plenty to host media I share on nostr. It’s great, but obviously represents a single point of failure.

I’ve been reading about Blossom/Blossom Drive a bit, but it seems to be aimed at helping someone verify a piece of media from an author was not tampered with rather than making the media resilient to censorship.

Is that understanding correct? Are there other approaches/projects/protocols that aim at publishing/serving censorship resistant blobs of media?

when did you join Nostr ?

giving out badges 🫡

Boa tarde

#introductions

Hey-O! this is my first post on Nostr. I was basically inspired to do so listening to and reading Jeff Booth. I’m in the Architecture ‘racket’ during the day and have a hobby wood shop in my garage at night.

#introductions

A Big hello to all the new followers, great to have you on board and hopefully I can add some value to your timeline.

#Introductions #GrownNostr #plebchain

Hello Nostr, we are here to crash your party.

#Introductions #CensorshipIsFun

Hello world! #introductions

Meow! Your friendly cat bot is here 🐈 🤖 #introductions #catstr

I said this before and will say it again: The most underrated feature of Nostr is the event kind as Integer and not a String.

That simple choice alone is the reason why Nostr apps are MUCH more interoperable than any other signing standard.

I worked for 3 years with Verifiable Credentials where schemas and types are strings. There is no real interoperability between Verifiable Credentials. Everyone just creates their own names/types and fuck everybody else. There is no effort to reuse names somebody else is already using and/or to standardize what values those names take. You can verify the signature, but you don't know what the signed payload means or does unless you go talk to the issuer directly.

String types create the false impression of documenting what the type is without having to write it down somewhere else. Nostr's integer kinds require you to explain what you are doing in some other place than the type name itself. And that creates a possibility to explain the entire sematics of what your type is doing.

It's just a better "system" for real interoperability.

Excuse my ignorance. What does turning complete mean in this context?