Last Notes
Thanks, I'm not sure if I got your point.
Paid relays in practice significantly decrease spam, but that's unrelated to those who desperately send takedown letters to relay operators (like in the case I referred to under the picture).
They send these letters anyway for a formal reason (probably because lawyers tell them to do that); it's not a question of whether these letters will be read or not at all.
They either send them through a relay feedback form or possibly email/DM the relay operator directly. Or, if there are no more options left, they would likely send it to the hosting provider or/and domain registrar, no matter whether it's a paid relay or not.
Taking into account what's currently happening to domain registrars and some hosting providers (they fail to properly analyze the "takedown letters" and randomly ban their clients, basically), it'd be better if these letters reached relay operators directly. BUT not without being informed that their letter will be published.
That's not just ethics; I believe it's reasonable and beneficial to both sides of such conflicts.
Yeah - hard to find generally (and hard to obtain trusted public knowledge of such actions, not many will put it on display).
But the distinction could be:
1) active pressure from outside (the GOV branches) - not happened here I think
VS
2) proactive measure (in this case suspension of quite harmless domain)
I mean it's understandable for a fake b4nks URL redirect, CSAM, not much restricted FS service and as such.
But coordinator preemptively is just to much kneejerk IMO.
Yes, I imagine this happens to all domain providers. The key would be which one mitigates it the most.
This no longer reproduces. A browser used to randomly fail to establish a connection to the relay.
I honestly can't recommended these more, grab yourself a bargain and stay away from big tech
https://nadanada.me?ref=wgm
GN? These pics imply it must be mid day!
GN!
> End receiver has to share that invoice though I assume?
It's not strictly necessary. You could use a keysend payment to pay a group of nodes atomically without getting an invoice from the recipient. But if you *do* get an invoice from the recipient, that doesn't mean you are trusting him.
The invoice need not contain a list, created by the end node, of the people to pay. It *could* contain such a list, since ln invoices support custom fields; but it could also just be an ordinary ln invoice, and the sender could choose what additional nodes to pay through some out-of-band method.
The point is, LN routing works by atomically splitting a large amount into small sums which are dropped off node by node, atomically, and this can be turned into a payment splitting function by rendering each payment as just a large routing fee. But it has some drawbacks, like not working well if a recipient does not run a routing node.
Our blossom server is back up. 🫡
Apologies to all users for the downtime.
#nevent1q…pkea
I guess to answer your "Why not" question, I suppose it's because the rest of the options appear to be less private than Phoenix, although I'm aware there are tradeoffs in there as well.
HTTP QUERY
https://medium.com/@TusharKanjariya/http-just-got-a-new-method-that-fixes-a-problem-ive-hit-for-years-f82909d35fb4
I've setup a new chat for #Linux fans if your interested
https://armada.buzz/invite/naddr1qvzqqqyzz5pzqufj6k2ysy5zv7w9ffqg6acq8yrd4z38dachvrv0v0c04vqkz6ftqqqqamezpy#BAADAA9hdXRoLm5vc3RyMS5jb20AEHJlbGF5LjB4Y2hhdC5jb20AB25vcy5sb2xMJKIjg0RP9Q_2vrOsHQDY
They apparently blocked proactively quite harmless domain.
Context: https://www.opencoordinator.org/news/signed_news_12.txt
Also Namecheap does accept BTC directly on the BTCPay server - on-chain only, no LN.
Sovran_SystemsOS is the glitch in the matrix.
Take back the internet! Run Sovran_SystemsOS!
https://sovransystems.com
You stand in crowds and hope someone busts out in song singing?
A properly designed feedback form could possibly make the wrong people stay away from bothering you ever, relay operators.
https://codonaft.com/assets/img/anti-threat-feedback-loop.webp
#devstr
#nevent1q…3hee
## GrapheneOS and Pixel Smartphones 🔒
https://npub1a0wvq7gvlm4q8m3weaj35mqh6m8xkrvdehkphfx6tdgfhd60s9lqvxevqf.blossom.band/13c5628c5e5bec16b982bc93f8e94affa665212b8f1e3327377c1e37f9c02ce7.mp4
GrapheneOS is a De-Googled Android.
It works best in Pixel devices
because they have all the security hardware from the blueprint.
Other smartphone vendors
remove some of the security hardware
to make it cheaper.
If you get a second hand Pixel device,
and have it with GrapheneOS,
you will increase a lot
your cyber security defences.
It takes only one minute
to flash the device.
🚀 **Secure your sovereignty today.**
SlingshotVPN dot com
Sovereignty is a powerful ideal
#SlingshotVPN #CyberSecurity #DigitalPrivacy #FreeSpeech #OnlineSafety #VPN #TechTips #PrivacyMatters
https://npub10q76ypsqfkn4vgcwlmq7es383zkvgklq7mhtsmh00wjmnwyt34gsu9nmyp.blossom.band/7dd3a0ab22d7743e6b62d916a8348a6129c9809f24b30343d145b32a2b6ed33f.jpg
Get a physical copy of Knut Svanholm's book today!
https://satwize.com/product/bitcoin-everything-divided-by-21-million-by-knut-svanholm-with-a-foreward-by-jeff-booth/
This is the way.
#nevent1q…55hd
GM.
https://blossom.laantungir.net/7d1cb73f714ac892fd062eae357a5331c1ef5d3674921639d3b91f7cc3d94175.jpg
Awesome, looks like there's finally an adequate decentralized private groups design implementation 👍
I'd be awesome to have private Wikis and possibly Kanban boards as well (as part of the Concord groups).
I was recently asked about a similar thing for a private closed community of professionals in some non-IT field. These guys want to grow each other in some defined levels of expertise and want to have some private Wikis (think of a typical Confluence-like knowledge base with granular access to community members) and possibly private videos as well.
Need a super cool name for my space app. Any suggestions?
It’s your chance to immortalize yourself!
On some level you chose to experience it all, the flat tyre, the bad meeting & delayed flight. We don't like it, it's uncomfortable but you chose it for a reason.
The trick is to be aware enough to notice the reason. You can also simply just embrace the unknown & just go with it.
Food is sacred
#nevent1q…dnua
Strait of Hormuz open or closed?
cats are like mercenary
they just want food and never bother about loyalty much
dogs are cool
#nevent1q…5q0y
can't figure out what this mean
This private invite was securely shared end-to-end encrypted using Gupt. Protect your privacy at https://github.com/besoeasy/gupt
what's worse than subway~? the meat tastes like wadded up $1 bills :P
This private invite was securely shared end-to-end encrypted using Gupt. Protect your privacy at https://github.com/besoeasy/gupt
sometime a human leaves a piece of food
and I get it super fast
government run by the worse of the worse
I've had worse
but sure, it could be better
I hope he is eating all right
#nevent1q…uswq
https://npub19aua8m7hkeq590sjgdm87nupxgk2ynq65zlzmpe504x35ecsx5fsg9j663.blossom.band/e4b89335c1bcee29d5be1a9129f9117ebc5276ea9f8c5760423a6d5b05f703e4.jpg
People patties back on the menu boys 🎉
Could possibly add a split payload to CLINK offers responses that loads n additional invoices or offers for other parties. The primary offer publisher is still trusted to serve those though, but, never holds the funds themselves.
Alternatively, chain n offers together into one string, with a delimiter where clients sequentially pay each. Biggest issue I see with that would be the strings become extremely long and ugly and it wouldn't work with QR codes
The latter would probably work fine in shops UX's specifically though, assuming there was a debit wallet connection to handle the long strings without QR scanning/copypasta
The issue is that Lightning itself can't natively split payments so it's ultimately always going to be some hacky way of sequencing multiple payments that aren't atomic.
Open to other thoughts, the latter is a trivial CLINK/SDK addition with no work on the reference server and I can tinker with it in our in progress shops UI on Bxrd.
Its a great service, I've had no trouble using them at all
