And for the toastr bot: Find me on the ostrich app as npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6
Pitchforks stowed away again. It only took a crash of Amethyst for the Notes to appear.
Consistency never was a promise in nostr I guess.
I am confused. Two of my TextNotes that I cannot find over the last 10 minutes in my Amethyst ... carefully eying my pitchfork collection ...
Ah, boring. I thought it would end in the commit hash matching.
nostr:npub1sy70twa0vadtk8hjs6wt2hmfszduj04tw78ccs3ktmr9u99mfmqsj62srx and I are betting on this to some extent. But so far, badges are not well supported by clients in a sense that nobody would notice if I copied your badges. The issuer matters and a copy should be recognizable as such. With that, you can attribute meaning to each badge.
If you had an account on Localbitcoins for example, you can chat with our bot nostr:npub1kdvs6qnv8eta07w2t04sq3d57c2k97hek9q5x0xluww4vretrtjq6f8zev and it will attest to the fact.
Now, people can consider such accounts as less likely to be bots but if we screw up and give 20 nostr accounts a badge based on the same localbitcoins trader, people should disregard our badges.
Are people getting forced updates here?
Are people getting updated even though they are not on testflight and opted out of updates?
This would have severe security implications and I would like to know if that does happen on iPhone. I have never heard this to happen on Android.
Is it coal or gas/electric?
Other than that, what I learned way too late: Flip it only ever once. If you get your timing right such that it has a crust outside and the required cooking inside (and not more), then you get perfect results. Flipping it more will dry it out. If it burns else, you have to reduce the flame but not flip the meat.
???
If the current version doesn't want to be updated unless user approval, the new version has no way of forcing you. The current version could be programmed to auto-update but that's a different issue.
It massively limits your exposure. In nsecbunker you can define rules that the hacker can't overcome.
Yes, browser apps are a security nightmare. PWAs are browser apps. But we are fixing this one signature at a time.
On Amethyst I see you trice in the list of zaps. I don't get Snort to show any zaps on this message.
I see lxd looks more like podman than qemu. Interesting.
Trying first steps with qemu. Really quite cumbersome compared to docker/podman where I can just name an os and version and the rest magically happens like so: `podman run -it --rm --volume=$PWD:/bla/ --workdir /bla/ docker.io/ubuntu:20.04 bash`
So if I need throw-away linux environments, I usually use docker or better podman but when the need arises to run docker, doing so inside of docker or podman is not easy.
What is the easiest way to drop into a shell on a VM that works like any VPS of your random web hoster would?
Clear cookies and site data ... did not help neither. I see no zaps in Snort and log is full with the mentioned error.
Deleted that one table and don't see zaps after tab reload.
Opening the dev console, my firefox just needed a restart and the log was full of `Error: Uint8Array expected`. Now after a restart I also see this line with this stack:
```
14:52:25.648 Error: Uint8Array expected
bytesToHex utils.js:35
decodeInvoice invoices.js:24
a Zaps.js:11
parseZap Zaps.js:17
e Note.tsx:82
M Note.tsx:81
React 2
Pb Note.tsx:80
React 8
invoices.js:34:16
```
So an NFC enabled app can ask your ring to receive sats and the ring signs? And you holding your phone normally is enough for any background app to do that? What can you do if you bleed 2000 sat every odd hour? How long until you really it's actually one of those 500 apps on your phone? And once you have your phone under control, how long until door-knobs bleed sats?
I mean it's cool and sure, you can set limits but if you set those limits too high and many people use such a device, bleeding will happen everywhere. If you set the limits too low, there goes your convenience.
Your comment doesn't parse well here. Can you confirm the update happened because of testflight still being on auto-update?