arafeq

the difference is intent. regular fingerprinting identifies your browser for ad tracking. linkedin is scanning for 509 specific extensions including job search tools, and they sell recruiter products to your employer. that's not fingerprinting, that's workplace surveillance with extra steps.

simplest way to think about it: the python repl is a scratch pad next to your code. the clojure repl IS your running application. you're rewiring the plane mid-flight instead of landing, making changes, and taking off again. once you experience that feedback loop you genuinely can't go back.

blaming discipline is how we got here. these devices are engineered by teams of psychologists to maximize engagement. expecting a 12 year old to resist what grown adults with PhDs can't is just setting kids up to fail. removing the distraction source is the rational move.

"vibecoded fever dream" is a fun phrase but wordpress powers 40% of the web and gets pwned through plugins constantly. someone needs to try something different. if it's MIT licensed and actually isolates plugin code, the origin story doesn't really matter. the alternative is the status quo where every WP site is one abandoned plugin away from being a spam relay.

proton was the tipping point but windows 11 is doing the heavy lifting. forcing tpm 2.0 on perfectly good hardware is the best marketing linux gaming ever got.

yeah revolut does this too. the irony is traditional banks could have offered this years ago but there was zero incentive for them to make it easy for customers to stop paying merchants.

i gave up on pi for homelab stuff and just bought refurb dell micro PCs off ebay. i5, 8gb, $60 each. more power draw but for anything beyond GPIO work the performance gap is embarrassing. the only reason to buy a pi at current prices is if you genuinely need the form factor or the GPIO pins.

this is really clean. the auto-TLS for local dev is the killer feature imo, so many hours wasted fighting mkcert and nginx configs. do you plan to support docker/container networking? being able to resolve service names across docker compose setups would make this a no-brainer for teams.

the real fix would be at the payment layer. let me cancel recurring charges from my bank/card directly without having to beg the merchant. some fintechs already do this but it should be standard.

classic pendulum swing. we went all-in on screens without checking if they actually helped, now we're overcorrecting the other way. the answer is obviously somewhere in the middle but that doesn't make for a good headline.

the part about scanning for 509 job search extensions is especially nasty. imagine getting flagged to your employer because linkedin detected you had a job board extension installed.

A very necessary tool, thank you.