Râu Cao

Another chapter closes. I vividly remember watching Julian presenting Wikileaks 1.0 at the 26C3 in Berlin in December of 2009.
Less than a year later, the Swedish government issued what we now know was an arrest warrant based on bullshit accusations, intended to get Julian to a place that would immediately extradite him to the U.S. Then-vice-president of the U.S. Joe Biden called him a "hi-tech terrorist" at the end of that year.
After the initial legal back-and-forth, the Ecuadorian government at the time granted him asylum in their London embassy building, where he was then holed up until 2019, even though in 2017, the Swedish prosecutors dropped their investigation against him and the European arrest warrant was withdrawn. But in 2018, we finally got proof of a sealed criminal case by the U.S. government against him, which was the reason for his unlawful detainment all along.
When British police were finally allowed to arrest Julian, mainstream media ran another smear campaign, claiming that the Ecuadorian government was sick of Julian's political opinions, like e.g. supporting the Catalan independence movement. Laughable.
Meanwhile, the Ecuadorian government had changed. After the socialist president Correa had run the country's finances into the shitter (and just by the way, Ecuador is using USD as their own legal tender), the newly elected former vice president was much more eager to cooperate with the U.S. government. So it wasn't that big of a surprise when Moreno signed MOUs with USAID in 2019, which resulted in a direct $62.5M investment, followed by a $6.5B IMF loan in 2020. Julian obviously being part of a quid pro quo.
Then, the worst part began. The U.K. government, stooges of the U.S. as they are, decided to not just detain Julian on behalf of the U.S. government (with Donald Trump being president at the time), but they thought putting a journalist and publisher in a supermax prison built for terrorists, rapists, and murderers was the most reasonable course of action. And they kept him there, in a 2x3 meter cell, isolated for 23 hours a day, for 1901 days.
The process was the punishment. Julian exposed war criminals, who *all* walk free today, and never served a day in prison. And he's one of us. A hacker, whose only goal was to help people by giving them the information that their own warmongering, secretive governments denied them.
There are not many people I have more respect for than this person. And I don't think I ever felt this much sorrow for someone's misfortune, outside of my own family's tragedies.
I can't wait for the next chapter to begin. But I'm so incredibly glad that this one is over!
🙏

2024-06-23 13:27:17

- reply

Yes.

2024-06-22 12:20:27

- reply

When you zap someone, their LNURL server has to be able to publish a receipt to the relays you request. If they're not allowed to publish it there, then nobody will see the zap.
I just improved this for our own Lightning accounts and relay over here, by checking if the zap request came from a relay member, and then allowing receipts to be published by non-members:
#nevent1q…jpp7

2024-06-20 22:41:15

- reply

Nostr, or rather the optional NIP-05, does not use Webfinger. It uses its own "/.well-known" URL and response format. But a Webfinger response can also contain an arbitrary amount of different links for different services.

2024-06-20 16:17:59

I just deployed a few things that I was working on over the last week, and some of them should make the zapping experience with the Kosmos relay and Lightning accounts/addresses a bit faster and more consistent:
1. When we zap someone to a non-Kosmos Lightning address, their server is now able to post the receipt back to our members-only relay.
2. When someone who's not using our relay zaps us, our accounts server publishes the receipt to the non-member's requested relays, but it will also publish it to our own relay in addition to theirs.
This means that we now reliably (and quickly) see all incoming and outgoing zaps in all of our clients, especially when other people's relay lists don't overlap with ours.
I think everyone running members-only or paid relays should implement a similar policy for allowing zap receipts to be published for their own users' outgoing zaps. Here's the relevant code in our own policy:
https://gitea.kosmos.org/kosmos/akkounts/pulls/197/files#diff-cc5c58329fae4e65a47568a691835d6d14ab236a
If someone spots a mistake, or this is generally a bad idea for some reason, please let me know! 🙏
#nostr

2024-06-20 03:10:13

We need Jungle, I'm afraid.
https://www.youtube.com/watch?v=isiVdlz8bDY

2024-06-19 15:50:33

This policy works: https://gitea.kosmos.org/kosmos/akkounts/src/commit/0daac33915f827494feb4a5d6bb9ba5d49e6b904/extras/strfry/ldap-policy.ts#L18-L40
I think everyone running a members-only relay should do this. Unless I missed something, in which case I'd love to learn why it's a bad idea!
#nevent1q…m709

