EAtmULFO
EAtmULFO on Hacker News
It's okay John, don't be so hard on yourself! It was a great writeup.
Changed again?
"We do not use our users’ private personal data or user interactions when training our foundation models. We also respect the rights of web publishers to opt out of foundation model training."
I'm not sure I ascribe to the notion that you need to be technically competent in a specific field to be an effective manager or executive over the people doing the work.
This post reads like an invitation to one or more Trademark infringement cases.
It's become common practice for companies to post positions following layoffs that they never intend to fill.
Security updates through 2031. I'd rather not worry about added "features" introducing yet more bugs.
Server 2022 > Windows 11 for desktop OS. No bloatware, less garbage, almost identical driver and application support.
This is what happens when people don't put in the effort and time necessary to actually learn a craft. Result: Overconfidence and potentially very damaging outcomes.
Tout the hot-patching feature of Windows 2025...
Casually inform the viewer that they're in for a treat: Yet another subscription you need to purchase.
Thank you so much for reaching out. I've emailed you the case info.
The cat and mouse game continues... For every, "unbreakable" claim, there's someone capable and determined enough to prove that claim wrong.
I can confirm the support experience, although we're not currently using R2. We are an Enterprise customer and have been trying since May 8th to get a downed Worker fixed (ticket filed as, "urgent"). Still no progress/response from level 2 support.
I'd recommend getting your Privacy Policy in place as soon as possible, especially since submitting the form appears to require its acceptance.
Gosh, this is exactly where I went when thinking about this problem too.
Ugh. Seems they are spamming with reputable accounts now too. Thanks for pointing that out!
An an Enterprise customer, I've got a great CloudFlare story: May 8, 2024 one of our Workers stopped functioning completely when a single string was edited in the code. Rolling back to a previous version gave a "Script not found" error. Replacing all code with the previous version and saving the Worker continued to result in the same error. Being an Enterprise customer, we were not worried and simply opened up an "urgent" ticket.
A first-level agent escalates the ticket.
- 24 hours passes with no response or update. A response is requested.
- 72 hours pass with no response or update. A response is requested.
- 120 hours pass and an email is sent to our account manager with details on the ticket, begging for help. No response.
- 144 hours pass with no response or update. A response is requested, making note of the fact that we are an Enterprise customer.
- The next day, I sent another email to our account manager, hoping for some contact. Again, nothing.
- The same first-level agent responds that it is still "in process" with no details on what is being done.
- Another 2 days pass with no response. A response is requested.
- I request an emergency callback via the support portal.
- Another agent looks at the ticket and determines the original request was "misdirected."
- Another day passes with no resolution, but a quick update from the second agent stating it's "still in process."
- Four more days pass with no update or resolution.
- Desperate, I create a new Worker and connect it to the original KV stores, but some problems persist. Still no resolution.
Contemplate your options carefully if you plan to run production workloads with CloudFlare! I still have yet to hear back from anyone with support or resolution.
Agreed. That was a great read and cautionary tale about not following best practices!
How crazy is it that Microsoft is not even monitoring/alerting on commands like, "whoami" being issued on their managed systems? Wow.
My recommendation (although I am not a programmer by trade, and the quality of my code readily reveals this) would be to start by writing some small tools that fix problems you encounter in your day-to-day. Having a catalog of existing repos will give you much more credibility as an unknown and it will give you an opportunity to develop your documentation and code hygiene skills.
Once you have some nice repos under your belt, start looking at issues within repos you are interested in and give it a crack. Good luck and thanks for your interest in helping FOSS!