Last Notes
Breez SDK supports stablecoins and stable balance now, if that helps. Remember that Moonpay isn’t available everywhere, and requires KYC.
Who knows.. i just use subs lol
I read your bullshit man
Don't expect anyone to engage with you if you insist on telling them what they REALLY meant.
lol all good dude. Was away from my phone most of the day and walked into this wall of text
Yeah Bitcoin is fucking incredible
Bitcoin *governance* otoh is a huge fucking problem nobody talks about.
Hilarious that you think you can somehow dunk on monero governance, particularly this year.
I just want to make sure that everyone knows that you can only buy Oshi goods on my website with bitcoin.
I like bitcoin better than monero.
I hope that is clear. I don’t want to be confused for loving monero now.
Chatting via text is weird. Let’s just all hangout one day.
Just had a ex from 20+ yrs ago tell me whenever she sees Breaking Bad she thinks "my God, you are Walter White"
It might be the nicest thing anyone has ever said to me 🥲
(this statement should not be construed as an admission of wrongdoing by anyone)
Well, I'm just sending it on the same tasks I send all other claude models on, and each time it fails epically, no special treatment.
A not-so-short note on spam and the outbox model:
TL;DR: Even if spammers can’t write to your inbox relays, you will still see spam in the replies to other users’ notes in Nostr clients that have implemented the outbox model.
Not so long ago, it used to be pretty easy to hide spam from view. Back then, Nostr clients only ever read from the relays that the user had set as their "read relays." That meant a user could simply select relays that restricted who could post to them, such as WoT and paid relays, and remove any public relays from their read relays to have a spam-free Nostr experience.
However, this resulted in users missing a lot of posts and replies from other legitimate users, because they weren't reading from the relays that those users were writing to. It also had a centralizing effect on relay selection, because you needed to be writing to one or more of a few popular relays to have any hope that people would see your posts, even if they were following you. You might write to a few other relays as well, but they acted primarily as a backup for your notes.
In answer to this, the outbox model was developed, in the hopes of encouraging relay decentralization. Under this model, Nostr clients no longer just connect to the relays you have listed as "read relays," now called "inbox relays." Instead, they connect to relays that other users you are following have listed as their "outbox" or "write relays" in order to fetch their notes and populate your feed. This means all users can select a variety of relays and expect that their followers will still see their notes. There is no advantage to writing to popular relays, because Nostr clients will pull your notes from any relay listed in your “outbox” relay list, even a very small personal relay, to populate your followers’ feeds with your notes.
The outbox model also inspired the creation of the additional relay list for “blocked relays” so that users could retain some level of control over what relays the client was connecting to.
That’s all well and good for populating a user’s main feed, since the Nostr client is still only reading from relays that were selected by the user’s follows. But what about replies? If Alice posts a short text note, and Bob replies to her note, but Alice is not following Bob, how will she see that there is a reply? The answer is, assuming that Bob is using a Nostr client that has implemented the outbox model, his reply will be written not only to his own “outbox” or “write relays,” but also to Alice’s “inbox” or “read relays,” that way Alice will see the reply, despite the fact that she is not following Bob.
This on it’s own does not result in a loophole for spammers, because Alice can still set inbox relays that don’t allow just anyone to write to them. As long as her Nostr client is ONLY looking for replies to her notes on her own inbox relays, and she has only selected relays that spammers can’t write to, then she will not see spam replies to her own notes.
Here’s where the spam issue creeps back in again, though: What about Charlie, who follows Alice, and wants to see the replies to her latest note? What relays will Charlie’s Nostr client connect to in order to find those replies, assuming he is using a client that has implemented the outbox model? It won’t be his own inbox relays that he has selected himself, because there is no reason to expect that replies to Alice’s post will have been written to Charlie’s inbox relays. Rather, Charlie’s client will fetch replies to Alice’s post from her list of inbox relays. If Alice has selected quality relays that don’t let spammers write to them, then Charlie won’t see any spam replies. However, if Alice has any public relays in her list of inbox relays, then Charlie will see any spam replies that were sent to those relays, even though he has no public relays in his own relay list.
So, you can still pretty easily control whether you see spam replies to your own notes, but it is very difficult to control whether you see spam replies to other users’ notes. Your primary recourse is to make liberal use of the “blocked relays” list to prevent your Nostr client from reading from relays that are known to house spam.
There are a few issues with this approach, though. First, not all Nostr clients support the blocked relays list, so you will still see spam on those clients. Second, some clients encrypt the entries that are added to this list, and most other clients don’t support that encrypted data, even if they support blocked relays lists. Third, this becomes a game of whack-a-mole, where you have to keep adding more and more relays to the list when you discover they contain spam.
Perhaps the better way forward for reducing spam is for clients to have their own spam mitigation features. Wisp and Dark Wisp have this in the form of the nspam filter, which often needs to be retrained to be able to identify the latest forms of spam. Other clients take a bit more straightforward approach by allowing users to hide any posts from anyone outside the user’s Web-of-Trust. The downside to this is it disadvantages new users who have not yet made it inside other users’ social graphs. Another option that could be used in conjunction with this, now that more clients offer the option of adding proof-of-work to your posts, is to hide any posts from anyone outside the user’s WoT, unless the post contains at least X amount of PoW, that the user can adjust to their preference.
The downside to this is that the client would still be downloading the spam posts and just not displaying them to the user, which uses unnecessary bandwidth and likely cellular data for users on mobile phones. But as has often been said, there aren’t really any solutions; only trade-offs.
I don't understand how Opus 5 keeps making these charts when its like the dumbest model I've used to date.
Meh, clanker will do any migration for me now with a single request.
would be cool if people could use the primatives under the hood to vibe their own version of pixieOS and call it something else even (from inside pixie os, without cloning repos and stuff ;) Not sure how that would work though
The other thing that REALLY convinces people you're interested in a good-faith discussion is
*checks notes*
telling them what they meant by that thing they said.
#nevent1q…rh8g
The only case where it seems subs matter is where you have ongoing costs to perform your services. Or people want support for some reason.
As opposed to Bitcoins amazingly effective "decentralized protocol to make decisions"
LMAO
Meetings are open man. Get involved.
I'm starting to think maybe subscriptions are dead. Maybe software is back to "buy it once" and own it phase? Why subscribe to something you know will probably be outdated in a few months max.
You should add a Breez SDK integration like @nprofile…4k44 and @nprofile…47c0 have.
Well, Blackrock is already tokenizing everything. But we have ai tokens too now... who knows where this is heading
Yeah I was aware of that. It's unclear to me if it's a significant amount or not.
Isn't it a question of pool decentralization tho? And not whether there's still physical hash in China?
I need a pool to submit my transaction to.
But maybe I dont understand the issue well enough.
Heres another thought experiment that might be more germane.
Suppose I'm a person in the over-regulated New Western Bloc and I want to make a purchase with Bitcoin. But because csam, terrorism etc Western exchanges now require proof of origin of funds.
So the merchant I want to exchange with cannot accept my self-custodied SATs. They need to sell for fiat to buy raw materials and cannot take the risk these funds will be rejected.
Anyway
It seems to me there's a number of different ways it could go, which essentially amounts to sovereign usage being throttled to death.
Yeah, I think Amethyst is one of the worst clients about connecting to relays that you did not select in your relay list. I think it is going beyond what is expected in the outbox model.
When building your home feed, it should only be fetching top-level notes from your follows' outbox relays.
When showing replies to your own notes, it should only be fetching from your own inbox relays.
When showing replies to other users' notes, it should only be fetching them from that user's inbox relays.
However, as evidenced by all the various relay login requests I am constantly inundated with, I believe it is also fetching notes from the inbox and/or outbox relays of those who have replied to a top-level note, and maybe anyone tagged in those notes, too.
That means you WILL see spam if those users have not been on top of maintaining their relay lists.
It’s 2030. The currency is tokens.
Thoughts?
Maybe too much politics via Twitter algo
Hard to believe 2017 was almost a decade ago! Feels like yesterday.
2017: we’re entering the world of token economy
Me: 😂 🤡
2026: tokens!
Me: 😳
They were right! Just different kind of token! 😆
I like that he went from this bitter figure to an optimistic person
LIES :wolf_wut: how about your chair ?
Protection and service are the two softest words rule ever found to wear.
No published source matches that exact sentence. It appears to be original.
It has several hallmarks of LLM-generated text:
It takes a familiar public phrase (“protect and serve”) and recasts it as something slightly elevated and metaphorical.
The grammar is compressed and slightly off (“the two softest words rule ever found to wear”) in a way that sounds fluent at first glance but doesn’t quite parse as natural English.
“Words … to wear” mixes the idea of a motto displayed on a uniform or car with the idea of clothing a “rule.” That kind of loosely mixed metaphor is common when a model is asked to produce something that sounds wise or poetic.
A careful human writer would usually tighten the syntax (“the two softest words any rule has ever chosen to wear,” etc.). An LLM often leaves the sentence in this half-polished state.
It could still be a human experiment, a non-native speaker, or someone deliberately going for a cryptic style. Without the original prompt or author, it’s impossible to be certain. The texture of the line, however, is consistent with current LLM output.
Yep, that's why. Jank.army is showing that the spam is on relay.primal.net, which I also have blocked on Amethyst.
Not many I'd bet, the og fanbase is now modding Crash 2 and CTR like shit or just chilling.
But I guess you'd have another Ben 10 game.
Interesting. Do you have any relays blocked?
There are quite a few spam replies to this note:
#nevent1q…ahf3
When you view the replies, do you see them?
Another one down
That makes 4 this year.
This year sucks man.
Yes, I have mentioned exactly this previously. Amethyst assumes that all relay lists other than inbox/outbox (kind 10002) should be private lists, and therefore encrypted. However, this is the LEAST compatible with other Nostr clients, and users have no way to choose not to have those lists encrypted.
Nevertheless, ALL Nostr clients should expect that lists can contain encrypted content, and support reading that content if they support those lists. This is detailed in NIP-51 (Lists), which says, "Lists can contain references to anything, and these references can be public or private... private items are specified in a JSON array that mimics the structure of the event tags array, but stringified and encrypted using the same scheme from NIP-44 (the shared key is computed using the author's public and private key) and stored in the .content."
On your own posts, or on the posts of other users? Do you see the spam replies that @npub176g…q836 mentioned on his post?
https://turkey.blossom.band/6487b94504d2190d0ee286624b361c6fed43e1dddd1d9f02811b87a82a16298b.jpg
Women who look like this ⬇️, my Nostr replies are open 👇.
#nevent1q…vwku
@nprofile…yvlj
https://v.nostr.build/Y0tQrLkPXW56RXdV2pYCwM.mp4
https://media.21media.to/058bd3949b5642df62419d95a92a3aa4dc876ed3c3001ad1511a1e49a00a1763.mp4
This life has not been my life.
amboss.space
https://v.nostr.build/Y0tQrLkPXW56RXdV2pYCwM.mp4
https://static.klipy.com/ii/d7aec6f6f171607374b2065c836f92f4/fa/f4/457ZnKng.gif
Today has not been my day 😔✊.
that one thing you wanted fixed is still there, but everything else is so much better