Another banger from Cory Doctorow.
nostr:note1vzpj9qllay55es9dr4nm22f5dvgrptxhp73mnys6h8tw7jwk569qtuwmpr
Actual PhDs are cheaper than that.
I was thinking about a way this could work. If the relay already handles NIP-09 deletions, it should keep the kind 5 notes around and use them as a filter just in case one of those notes happens to be sent to that relay in the future.
So, a relay also has an npub. So it should accept any kind-5 published by the relay’s npub regardless of the author of the offending note.
I celebrate Orthodox #starwarsday.
It’s three weeks from today, May 25, the anniversary of the day #starwars was released in the theaters.
I’m looking for a #nostr relay implementation that has an admin ui for moderation.
Also, just removing a note from the database isn’t enough. Because it can just be sent again. The moderation system needs to remember the note id so that if it’s ever sent to the relay again, it’s not saved.
Bonus points if it has a way to sort by number of “reports” a note has.
#asknostr
There’s a fan edit out there on the interwebs called “The Bilbo Edition”. They basically cut it down to one-movie length. It’s actually watchable.
“Ugly bags of mostly water.”
A rough draft of a BUD-10 for multi-part uploads to blossom servers. not sure if this is a good idea so I'm looking for feedback
https://github.com/hzrd149/blossom/pull/67
The biggest issue comes from the fact that blossom relies on the sha256 hash of the whole blob. so there isn't a way to verify that each uploaded chunk is part of a whole until the all the chunks are uploaded.
I think this issue can be mitigated slightly if the client includes `x` tags in the auth event for each chunk its uploading. so that the server can verify that each chunk was created by the client.
In the case of payments, I think it could be possible for the client to pay for each chunk. although this might require more requests or the server to define an x sats/bytes pricing.
Inspiration taken from https://tus.io/
Thanks to nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 for making me aware of it
Wasn’t nostr:npub1t89vhkp66hz54kga4n635jwqdc977uc2crnuyddx7maznwfrpupqwra5h9 working on something like this? Hornet?
Hey nostr:npub1f5pre6wl6ad87vr4hr5wppqq30sh58m4p33mthnjreh03qadcajs7gwt3z is this that plant you were mentioning making the anti-histamine tea from?
Mushroom looking & purple flowers?
Rev uses Purple Dead Nettle. That looks like it.
Wrong. Only if you distribute the code at all. If you keep it on your own hardware (or on your company’s hardware) and never give it to anyone, you don’t have to open source it.
> if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
https://www.gnu.org/licenses/gpl-3.0.en.html
If you don't want to open source your shit, don't distribute it to others.
This is the correct answer. You don’t HAVE to open source it, but if you even email a copy of the code to one other person (outside your organization if your company owns the copyright) then the GPL applies.
We sing this song when we play Settlers of Catan. “We built this city with rock and wheat!” Or, if trading is necessary, sometimes it’s “We built this city with rock and sheep!”
Yes. However, the improvisation was because Harrison Ford was super sick with the flu that day and didn’t have the energy for it. So he asked “can’t I just shoot him?”
They give away their services for free to 99% of their customers. Remember, if the product is free, you’re the product.
But the other 1% pay through the nose for their “Enterprise” service, which has extremely good privacy and security. And all the settings you could possibly want for configuring your environment.
The fact that there’d be a battle at all is proof that something fishy is afoot and the account is probably compromised. It’s a losing proposition for the attacker.