I like the fourth or the last one since it encourages all other error responses to follow a similar standard. That will allow the client to have a reusable error model and error checking.
I’ve had to use APIs where every response was 200 ok with json, 400 bad request with pain text that said unauthorized, or a 500 error that returned an HTML error page. The worst.
Thanks for the giveaway. I’d like to enter for Hogwarts legacy.
I’ve been playing around with running AI image gen and LLM locally because the tech is cool. Pretty entertaining what you can do with it, but I haven’t posted any of what I’ve generated. Seems to be a good skill to learn as well. Was good motivation to upgrade my RAM from 16G to 32G. Tomorrow, I’m upgrading to 64G.
Instructions unclear. Baby is now a werewolf and howls loudly when Kodi is buffering.
That just allows Google full access to all logs from any application you have installed.
That service is not free either per month and those costs will be passed to the consumer in either a subscription or worse software.
From article.
Downfall, a fan expansion for the popular Slay the Spire indie strategy game, was breached on Christmas Day to push Epsilon information stealer malware using the Steam update system. … "The breach window was roughly 1:30 PM-2:30 PM Eastern (1830-1930 UTC+0) on 12/25. If you did launch Downfall on 12/25 during the breach window and got a Unity library installer popup, please continue to read. You may be also at risk…
I personally wouldn’t use raidz1 because it seems too risky to me. I’d have higher redundancy.
Some links
https://www.truenas.com/community/threads/raidz1-vs-raid-5-ures.42598/
https://www.truenas.com/community/threads/5x-4tb-raidz1-array-rebuilding-with-nre-ure-issue.13719/
https://magj.github.io/raid-failure/
The last link is talking about actual raid and not zfs. But it has a 50/50 chance with a URE rate of 10^14 to lose the array. Raidz1 maybe won’t have that catastrophic of a failure, but you’d still be rolling the dice on some corruption.
Other people gave a good explanation of raid and some alternatives like zfs in truenas.
You want to avoid RAID5 with drives above 4TB. Every hard drive has can have an unrecoverable read error (URE) during the read. It’s a very low percentage change that your hard drive publishes. During a raid 5 rebuild after replacing a drive, the other drives are stressed for a long time during the rebuild. With high capacity drives you have a pretty large chance of encountering a URE and losing the entire array. The high stress on the drives can also cause drive failure if another drive was on its way out.
I run truenas core at home in volumes that looks like raid 10. Two mirror volumes striped together for performance.
I never played around with raidz1 (like raid 5) but you still have the chance of an URE during the resilver. I can’t comment if it’s possible or what happens during an error. I did see people recommending raidz2 to allow for two disc failures from losing data during a resilver.
“While we have not seen direct evidence that the threat actor is using this list to launch phishing attacks against support system users,” the company said to customers, “phishing attacks are a constant threat.” Okta, which manages user authentication services for thousands of corporate clients, didn’t immediately provide comment.
Okta’s shares plunged last month after the San Francisco-based company disclosed that hackers had used a stolen credential to access its support system. At the time, a company spokesman estimated that about 184 clients, representing roughly 1% of the Okta’s customers, were affected. It wasn’t the first time Okta had been breached. The company disclosed last year that a hacking group had broken into its system after the gang posted screenshots that appeared to show access to Okta accounts.
The company said in its letter to customers that a recent audit found more data was stolen than it initially thought, prompting it to revise its findings. The firm also discovered that some Okta employee information was included in stolen reports, according to the customer notice reviewed by Bloomberg.
The customer report contained fields for customer user names, company names and mobile phone numbers, Okta said, while noting that the majority of the fields were blank and didn’t include credentials or sensitive personal data. For more than 99% of customers listed in the report, Okta said, the only contact information stolen were full names and email addresses. Read More: Okta Falls on News That Hackers Viewed Some Customer Files Many of the affected users of the customer support system are Okta administrators, according to the company’s notice. Okta is scheduled to report earnings on Wednesday. The company said in its notice to customers that it would publicly disclose the new details on the same day.
Here is the rest of that article
I’d look at getting better than a c tier low end PSU.
I’m interested to see what hosted options are out there as well.
If you’re willing to consider alternatives, take a look at Greenshot. It’s a free and open source local program that takes a screenshot which allows you to edit it directly and copy the image to clipboard without saving.
It includes the ability to add text, blur out parts, crop, draw arrows. Just press print screen to capture an image.
As well as “The universe and everything else”
Bruh, get a 2019+ Miata MX5. It solves 95% of what you are complaining about and it’s fun to drive.
Coming soon to a future headline near you:
“Big Microsoft Azure outage as termite infestation introduces new bugs”