A lot of people on this thread's comments saying how they love the walled garden: https://news.ycombinator.com/item?id=36346254
I suspect apple users who love the walled garden are going to wake up someday and realize they've been seduced into more and more compromises that didn't seem like a big deal at the time - or like a frog being boiled they won't even wake up, they'll just find themselves locked out of everything interesting and cope in their "but I like the shinies so I must be happy" kind of way.
Are there any Nostr client apps supporting _both_ NIP46 & NIP26? I've added combo support to my Keystr signer app, and I don't know how to test with real-world apps...
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet
nostr:note1p9v29uxqr8gz6rnwndxs2w0g4uhg3l6l77az2nqfucgpmdp5pgdqs76em3
gossip only does NIP-26 not NIP-46.
I take good care of the sheep. I hate to see them suffer, and I fix anything as soon as I notice it, like hoof problems and limping, or flystrike (a dreadful thing). They seem to live happy lives, happy to have plenty of food and happy to be in a flock, and to do their breeding. The suffering at the end is as short as I can make it and I'll leave out the details.
PLEASE DON'T TORTURE ANIMALS to get tasty meat. I didn't think that anybody would use this knowledge to do so, but now I think maybe I should have kept my mouth shut.
I will always attempt the cleanest quickest most painless stress-free kill possible. The difference in flavor isn't so significant that I would wish for another soul to suffer. That meat would have to taste ridiculously orgasmic, and even then I can't bear to wish suffering on another conscious life form.
I agree without a double-blinded test you can't know, and science would require multiple tests.. but that would be unethical. I expected it to taste bad, as did the other guy who took some home. I noted how good it tasted, and then later when we met again he, without prompting, said it was the best lamb he ever had. So that is not double-blind, but better than just my word on it.
I always heard it was the adrenaline, that it tainted the meat, made it taste bad. Arbitoirs here talk about how they use techniques to lower the stress on the animal first, even to the degree of killing them in a dark room. So I was really suprised.
I've always heard that if an animal is stressed before it dies, the meat doesn't taste as good. But among the few wiltshire sheep that I have accidently killed poorly, who unfortunately suffered a bit before I could get them properly killed, actually tasted better than anything I've ever tasted. I'm sad to think that animals might want other animals to suffer a bit in order to ramp up the flavor... terrible thing, and not something vegans are going to want to hear.
I've also heard that older animals don't taste as good. But I've found that sheep that are about 3 years old taste the best -- not tough yet, and full of flavor. Too old and they get tough. "Lamb" (up to 1 year old) may be the most tender, but the flavour hasn't developed enough yet.
If gossip adds zaps, will gossip users finally be able to hear people saying "thank you" with satoshis?
Question for relay devs: I want to subscribe to all events that augment the events I'm currently displaying (zap receipts, reactions, and deletions). I'm considering making subscriptions with a long set of IDs in an "#e" filter. So my questions are:
1) How long can that get before relays complain the list is too long?
2) If I add a bunch of IDs to an existing subscription, does it start over, or does it remember that it already gave results for the previous ids? (I presume it would start over, which won't be useful for me)
3) If I then instead open new subscriptions every time I need to watch another batch of events, how many of those can I have before the relay gets mad at me? Because I'd be making new subscriptions every 10 seconds or so for a very long time without closing the old subscriptions.
4) Would it be more efficient for me to be watching all the events my user might see on screen all the time, or should I dump and restart subscriptions whenever the user changes to a different feed? That second method would be watching much fewer events, but would rewrite subscriptions frequently thus pulling redundant data.
I know I can look at the NIPs and program to that, but I thought I'd get to the best plan of attack faster by just asking.
nostr:npub1xhfxu35se0s63x90v8xr29txr66l5a3m277skshy2zvu3ve0658sla4xw3
nostr:npub1qqqqqqyz0la2jjl752yv8h7wgs3v098mh9nztd4nr6gynaef6uqqt0n47m
nostr:npub1yxprsscnjw2e6myxz73mmzvnqw5kvzd5ffjya9ecjypc5l0gvgksh8qud4
Everytime I sit down and work on putting zaps into gossip, I find some problem with gossip that needs to be fixed first. This time, it turns out we aren't correctly subscribing to all of the events that modify other events (reactions, deletions, and zaps) and in order to do so we need to modify specific filters within existing subscriptions which we haven't been doing yet either. So I'm naming each filter in each subscription so it's easy to address and modify. Next I'll update those subscriptions with the list of IDs from the feed you are looking periodically if that feed has changed. Far removed from zaps, but that is how I got here.
I guess for existing gossip users, just be aware that reaction counts have always been low. I want to do better for zaps... even though I know we can't find all the zaps that apply to a note, I want to do the best I can given the relays you are connected to, and we aren't doing that today.
Yes I see this.
This morning i was getting 2.5 Mbps down, 1.28 Mbps up... then 0.00 Mbps up as everything timed out, then it would come back. I called customer support and they tried to sell me to a higher plan instead of resolving the problem so I promptly cancelled. I'm looking into starlink now.
The Barbara Streisand effect. She didn't want her house on Google Maps, and then everybody looked at her house on google maps. Apple suggesting banning Damus, now everybody wants to get on nostr and see what it is about.
But whenever I hear her name that song comes into my head.
... then mix that into https://www.youtube.com/watch?v=vbmGfH_2mrI
You can run Android with Google in a sandbox. Then you get the Play Store and it's Google Services, but they don't get control of your phone or any apps outside of their jurisdiction. Daniel McCay did this very well in GrapheneOS.
I'm unfamiliar with iPhone jailbreaking but that sounds like a good thing.
I agree. There are levels of resistance.
Some protocols with high censorship resistance detect and route around censorship, blind the end nodes involved, hide communications steganographically, etc... nostr doesn't do any of that.
But beyond being decentralized, it is organized to rapidly and easily switch providers (relays), on every note you post if you want, unlike older decentralized protocols like email or UUCP, along with expected redundancy of posting.
So I'd call it fully distributed and somewhat censorship resistant.
Not being able to distribute a client through a walled garden isn't a fault - no client could possibly do that without the walled garden's approval.
3 completely bad reasons to write your own Nostr-like protocol that isn't Nostr, from https://news.ycombinator.com/item?id=36259930:
Nostr is pretty good and I was inspired by its idea. However, I didn’t like a few things and that’s why I decided to build my own protocol.
1. Nostr relies on Schnorr scheme for signing the data. While from my research, the patent on it has expired, I also read some other details on how there’s other pieces of it which are still patented. I am not a legal expert, so my understanding on this might be wrong and it might be in the clear.
2. Schnorr is fairly new and not used widely yet. It’s not even built natively in Crypto Subtle which comes built-in in all browsers.
Based on this alone, I couldn’t use Nostr. My implementation uses ECDSA P-384 keys which can be generated using the browser built in crypto subtle library:
https://developer.mozilla.org/en-US/docs/Web/API/EcKeyGenPar...
So this allows one less third party library to rely on the client side.
3. The 3rd reason (and this was one of my biggest reasons) was that Nostr runs on websockets. I didn’t like that at all. Servers are already limited on the number of sockets they can handle. Plus it seemed like unnecessary complexity when vast majority of the developers already know how to use REST api.
So instead of websockets, mine uses a simple REST api with only 2 endpoints: one for creation of records and other for searching for records based on filters.
Many of us too thought nostr wasn't quite right and we could do better when we first encountered it. With a bit of discussion, this guy would come on board.
