PinkSheep
- the employee pulled off the impossible
- may be already burnt out or on the brink of emotional collapse
- the "jump out of window" would have been as much of a joke as it was a coping response
- the righteous language policewoman does not feel empathy to personally ask him, how he is doing
- instead, she goes to HR to report him
- this unexpected hostility breaks the camel's back and what might have been interpreted as a joke actually wasn't. Still emotionally drained and now backstabbed, the person commits.
In short: policing voice was more important than taking a potential signal seriously. How is it not a despicable behavior in this situation?
PS: I hereby permit the commenters to reprimand me for the stereotype-based guess.
Once upon a time someone wanted to automate a printer. Why? It kept jamming paper. That's how the free software movement was born.
As far as "smart devices" go, we haven't really escaped that hell. This coffee machine is an example of it. Thankfully, open source firmware and DIY have an incredible amount of worldwide momentum, but we are still far away from devices and software serving their user first. DIY is a niche by definition, everybody around you aka normies still have to suffer from technology. Even when don't recognize it: https://danluu.com/bug-blind/
Keep the "shit" to yourself, because I didn't say nor imply that.
> buy it 5 years before LLMs became relevant
GPT-3 is mid 2020[1], but I doubt the inter-departmental communication would've been strong enough to seriously consider a Github acquisition since 2017?/2018. These decisions take time.
> but there's nothing stopping anyone other than Microsoft from downloading all of GitHub.
Licensing. Not that they care about such details today.
My interpretation of events is as follows: Microsoft pivots to cloud, while strengthening their focus on developers and the ecosystem (like they have once successfully done with Win32 and later tooling & frameworks). VSCode fits this idea. The immediate goal of Github ownership was developer relations and to bring all this mass to orbit the Azure ecosystem. The machine learning trend happened to chronologically come right after. Github Copilot was the first experiment. Today it ought to be one of the major reasons to keep and expand the user base.
https://forums.theregister.com/forum/all/2019/05/24/github_i...
[1] https://en.wikipedia.org/w/index.php?title=OpenAI&oldid=1014...
Don't let curiosity kill the cat, what's so bad about it? :) Is it Zigbee itself or the firmware quality? IoT without the S?
PS: You have seen Alec's unbelievably detailed encounter with the cheap red refrigerator, right?
1. I wonder how much optimization ngx_http_rewrite_module has? Does it precompile the patterns? LLM said yes, this SO answer [1] says that a JIT config option must be on. I consider "Just in Time" to be a half measure when the config itself is static.
2. From looking at NGINX docs, it looks to me there are some pitfalls to writing these rules. Like you must manually make sure to short-circuit the rewrites to exit early?
3. The caveat of regex is that catastrophically backtracking regexes do look simple. I don't see this issue being talked about enough. See links, if you, the reader, haven't heard of it yet.
[1] https://stackoverflow.com/questions/59284921/how-much-impact...
[3.1] https://joshua.hu/nginx-directives-regex-redos-denial-of-ser...
[3.2] https://en.wikipedia.org/wiki/ReDoS
[3.3] https://infrafolks.com/blog/regex-backtracking-devops/
[3.4] https://www.regular-expressions.info/catastrophic.html
Here's another guess: a DDoS to steal your attention and mask other intrusion attempts.
> Defenses need to have broader rate limits across more than just IPs (ASNs, hostnames, etc.).
The description/approach seems static and limited? Why not maintain a leaky bucket that counts each request (tickets/points) with higher cost for expensive requests (404, redirects). As the IP's reputation deteriorates (IPv4/32), it begins to spill over to a broader subnet like IPv4/31 then /30 and so on. Fight adaptivity with adaptivity. // maybe I describe something totally obvious, I'm not involved in the web ddos protection side of things.
> Attackers actively search for non-cacheable paths (e.g. dynamic redirects, search endpoints, and 404s).
To continue with my previous point. As long as individual server's resources permit (memory, socket limit) stall requests before processing them. Low reputation IPs get stalled for longer and the requests that exceed the queue get dropped. The idea is graceful degradation:
A good rep IP will not be stalled by sleep(). A poor rep IP will be stalled, but eventually receive its answer instead of some 429/403 (i.e. a user who opened many tabs at once). A bad rep IP will be slowed down by the wait times + rate-limits (queue exceeded) before getting completely banned for good. The point is to have more granularity before throwing errors at random users at the server-level.
It seems all too similar to the degradation of peer-to-peer networks where nodes are replaced by few supernodes. You mentioned a couple reasons yourself: consolidation and legal pressure. Add to this the technical qualification aspect and time investment (Mullvad's position), and the financial cost of sustaining such a non-profit project. Suddenly there are very few people or even organizations worldwide, who can bear the burden.
Thank you for existing and your tireless work.
Lesson to learn: Let's Encrypt does not protect against MitM by a state-level actor, unless you take precautions. *let's assume network admins won't MitM your server for personal vengeance reasons
Average of (current maximalist copyright; ending copyright) is what you called middle ground.
Average of a sensible position like (current maximalist copyright; ending copyright divided by 2) still does not yield a sensible world where culture and art - or even human interactions - can thrive.
The comment above shows this type of people don't understand it. Yet they are the ones getting hired due to formal qualification. Those who do are at the intersection of design, engineering and computer science. The latter give you enough experience to understand the culture to recreate familiar _look and feel_.
While you raise good arguments against wide deployment, politics will not backtrack. Despite the loopholes, despite the vulnerabilities, despite real life precedents, the juggernaut will keep moving. Much like blackouts or internet outages (Canada) that make payments, digital communication impossible, people will not rely any less on cashless payments etc. That's the blackpill.
The Navy drones article is terrifying. The easier solution is to not have wars at all (lol) then the problem is reduced to only corporate espionage.
"similar price to closed source" -> Good argument. But what if the _lower price_ is only lower thanks to a vendor lock-in? Thus, over a long period of time, you don't get a better deal? Furthermore, here an expensive reverse-engineering project had to discover the backdoors? What was its cost? Why can't the government have this work done (new cameras) on a contract basis?
First step: "we want this and that, you may choose the hardware freely, but the project source code will be perpetually licensed to the government to use and extend upon." Second step: "we have this source code from the last contract, we want another 1000 of these traffic cameras with improved specs/features."
The belief, that the market will do anything right, perpetuates this system of outsourcing everything to the market. Though I don't think it can work any other way, because nobody among the government workers wants to bear responsibility and liability. It's much easier to give party B the money and then argue with them based on the paper trails. This is what they've been trained to do after all.
SecureBoot is a funny one. It should be signed with the deployer's keys (Slovak), not the manufacturer's. Trusted boot probably wasn't a consideration here, really.
Ironically, a custom firmware can now be used thanks to the lack of a digital lock... if you still trust the hardware.
PS: Props to NBU for doing their job.
Pay attention to the European efficiency rating for LEDs. Anything above B is practically "Dubai LED" class. The common Osram isn't doing good in this category, their LEDs I have seen in retail are rated like E-F.
To reiterate: the article fell short on the point of LED efficiency. LEDs are semiconductors, do you know when the CPU is at peak efficiency? Before it hits the exponential voltage/frequency curve. Low voltage -> cooler LEDs -> more efficient light conversion -> easier to cool -> tens of thousands hours of practical lifespan.
What does it cost? Like less than a dollar in BOM. What does it cost us? Billions in replaced LEDs worldwide and megatonnes of electric waste, because it is not made to last for "objective reasons": lower price tag in storeshelves aka capitalism and oblivious consumers.
As much as I generally agree with your comment, it's not "the screens". It's the entire industry hyperoptimizing every bit out of their social networks/media for attention; gambling mechanics in live-service games. In other words, not a "handful" of apps, but too many of the apps and websites you come across.
You'll surely remember the numerous attempts at edu software/games of the 90s. Instead, the current attention monopolies won and have been perfecting their addiction mechanics for the past 20 years.
If there were an organic push by parents, they would be happy to buy and promote products today, without waiting for legislation to catch up. Where are these local parental control products?
Speaking of social media and Youtubes of the world, why can't I, as account owner/parent, totally blacklist some "recommendations"?
Age verification is not a fit tool for content filtering. Users want the latter, but get switcheroo'd into the former.
> cwebster-99 / Courtney Webster / Product Manager at @microsoft working on VS Code and GitHub Copilot!
>> No description provided.