Yes, those details matter significantly.

⚡A C V⚡
Spam is not a threat to #Bitcoin
I'm just saying, they're not charging him with silence, which is a right and he is permitted to remain silent.
He didn't say, no thank you, to their request for the pin. He didn't claim his right to silence and an attorney. He provided false testimony, in a pin that wasn't the right pin, and that pin destroyed evidence. At least thats how the prosecution is seeing it. You can't argue against a crime you're not charged with.
You have to take on the charges directly. How do you argue that it wasn't lying about what the pin was/did? It was. It was a trick pin. It caused a destruction of evidence. It was his intention. Maybe this new charge is less than the charge they would give him if they found the content on the phone, but it's not inaccurate to say he took these actions. If the court agrees he took these actions and that these actions are against some code or another, which seems likely, then they will convict.
He didn't say, no thank you, to their request for the pin. He didn't claim his right to silence and an attorney. He provided false testimony, in a pin that wasn't the right pin, and that pin destroyed evidence. At least thats how the prosecution is seeing it. You can't argue against a crime you're not charged with.
You have to take on the charges directly. How do you argue that it wasn't lying about what the pin was/did? It was. It was a trick pin. It caused a destruction of evidence. It was his intention. Maybe this new charge is less than the charge they would give him if they found the content on the phone, but it's not inaccurate to say he took these actions. If the court agrees he took these actions and that these actions are against some code or another, which seems likely, then they will convict.
BBQ
That was my favorite part too.
This is exactly it. This banking crisis isn't over.
I want them to try.
Even someone like yourself can't believe fully until the work is proved.
Until they come at us with all of their might, many will still say "wait until they decide they want you dead".
Fuck around, find out.
Even someone like yourself can't believe fully until the work is proved.
Until they come at us with all of their might, many will still say "wait until they decide they want you dead".
Fuck around, find out.
I feel attacked
This.
Debt is a history book that tears down the idea of a barter economy in economic antiquity. It doesn't really say much of any meaning about Debt or modern economics, etc.
It's a fun read, though.
Debt is a history book that tears down the idea of a barter economy in economic antiquity. It doesn't really say much of any meaning about Debt or modern economics, etc.
It's a fun read, though.
pictures of feet are apparently very popular
Nice. Thanks.
GM I've been away too long, Nostr
Looking great. Let me in! THanks.
You deserve a break.
Banks are closed Saturday, that's the joke. Lets do it right now! =)
I don't think there is a right size.
The problem is that Iris is a website and its fully implementing the protocol.
The local data issue is due to a scaling problem in the protocol. If you query as you want to view, you're potentially querying a relay you don't typically connect to or you're querying a relay thats very busy. You have overhead to connect to it perhaps or you're waiting on your turn. This is worse because everyone has 7+ relays and at least they're gonna query more than one to get a fastest return.
The amount of work the relays do in responding to client requests scales poorly. They rate limit these requests to keep from being DDoS.
I think we'll see that the websites/phone apps need to use a middle layer service and index that scales better and pulls notes only as you need them, and not just every note seen for only a few hours or days.
Fully implementing the protocol, a global protocol for every message basically, is going to need some hardware resources. It doesn't seem to work great in a light phone or web app.
Alternatively, you can limit things to only the last 1-3 hours, some small set of friends of friends, instead of friends of friends of friends or more, which is what it seems like it's doing if you close and reopen #[3]. It doesn't get slow or unresponsive, but it only has a few hours of the global feed. It seems to have no follower feed until global has synced those notes, and then you return to the follower feed.
The problem is that the relays don't respond promptly to queries so we need to sync and save every message seen, for viewing it later on demand. If the relays were fast like professional cloud services with indexed databases, etc. then we might be able to dump the sync data and just query as we go, which is how a web app is supposed to work.
The data needs to be removed from the web site/browser cache. That will never work well enough for the amount of data used in a day or week, from 5-10 relays. It needs to be put into a real database, a real cache, a real index and that would only be possible for a service style client like #[5] and Nostragram, or a full database backed desktop client like #[6]
The problem is that Iris is a website and its fully implementing the protocol.
The local data issue is due to a scaling problem in the protocol. If you query as you want to view, you're potentially querying a relay you don't typically connect to or you're querying a relay thats very busy. You have overhead to connect to it perhaps or you're waiting on your turn. This is worse because everyone has 7+ relays and at least they're gonna query more than one to get a fastest return.
The amount of work the relays do in responding to client requests scales poorly. They rate limit these requests to keep from being DDoS.
I think we'll see that the websites/phone apps need to use a middle layer service and index that scales better and pulls notes only as you need them, and not just every note seen for only a few hours or days.
Fully implementing the protocol, a global protocol for every message basically, is going to need some hardware resources. It doesn't seem to work great in a light phone or web app.
Alternatively, you can limit things to only the last 1-3 hours, some small set of friends of friends, instead of friends of friends of friends or more, which is what it seems like it's doing if you close and reopen #[3]. It doesn't get slow or unresponsive, but it only has a few hours of the global feed. It seems to have no follower feed until global has synced those notes, and then you return to the follower feed.
The problem is that the relays don't respond promptly to queries so we need to sync and save every message seen, for viewing it later on demand. If the relays were fast like professional cloud services with indexed databases, etc. then we might be able to dump the sync data and just query as we go, which is how a web app is supposed to work.
The data needs to be removed from the web site/browser cache. That will never work well enough for the amount of data used in a day or week, from 5-10 relays. It needs to be put into a real database, a real cache, a real index and that would only be possible for a service style client like #[5] and Nostragram, or a full database backed desktop client like #[6]
Well, they have to mail you the hardware but the ISP doesn't know your address, only Calyx who would hopefully require a warrant as a 'Privacy' focused non-profit.
It's like an email. You don't say anything in an email, you wouldn't want the whole company to see. Because emails get forwarded, cause thats how email works.
The problem isn't that people shouldn't share the note with other relays, it's that they could and inevitably would. The note is self-authenticating, if it's valid, if it's Nostr. The server isn't the database of record, or anything. If it's read by someone other than you, it can be shared and instead of it being someone just claiming you said this, it would be as if you said it yourself, and all of Nostr would accept it as valid and authored by a public key.
Totally absurd. Nostream is not in possession of any data that can be considered personal or private, it's literally the point of all the data that is sent to the nostream service, to be shared openly.
I don't live in California, but I wouldn't worry much, if I were.
I don't live in California, but I wouldn't worry much, if I were.
There's no such thing as a private relay, only a secured relay. Someone will have access to the notes, and since any user/client can verify that you signed the note, any of those people or their clients can republish the note, and often do, to any relays they might want.
The real issue, for me, is that Microsoft Defender is producing a false positive for
Trojan:Script/Wacatac.H!ml
I should just build from source, I guess. I'm lazy.
Trojan:Script/Wacatac.H!ml
I should just build from source, I guess. I'm lazy.
100%
Consensus is hard as fuck, but if there's an existential issue, like the bug from 2010 that created infinite Bitcoin, everybody is aligned and consensus is automatic.
Consensus is hard as fuck, but if there's an existential issue, like the bug from 2010 that created infinite Bitcoin, everybody is aligned and consensus is automatic.
I have the 0.5.2/gossip.0.5.2.msi
I don't think it's a virus, I think the build config is putting 0.5.3 in there when it's really 0.5.2. I didn't get updated but Windows thinks there's a virus in here, for some reason, when I don't think there is, given the SHA 256 checks out. It's the installer you produced.
the 256-SHA hash is correct but it says this:
Subject: Gossip 0.5.3 Installer
https://nostr.build/i/nostr.build_0bfe508f63faaaf762aea82…
I don't think it's a virus, I think the build config is putting 0.5.3 in there when it's really 0.5.2. I didn't get updated but Windows thinks there's a virus in here, for some reason, when I don't think there is, given the SHA 256 checks out. It's the installer you produced.
the 256-SHA hash is correct but it says this:
Subject: Gossip 0.5.3 Installer
https://nostr.build/i/nostr.build_0bfe508f63faaaf762aea82…


