Full stack web developer currently working mostly with #PHP / #Laravel, Vanilla #Javascript and #SCSS. Love learning more about (almost) anything, but particularly #MySQL and #InfoSec. Currently learning Arabic. Husband, father of two boys, Christian.
With all the arguing about threads the one thing that actually annoys me is the current status quo, where federation is entirely one-sided: any reply just disappears into a black hole, nor can fediverse servers see replies to posts from threads.
It’s just that one post in total isolation.
I assume the answer is ‘no’ but wanted to ask anyway: does anyone know if threads has (or is planning to have) an API to at least fetch responses so it could be integrated with FediFetcher?
I think he expresses a lot of things that I have held for a long time. And I believe more and more (although I might be wrong of course 😉) that people not grasping these things is a big big reason for the polarisation and partisanship of our age.
So, read the article! And pay particular attention to the four takeaways at the bottom.
I’m not a big fan of summary/details generally because it’s just too inconsistent, but dialogs are great. And I didn’t actually know about input type="color" yet.
I've been seriously fed up with Google's search recently: results full of ads and/or SEO spam, to the point that it's hard to find info.
The results in kagi search are overall good (though the map is really lacking), but it's just very expensive. I'd definitely need their $10 per month plan, and I'm not sure I could justify this, given there is free (though arguably worse) competition. 🤔
I guess I could cycle through the trial by creating a new account every week (the joys of having my own domain name) but that seems a little ridiculous, too 😆
This whole eIDAS situation is absolutely horrific!
In short: The EU wants to force browsers to accept government appointed certificate authorities. Worse, it wants to prohibit browsers from scrutinising the security or propriety of these authorities in any way.
This will endanger the security of every web user worldwide, if it happens.
Even as a person with good eyesight, I find these incredibly annoying! I always cover the pin pad when entering my pin, to prevent shoulder surfing, and that just doesn’t work here.
On the contrary the only way to enter your pin on these is to do it slowly and in clear view for everyone. Such a ridiculous thing!
Lovely email to wake up to: someone’s cracked my wife’s age old Hotmail password …
Any accounts she actually (still) uses are secured with proper random passwords (no, she hasn’t always appreciated my insistence on this - now she suddenly does 😁), but that one hasn’t been in use for many years.
Only problem is: it’s still associated with her Facebook account. Oopsie 😬
Lesson to learn: make sure you don’t use an unused email address with your still-used (social) accounts…
So, today I deployed the 2nd microservice that I had split out from our monolith.
I’m a big believer in avoiding complications, so how did I know I needed microservices?
Both of these were aspects of our app that needed independent scaling from the rest of the app: while the main app scales quite predictably with user growth, these two services see huge fluctuations in usage, regularly increasing (and occasionally decreasing) 10-fold or more in a matter of hours, and without warning.
It also helped that these are logically quite self-contained, without strong dependencies on the state of the application.
Ultimately these two microservices now run on CloudFlare Workers, allowing near infinite scale, and geographic distribution, which is fantastic!
