I REALLY liked the Inbox app they made for gmail. Sadly, like all the best things google makes, it went the way of the dinosaurs.
Glad fizzbuzz doesn’t fit into the gibberish category
Oh I definitely had to look it up lol
Boost hasn’t failed me yet, but aside from checking to see if it’s down, I’m being careful and popping away without browsing. I don’t want the dev to get slammed with more API fees because of me.
Yeah, at my company we switched to allow/block listed last year. Whitelisted and blacklisted are verboten
Daedalic didn’t make Portia, was Pathea. I was surprised for a minute there. Loved that game and I knew Sandrock was in active EA for a while now. So, whew.
As another dev here, I have barely used a PC/laptop outside of work in years. I got a gaming PC like 2 years back and don’t use it much. But every time I get the hankering for some personal dev project and have to mess with the registry I cry inside. I really need to just ditch it for Linux entirely. I’m so much more comfortable on Linux. You might just convince me to bite the bullet and remove it entirely since 90% of my gaming is on steamdeck anyway.
It was! Posting this from my fold-4 as we speak. I’m loving the app so far. Great job on this!
Lol, yeah for us we didn’t own any of the code that used it but depended on server software made internally that did. At the time we managed our own hosts, so it was a long week of deployments.
That was not a fun week to be a developer.
Had GPT summarize what happened.
The “left pad” incident refers to a controversy that arose in 2016 when a developer named Azer Koçulu removed his JavaScript package called “left-pad” from the NPM (Node Package Manager) registry. This caused a ripple effect, breaking numerous projects that relied on this package and highlighting the potential risks of relying on external dependencies. The incident sparked a debate about the stability and trustworthiness of the open-source ecosystem and led to discussions about best practices for managing dependencies in software development.
1000% agree. This is how it should be done. And not hidden away somewhere deep. There are legit reasons for in depth tracking, but when used for advertising or something other than improving the user’s experience, count me out.
It’d be a “vulnerability” of anything public. There’s nothing stopping me from building a bot that pulls posts/threads from any instance and storing all the comments, their owners, the posts and their owners, yadda yadda.
I suspect the up/downvotes are “private” but on any instance, the owners will have access to that. I can’t imagine all the data is encrypted at rest by default. But, don’t take my word on that as I haven’t read any of the specs. But, I’m pretty sure we’re just looking at the protocol, not the implementation with regards to how a federated instance works.
So, same precautions as anywhere else really. Your data that’s public WILL be tracked by someone and Meta is a damn likely culprit who absolutely would do that. I’m a total privacy nerd myself, but you’d be amazed at the things I want to track at work related to what/how/why people use the tools I work on. Granted, it’s 100% exclusively used to improve user experience, weed out bugs, and see what is used most frequently to focus on that stuff. But if it can be tracked, somebody is tracking it.
Just a few weeks I’m sure