2024-06-18 20:35:26

Should paid relays accept zap receipts, if the pubkey that signed the contained zap request is on the allowlist to post? I think it would make sense.
I'm asking, because my Lightning account just received a zap with not a single relay in the list that it could post a receipt to:
["relays", "wss://nostr.wine/", "wss://theforest.nostr1.com/", "wss://filter.nostr.wine/?broadcast=true", "wss://purplepag.es/"]

2024-06-18 14:24:24

https://video.nostr.build/756e84597eb1b77038c1cb68f87c80055ebe5bbbfa0e6479a931ba1381b80819.mp4
#nevent1q…a2d5

2024-06-17 22:02:00

- reply

This!

2024-06-17 17:40:13

Catus amat piscem, sed non vult tingere plantam.

2024-06-17 13:15:10

- reply

I'm sure it'll be easier than today at least.

2024-06-17 13:01:55

- reply

If they care enough, sure.
Although the more likely scenario I imagine is that Meta and Signal will just officially pull out of the EU, and then the Eurocrats can embarrass themselves publicly if they want to actually enforce app and network bans for encrypted messaging apps. I have my popcorn ready for that.

2024-06-17 12:44:02

There is no way to control user devices and the software they run for any of our open protocols, so there's simply no way for server providers to scan E2EE content transmitted via their services.
Let them cripple WhatsApp and Signal. Why do you care so much?

2024-06-17 12:29:06

- reply

