This is by design, same as with bitcoin, and IMHO is key to the network's growth and adoption. And also same as bitcoin, it's perfectly possible to build privacy solutions on top of the network to prevent excessive dragnet surveillance and data mining.
Some of this work is already in progress with wrapped objects, peer-to-peer delivery, relay syncing etc but a lot more remains to be first imagined, then built and deployed.
Everything in its own time. Before PGP messages on pastebins, you need reliable pastebins.
They use a third-party ticketing service, which seems to be a rather normie biz, and you know. Normies gonna normie :)
Speaking of normie services, I'm still banned from meetup.com - any suggestions how I can register for the Nostrdam meetup, or shall I just show up?
I used to do multi-day stopovers on the trips from SYD to Europe via Asia (SIN, BKK, KUL), but since the lockdowns it's usually been a 2-hour quickie via Doha or DXB.
Funny how time preference works and how easily it is manipulated.
Thank you for the reminder that flying used to be (and can again be) fun :)
Oh - sorry, I assumed you meant the coin owner's privacy and I wanted to point out that there's also a community privacy element to it. But you're right, technically it's still privacy related.
Here's just one reason:
A strategic element in the privacy war is the uncertainty of coin ownership (by you as well as others). Ideally this should be increased as much as possible.
By solidifying (definitely re-confirming) your ownership of those UTXO's, consolidation transactions shrink down the volume of unattributed UTXO's on the blockchain, which indirectly degrades everyone's position, including your own - via increased vulnerability to chainalysis etc.
Not exactly Nostr specific, but I'd be happy to do a Tor/privacy workshop (branching into p2p comms, self-hosting etc) if there's demand. Let me know.
> How do you decide which peers to sync with on Amethyst P2P? There are so many users.
It can be done, here's just an example:
It should be possible to generate an onion address keypair algorithmically from the recipient's Nostr keypair, in a manner that is reproducible on sender-side using only the public key. Roughly similar to how Bitcoin HD wallets (xprv/xpub) work.
There are probably some privacy footnotes with this method, but would give you 100% accurate peer discovery without an intermediary.
Just to be clear, none of this exists. It's only an example of how it could be done.
Update: I'm coming to Amsterdam. Nostr meetup?
It's easy when you know your stops.
Most people these days don't realize that, for example, for a fixed ISO, [1/250, f/8] is the same exposure point as [1/125, f/11], or [1/60, f/16] etc (this is what the thumb wheel on your Nikon does in P mode - it cycles through various equivalent shutter/f-stop pairs). Give one stop here, take one stop there, you end up in the same place exposure-wise - but different composition-wise.
It's such a beautifully unpredictable world, and yet so structured at the same time. Wish you best of luck in your explorations. :)
Cat, the pictures are lovely and I like your play with depth-of-field, but: your ISO 2800 is WAY TOO HIGH for the situation.
Keep in mind, your sensor's real sensitivity is probably around ISO 200; anything above that is just amplification, and with amplification also comes noise.
Now, your post-processing work does a great job of reducing that noise, but does so at the expense of sharpness and detail. You'd be better off not introducing the noise in the first place.
When shooting in clear daylight (like the pics above), consider keeping your ISO in the 200 range. Maybe go up to 400 in semi-shade, or on overcast days, or if your subject is moving so fast that you need to go high on the shutter speed. Your pictures will be sharper, your shadows deeper and your color gradients smoother.
I hope this helps :)
> if you care about your privacy, you should use a VPN
From what I've read, VPN technologies are mostly used by fiat companies to connect branch offices and remote workers to a central office. How would using this fiat tech *solve* my privacy concerns when connecting to a nostr relay?
> Need a fake normie name to use for business purposes.
Wouldn't a *real* normie name (like David Jones) work better for normie business than a made-up name of questionable "real"-ness?
Put simply: are you trying to blend in or stand out?
Because hey, free hosting :)
Oh, OK, thanks. I misunderstood your statement to mean that the inner event's metadata leaks through the wrap, which would have been catastrophic.
> they give a false impression of no metadata leaks
OK, most of your reasons appear to be purely personal, but this one is scary if true. Where's the leak and how can it be prevented?
> Even some major nostr relays seem to be doing Tor blocking now
Ed, I've been a Tor maximalist for nearly 10 years, and can definitely relate. But I think the Tor friction that we've been experiencing on nostr is mostly due to naive operators using Cloudflare to front-end their services and relays, rather than malevolence (as is definitely the case with centralized platforms).
Most of these people have never run a server before, and while it's sad to see them walk straight into the Cloudflare funnel, in my opinion it needs to be part of their learning curve - just like a bitcoiner's shitcoin period.
I think as the network matures and the rubber meets the roadspikes, Tor friendliness will emerge organically. Give it a year :)
Sorry to hear that. Just a couple of points that may help:
First, the Tor access performance is not a linear function of your bandwidth, it's more of a "whichever is lowest" function between your bandwidth and that of the onion circuit that you're on at the time - which rotates regularly, and can also be changed manually. So, while you may notice slowness every now and then, it won't be consistently awfully worse than using the Internet bareback, and the benefits should outweigh the inconvenience.
https://metrics.torproject.org/onionperf-throughput.html
And second, if there's a government firewall getting in the way, one of Tor's available pluggable transports ("bridges") should take care of that for you.
Have you tried Tor? It's supposed to fix this type of problems.