Phase 1: cause netsplit.

Phase 2: join empty channel with ops on split server.

Phase 3: wait for netsplit to resolve, deop all other ops and take over channel.

Until networks build advanced channel registrations.

Feeling all nostalgic now.

This was really bound to happen sooner or later and in all honesty this is the absolute least amount of annoyance they could cause. It could be so much worse. This is easy because better filtering will be introduced and we will be better prepared for the things that will be far worse.

I'm always on the 1200 - 2000 window with mostly 2 meals.

You must be one of those big breakfast, medium lunch and light dinner guys.

Isn't the problem that they could be compromised enough already? Here's some thing that could eventually lead to issues:

1. They have your phonenumber. Which in 99% of the world means it will lead to you when things get "seized" (stolen).

2. Their servers are centralised meaning that if things get "seized" (stolen) they may at some point find a hole, or a a brute force attack vector that will be able to do something with that data.

I am not saying it is not secure (right now) or you should not use it, but it makes it really easy to apply a lot of pressure on a single point and that is something you have to consider if you need absolute privacy.

The article specifically states that it's a good idea to reuse cryptographic libraries that have been well tested.

I think it's even fine to initially take on the technical debt of a dependency that lets you get real world experience with an idea faster, as long as you accept the possibility that this dependency probably requires more scrutiny if you intend to keep on using it.

It's complicated and definitely not a black and white case that you should do something yourself. Both ways can go horribly wrong.

While i agree to not blindly inject any dependency that seemingly makes you productive faster having everybody implementing their own json parser (for example) going to be just as bad? It's not going to be 1 huge CVE that affects many apps it's going to be many CVE's for every single app/implementation.

There's probably a middle ground here that is not the worst of both worlds.

GM!

You can do groceries at Spar central station. Renting a house with bitcoin is possible but it's not like all landlords accept it. I know some that do though.

You can easily get an idea of what you can buy with bitcoin (lightning) on https://arnhembitcoinstad.nl

I'm feeling the purple!

For those wondering: yes it was as delicious as it looks!

I dunno what you've been hearing but feel free to ask and i can verify it for you.

Or pull a Hanlon's Razor. Power always blinds and corrupts.

You had me there for a second because of the order in which i read these things. 😅

I'll see you tonight! Stay humble and eat Indonesian delicacies! 😋

Sometimes you just have to deliver that value.

- Method not allowed

- Not acceptable

- Proxy authentication required

- Request timeout

- Conflict

- Gone

- Length required

- Precondition required

Etc

A whole lotta nothing

And then you start at the server errors.

I am always baffled at the fact that all solutions for all problems must be solved at the citizen level.

I'd just take 3 bags and throw whatever is left in front of city hall.

Reminder: It's this Thursday!

nostr:nevent1qqsvu2tk7cjsxuuf9avn7zq8tu6avufexr03qmd4qkhg74j8ehjdtegpr4mhxue69uhkummnw3erxtnyv9jkgctvw4ekcctzwvhxjme0qgs2a5vnhea6ph3f85furxq7fl34reztwz622lq8an4vu2l2rgjzz4grqsqqqqqphakzpp