OK, I understand what you're saying. However, inventing an unspec'd, poor man's version of a content-addressed filesystem by just saying "look there are hashes" is not exactly a satisfying solution to the problem.
First of all, and the biggest problem with this as of now: how would the files actually get anywhere else when lost? In almost all cases, they won't be stored with hash filenames on people's various devices that they used to post the media to begin with, even if they could theoretically find all missing source files (most people won't).
But there are other issues, like e.g. nostr.build using file extensions in the URLs, but not every service doing that. It also changes filename extensions by its own choosing.
Then there are cases like longer and high-res videos, where you don't want most clients to download a single 4K source file for example. You'd need a video-specific server and specs for this to solve it properly.
I'm not saying these (and other) problems cannot be solved. However, my initial reply was about content creators currently not being able to "publish content natively on nostr" when it comes to media files. And just looking at the current situation, that is just true either way, hash filenames or not. So there's no point in shaming people for linking media files from any HTTP URLs, regardless of the nature of the underlying service.

2024-06-17 01:01:07

- reply

Because you can't upload a podcast's actual audio files directly to Nostr relays, so it's much easier for everyone (creators, clients, servers) to host the RSS feed with the domain hosting the content in the first place. There's no reason why you couldn't *also* have a NIP for additionally publishing and consuming feed updates on Nostr relays. But the protocol is working very well as it is, and is used by hundreds of millions of people without dramatic censorship happening. Which, yes, is one of the important reasons for defending it.
That said, RSS is extensible, so you could easily add new attribute types to feed items to e.g. point client apps to social interactions on Nostr.

2024-06-17 00:41:47

- reply

RSS is extensible. You could easily add an npub and other new metadata to the feed. No need to use Websockets to fetch podcast episodes, but a client that supports nostr can then also add the social aspect to it.

2024-06-16 19:31:07

- reply

No, it does not "publish your content to nostr in a native way". It simply uploads to a separate HTTP server and inserts a normal HTTP link in your nostr event. Unless I missed something, in which case I'd love to learn what!

2024-06-16 16:58:23

- reply

True for text content, but media content "on" nostr is already not on nostr. Those files are just uploaded to nostr-auth-enabled silos and linked via plain old DNS, same as linking any other resource on the Web.

2024-06-15 18:12:57

- reply

Good explanation. I would say an API can *become* a (quasi) protocol (see e.g. S3 API), but a protocol can not become just an API.

2024-06-15 17:12:31

- reply

Wasn't the worst movie I've ever seen, but it was incredibly annoying that they didn't bother showing the actual rescue in the end.

2024-06-13 01:08:45

- reply

Elk as in https://elk.zone?

2024-06-12 17:54:15

I'm watching kind 4 direct messages from popular relays in a live stream, and it feels almost as dirty as watching the Venmo firehose, albeit with encrypted content at least.

2024-06-11 19:13:10

- reply

Alas, there's no way to confirm it. Someone could've faked most of that amount.

2024-06-11 01:57:29

Enjoying noStrudel a lot! Looks basic at first, but is actually much more capable than most clients. And yet, it feels lightweight and fun.

2024-06-10 16:01:27

- reply

Why integrate directly, when interoperability is provided by the Lightning network anyway? What's the major benefit? 🤔

2024-06-10 01:18:49

- reply

That's what I told Frank and Smuggler in person ~5 years ago, when they published Scrit. Alas, they were not convinced. But fantastic that @npub1nc0…z5pa picked it up where they left off! 🙏

2024-06-09 23:42:23

- reply

Thanks for the policy framework, @npub1q3s…d26p! Couldn't be any easier to integrate with. Spent half the day just fighting Docker to get Deno into the strfry container in our development setup.

2024-06-09 23:35:31

Hooray! Just before the end of CEST Sunday, I have completed our strfry LDAP policy, which only permits known users to write to our #nostr relay!
https://gitea.kosmos.org/kosmos/akkounts/pulls/196/files#diff-cc5c58329fae4e65a47568a691835d6d14ab236a
(Beware that you will need to register the nostrKey attribute in your server's schema to make it searchable. You can find an LDIF file for that in the akkounts repo as well.)

2024-06-09 18:37:10

- reply

There seem to be problems with Deno on basic Alpine base images, and the error is just as unhelpful as it could possibly be. :/

2024-06-09 04:07:06

Every time someone inquires about my "career":
https://storage.kosmos.org/raucao/public/shares/240609-0205-marley-rich.mp4

2024-06-09 01:03:44

- reply

We've been trying to get a bank account for a new Stichting for over a year now. Every single bank left us hanging for months on end until they suddenly got back to us with a rejection, but never stating their reasoning. And I'm not even angry at the banks per se, but mostly at the government for threatening them with heavy fines for not doing the required pre-crime policing in a way that leaves zero work for actual law enforcement.

2024-06-08 15:29:27

Fun fact: I'm getting notified via #xmpp when you zap me on #nostr, because we're mixing up and connecting various decentralized protocols in our (open-source) accounts back-end. (And for secondary accounts I usually set it to notify via email.)
Also, I log into my Kosmos account using my Nostr key via @npub1get…0nfm.
Many more integrations to come! Currently setting up our members-only relay, so we can do things like auto-sync notes and media to a user's #remoteStorage and such.

2024-06-08 13:18:25

- reply

Never mind, just checked and they already corrected the title on the Business Insider website. Not sure if the Twitter link preview will be updated or not.

2024-06-08 13:11:56

- reply

She could argue that the amount of money changing hands makes it of "compelling public interest", i.e. requires "transparency". A lot of people would probably agree, myself not included.
However, there's an actual lie in the subheader worth correcting, which is that he gave $10M directly to @npub180c…h6w6. That claim is contradicted in the article itself even.

2024-06-07 21:55:01

- reply

"I find this whole world of a thousand years of common law important. I don't think coder's law is good. I think it is shit. I think coder's law is the lowest attack on modern society, the biggest SJW attack, trying to rip down everything we have good." — Satoshi Nakamoto

2024-06-07 13:55:47

I just fixed a small bug in our Zap (NIP-57) implementation, which broke the creation of receipts in production.
Zap me 1 sat so I can test it more extensively!

2024-06-07 12:30:22

- reply

Did you hear anything since then? The status still seems to be the same.
I just spent some time writing a Chef cookbook for setting up strfry, but now I'm a bit worried about picking the wrong implementation for our new relay.

2024-06-07 00:19:52

- reply

https://m.primal.net/IbMT.jpg

2024-06-05 13:49:20

- reply

Free will is an illusion, albeit one so individual as to appear completely genuine.

2024-06-05 13:09:20

@npub1teawtzxh6y02cnp9jphxm2q8u6xxfx85nguwg6ftuksgjctvavvqnsgq5u Verifying My Public Key: "skddc"

2024-06-05 13:07:14

#[0] Verifying My Public Key: "skddc"

2024-06-05 13:07:01

#[0] Verifying My Public Key: "skddc"

2024-06-05 13:03:33

#[0] Verifying My Public Key: "skddc"

2024-06-04 17:04:24

Hello Nostr