tpaschalis @tpaschalis@m.tpaschalis.me

I used shelter via f-droid and that worked. Thanks for the suggestions!

First time in my life using #WhatsApp and it's a cesspool of dark patterns, forced "consent", and deliberate lies. I expected it to be bad, and it still managed to negatively surprise me.

Good thing I won't have to touch it again after this.

I like how this developer effectively made himself a private software modchip to play PS1 game xD https://www.gamesradar.com/after-23-years-developer-reveals-he-snuck-a-cheat-code-past-sony-that-turns-a-cult-classic-horror-game-into-a-godsend-for-retro-enthusiasts/ #gamedev #retrogaming

Multifactor auth factors:
* something you are
* something you have
* something you know
* something you feel
* something that has been revealed to you
* something always known, but not by the conscious mind
* something hidden in the space between moments
* something dreamed about, unremembered

Battlestation thread!

I posted to my desultory blog the transcript of a talk I gave in 2009 inside Google, mostly because someone recently asked me to, feeling the message needs reinforcing.

https://commandcenter.blogspot.com/2023/12/simplicity.html

First time in Miami and excited about a virgin voyages cruise

have you ever bent light with your fingertips?

pinch your thumb & forefinger together, do the same on the other hand, bring them together, where all four digits touch there’s a tiny hole

bring your hands up to your eyes, and make the hole as small as you can & things far away will now be in focus

congratulations: you have diffracted light using only your hands

I don’t know if any time of my life has blurred together more than the last four years

My talk from last week’s Observability Day is up:
“How Prometheus Halved Its Memory Usage.”
It’s a thrill ride.

https://youtu.be/29yKJ1312AM

The Forbes 30 doing 30-to-life now includes SBF and Elizabeth Holmes.

I’m on my way to Chicago to give a talk about Prometheus and memory usage. See you there!

#KubeCon

https://colocatedeventsna2023.sched.com/event/1Rj51/how-prometheus-halved-its-memory-usage-bryan-boreham-grafana-labs

the HTTP2 rapid reset issue reveals that Go has it's own dependency hell... google.golang.org/grpc declares which version of golang.org/x/net it's using, and so it's not just "update golang.org/x/net" in your application and you're safe, it's also "update GRPC in your application"... and of course this is now "update every module that uses GRPC and refers to an older version" which is now a huge sprawling mess of modules.

it's all fine saying that Go is always backwards compatible and doesn't require older versions to have updated, etc... but the reality of it is that security issues kick you in the teeth hard and the cascade of dependencies require you to update virtually everything anyway. it would be better to embrace "update everything all the time" then to have an illusion of "you only need to update your thing and not worry about other things" as the latter means you have no muscle memory or build tooling ready when you actually need to update all the things.

I like Go a lot, but I don't find the dependency / updates / supportability philosophy that they've taken on to be internally consistent or truly viable long-term, I've always held that they're smarter than I and implicitly this means I'm probably wrong, but as time passes I'm not so sure I'm wrong (I am sure they're smarter than I am though).