I need a vacation

Bro, do you even feel?

Also, I’m on Damus. My particular relay mix doesn’t have access to this full conversation. I jumped in mid-way when browsing replies. I just saw “403” and chimed in. If there’s a relay I should add, please let me know. 🙏

Does Jumble assess relay connectivity by WebSocket request? Or does it send pre-flight HTTP feelers? I’m speculating that feelers could be a reason users see 403’s, but I have very little info to go on (learning of Jumble for the first time today). 😅

Gold priced in Bitcoin, last decade.

I’m not sure. I’m going to give you a full answer at the risk of saying too much. There are two layers of authentication in the Nostr protocol stack: - HTTP - This is where the 403 comes from. - Nostr (specifically NIP-42) - AFTER the HTTP connection, relays often ask clients to identify themselves, which determines what events they’ll send/receive from the client. You can think of this like a bar. There’s the outer door (HTTP/WebSocket), then there’s the bartender (Nostr/NIP-42) that checks your id and only serves you drinks if you’re old enough. Typically, relays will be permissive at the HTTP layer (let any client “connect”) and then rely on Nostr-level authentication to determine level of service. If you’re seeing 403 errors, that means that the relay is rejecting your connection even before getting to the Nostr authentication part. The bouncer isn’t letting you in the establishment. Speculation: It’s possible that the relays are rejecting regular HTTP(S) requests because they expect only full WebSocket requests. This is like a dress code. Shirt and shoes (WebSocket) required for entry. Technically speaking, the Nostr protocol only requires WebSocket support, so a relay COULD reject non-WebSocket requests and be compliant. It could be that your client is sending feeler requests ahead of your actual WebSocket requests. This is like sending a kid in swim trunks to check if the bar is open. He never gets past the bouncer (403 Unauthorized) even though you’re ready to party (WebSocket) and would have gotten up to the bar just fine. So if your client is making regular, non-WebSocket HTTP requests before connecting the WebSocket, I would argue that the client is perhaps misidentifying strictly compliant relays as “down” or unavailable.

You may have given up on the SUPERCYCLE, but the SUPERCYCLE has not given up on you. Keys be unto you. Blessed be your bags. 🙏

🔥

S U P E R C Y C L E

403 means Not authorized. You don’t have permission to view the resource. Contrast to 401, which is an authentication challenge. Once you authenticate, the 401 could become a 200 OK (access granted) or 403 access denied.

Not sure exactly what you mean by “previously used”. Your single sig “wallet” consists of a few different parts: - the seed - Often encoded as a BIP39 phrase of 12 or 24 words. - the derivation path - Determines how the software wallet generates addresses. - the hardware - The physical signing device that holds the seed material. Multisig uses a different derivation path than standard single sig. So let’s assume you don’t mean reusing that part. IMO, this is fine. You MAY reuse the seed/hardware from a PREVIOUS single sig wallet to participate in a multisig. When you do, all of the addresses that that signer contributes will be different than in the single sig case. So an outside observer has no way of connecting the two. If you use a seed/hardware SIMULTANEOUSLY for single and multisig, you run a bit higher risk, since an attacker that gains access to this one device now commands both. But I understand your question was about the PREVIOUS case.

Of all the streaming services I pay for, government is the worst.

How so?

The fundamental concept you’re describing is “earn coin for holding coin”. That’s how staking works, in principle. By having some coin and staking it, you receive more. Philosophically, this is a rich-get-richer scheme. Whoever has the most coin earns the most. This is not a new idea. It’s the status quo. In contrast, a Proof of Work system imbues no advantage to holders of coin over the earning of future coin, nor over the rules of that system. In PoW, you have to do the work to get paid, and you still can’t change the rules. It’s true that in PoW, having more coin to start with gives you an advantage in that you can buy more mining hardware etc. But if you buy hardware, you don’t still have the coin. You’re an entrepreneur. Risk and reward. Staking is a regressive system that entrenches existing holders to the detriment of future participants. Proof of Work is an entrepreneurial system that rewards stewards of capital, equally for all.

Your brain absolutely can run on fat. The “-glycer-“ in “triglyceride” means the sugar backbone that holds the fat together. When your body is using fat for fuel, that glycerine gets sent to the brain, while the body muscles run on the lipids. Ketone bodies derived from the breakdown of protein are also brain fuel.

We’ve all been there