Uncaught (in promise) TypeError: r() is null
Immutable 11
promise callback* https://ostrich.work/:73
2.C2-pFGnn.js:10:4264
Cookie “_gh_sess” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. JPG.jpg
Cookie “_octo” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. JPG.jpg
Cookie “logged_in” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”.
And I cannot login. I have no extension enabled and those errors above. Would be nice to be able to login with Amber.
Nee, natürlich nur mit selbst-verwalteter Node im Backend. Alles anderes ist Mist.
Ahahaha geil und ich dachte schon.... da stimmt doch was nicht :-D
You could use: https://trocador.app/en/anonpayurlgenerator

What do I do if the BTCPay server does not reliably send the Zap event back to the relays?
Do I then have to query the invoice for payment myself, which would be more stable, or?
Um es nochmal zusammenzufassen:
Amber auf Android als Signier-Software für seine Nostr-Keys zu verwenden und sein nsec nirgends mehr in andere Software oder Clients einzugeben ist genau die bitcoin-art.
Amethyst unterstützt das bunker:// Protokoll. Also brauchen wir auch nicht mehr dort unser nsec einfach so blank eingeben.
Andere Clients ziehen nach und auch dort ist Nostr-Connect mit Amber dann möglich.
iOS-User schauen mal wieder in die Privatsphäre-Röhre. Die könnten aber so etwas wie nsec.app benutzen, welches dein nsec im lokalen Storage des Browsers hält, um dann über das bunker:// Protokoll Events zu signieren.
Also Ziel ist es so gut es geht, nur noch eine Applikation als Signier-Software und in Zukunft noch besser sogar Hardware-Signatur-Geräte, für Nostr zu verwenden.
Die Amber Software kann hier selbst kompiliert und geprüft werden: https://github.com/greenart7c3/Amber
To summarise briefly:
The election was not secret. Anyone can look up the events on the relays we use and check whether the respective nostr keys have also voted for the person in question.
The election was not yet super decentralised, as we only used our own internal relays because I was experimenting with two new event kinds. I would like to find out from real Nostr developers whether this was at all useful and whether someone can build a professional NIP or something similar from it. The storage format is also open to discussion. For the time being, I pragmatically used something that worked for me.
So we're talking more about a first proof of concept attempt to see how it works without email etc. In other words, we validate Nostr accounts and see whether it really is our active members who are signing Nostr events.
The whole issue of whether a Nostr key has been compromised is not yet part of this.
You will find the code here: https://github.com/HolgerHatGarKeineNode/einundzwanzig-nostr/blob/master/resources/views/pages/association/election/%5BElection%3Ayear%5D.blade.php
$note->setKind($board ? 2121 : 32122);
if (!$board) {
$dTag = sprintf('%s,%s,%s', $this->currentPleb->pubkey, date('Y'), $type);
$note->setTags([['d', $dTag]]);
}
I have simply invented two new custom kinds. The president was a replaceable event 32122 and the confirmation of the board members was an event 2121.
I used simple ‘content’ to store which pubkey has voted how: $note->setContent(‘$pubkey,$type’);
This can be rubbish and would be better packaged professionally in a NIP design.
I'm not sure how to do this ‘properly’ with a NIP.
Nsec direkt eingeben geht tatsächlich nicht. Das wäre zu unsicher. Es geht NSEC.APP dort liegt es dann im local storage deines Browsers. Aber morgen im Detail mehrm liege schon im Bett :)
Amber und Co fungieren als Signatur-App, also genau wie auch Software Bitcoin Wallets funktionieren.
Will this also affect Vaultwarden or Keyguard for mobile?
Would be really cool if nostr:npub1eaz6dwsnvwkha5sn5puwwyxjgy26uusundrm684lg3vw4ma5c2jsqarcgz had a popout chat box so I could show it during my live shows.

It's all there. See your streaming dashboard.
GM from?

GM 
Hey, I've been running Haven on Podman for a while with no problems (though I’m running it in rootful mode, so it’s not exactly best practice). I also authored the now-defunct docker-compose-ssl.yaml in the official repo, which included an Nginx reverse proxy with HTTPS support + automatic Let’s Encrypt certificate creation and renewal. nostr:nprofile1qqsq4hm8gawvch9y2m7nqghydaw4ym4s4a3gf0u9f9xqm4uy0ul9qvcpremhxue69uhkstnrdajxjmn8v9ex2mnp9e6x7up0da6hgcn00qq3vamnwvaz7tmwdaehgu3dwfjkccte9eshqup0qyghwumn8ghj7mn0wd68ytnhd9hx2tcht4zgq, are you accepting contributions? Also, does this sound useful at all? If so, I’d be happy to adjust it and contribute to your repo.
Yes, of course. You can send PRs here: https://github.com/HolgerHatGarKeineNode/haven-docker
I always use my own Nginx server as a proxy in my infrastructures, so I haven't had any need for this so far. If someone wants to start an Nginx proxy with Docker, they will be happy to have an opportunity to see how something like this works.
I am also a fan of traefik.
Mache grad die rustlings durch.... sehr nice. Danke dir.
Ok, I am learning Rust now...
GM, cool auf Nostr!
Bin nur noch auch SimpleX, Signal und hier. Öffne bei Nostr DMs nur GiftedWrapped Messages ;-)
SimpleX: https://w3.do/TIBkuQ9K
am not liable to pay tax anywhere
In the german army we have: VENÜ
Vormachen, Erklären, Nachmachen, Üben
