My hardest thing took about 7 years to build (with a child getting born and slowing things down a bit) but still. Good to hear that I’m not the only one :)
fDeploy is a self-hosted Windows deployment automation tool — a lightweight, on-prem alternative to Octopus Deploy. It consists of a Server (Windows service with a Web UI) that orchestrates releases, and Agents installed on target windows machines that execute deployment steps (IIS sites, file copies, scripts, etc.) across environments.
If you use both from the same IP without using a VPN… the profiles are most certainly grouped. There are commercial datasets on IP addresses with almost 100% accuracy with tags like “school”, “house”, “apartment block” etc. Furthermore, if you ever logged into both sites from within the same browser by accident, the link by fingerprinting was made right there and then. The final profile on you may not be 100% accurate, but certainly is in the 98% range.
And when you actually need a super hot fix for a 0-day, you will need to revert this and keep it that way for some time to then go back to minimum age.
While this works, we stillneed a permanent solution which requires a sort of vetting process, rather than blindly letting everything through.
I beg to differ. Let's say you're right. Code producers should turn to agriculture and let their managers and product owners prompt AI to produce code. How about code maintainers? Ever heard the mantra "You build it, you run it"? Lets say that AI can build it. Can it run it though? All alone, safely, securely and reliably? No. It can't. We can keep dreaming though, and when will AI code production services turn profitable? Is there a single one which turned profitable?
Because Microsoft, Google and Amazon, to name a few, sell the story of the cloud to decision makers who can sign a subscription contract. Developers go with the flow, not daring to question the setup. Meanwhile, they host their own servers on a r-pi and ship sideprojects. Devs are not at fault here. It’s the management.
I found a way to cheat. The fire which is meant to force you doom scroll actually disappears if you scroll down then back up. This means that you can just chill out in the “easy area” and get your powerups and kills. Scrolling down (doomscrolling) is not mandatory.
The keyboard pops up, but is not responsive right away. This very thing happened today on my work phone (which has a bunch of MS defender/enterprise policies and apps managed by the company, forced background app updates etc, which could explain this) but I recall it also being a regular thing with all Samsung flagships I've had over the years. It's the feeling of a very slight delay (it could be a matter of as low as 200 ms) for important components which are operating-system controlled, such as the on-screen keyboard. It feels laggy, as if an app or a background process impacts the responsiveness of low level OS features.
On iOS, this was never something I had to experience. Slow apps are killed, iOS is brutal in this regard, but it protects the core OS-level components such as the keyboard. Try it out, load a few apps and try switching between them, where one of them had the keyboard uplled up. This is something regular users will likely never feel, but if you've been around since amiga 500, you'll definitelly feel it.
With an iPhone, when you click on an input field, the on-screen keyboard pops up, and you can type right away.
On an android (latest samsung flagship), the keyboard shows up but is frozen for a second before you can type.
I feel this and I’m guessing iOS is a lot more closer to the hardware, while android runs on top of Java, so there is more to process. Maybe its just me.
Right on the money. We get paid to add more pretty buttons, rather than make sure exceptions risen by existing buttons are handled gracefuly at no cost to UX.