ziviz

Sega alleges infringements of the following five patents: No. 5930111, No. 6402953, No. 6891987, No. 7297361 and No. 7411307, all of which are registered in Japan.

I tried checking out that first patent there, 5930111 and who boy... is this shit hard to read

An information processing device includes: a control means for causing the player to acquire a content in response to a game execution instruction from the player; an extraction means for extracting content groups of the same type from contents possessed by the player, according to an instruction from the player; a selection means for automatically selecting fusion source contents and resource contents from each of the extracted content groups; and a fusion means for collectively fusing, for each of the fusion source contents, one of the resource contents of the same type as the each of the fusion source contents. The selection means selects, as the resource contents, contents having a rarity at or below a specific level, from each of the extracted content groups.

A fundamental flaw in this, is it still involves user data, even if "anonymized". You can advertise without any user data. We do it all the time. Does a television channel know your gender? Does a radio station know if you bought a car recently? Does the newspaper know your hobbies?

At least it appears to be something that gets triggered. In theory, if a node is not under attack or heavy usage, this isn't a consideration. Doesn't seem to be a perfect solution as it still slows the traffic of legitimate users in the event of an attack. I don't know the full details, but in the worse case it makes it easier to semi-DoS, maybe not by fully making a node unresponsive, but by making the service so painfully slow that users may give up on it.

I just tried it on Nobara. Just... application launcher (The start menu icon)->sleep. Waited, and then woke the machine back up and when the machine came back up, the game was still running. No idea if all games will play nice with that, but Satisfactory did.

Surely I misread the title. The wounded were all stabbed, surely. Nope... Cops open fired hit the suspect, 2 randos (one of which was hit in the head), and a friggin cop. All started by suspect not paying the fare. Cops made the whole situation infinitely worse than had they not showed up.

Kind of a click bait title imo, in the video he concludes it's not really ready for general use. Id argue that's not going mainstream.

30k doesn't even sound like a slap on the wrist or even a deterrent, rounding error at best.

If you ensured both the subdomain and the domain name were provided when using certbot, then it could be a case where the server is still using a previous cert. I had issues where changing the cert in NameCheap did not immediately take affect. (In the NameCheap CPanel console, cert would be fine, but actually visiting the site would still present the old cert for a while.) There were at least a couple times where it only presented the new cert after I fully removed the old one from Cpanel. Other than that, running out of ideas.

Sounds like the cert is missing a required SAN name. I used namecheap and Let's Encrypt together before. I had to ensure that *.ziviz.us and ziviz.us were both provided to certbot. I used manual DNS challenges, and it looked like this:

certbot certonly --manual --preferred-challenges dns
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Please enter the domain name(s) you would like on your certificate (comma and/or 
space separated) (Enter 'c' to cancel): ziviz.us *.ziviz.us

Not an expert, but I think it's Angular Leaf Spot. It seems to match at least, damage is not passing veins, looks like the underside of the leaves have white stuff on them. It does not look like there is a cure if so though, at least, not one I have found searching the internet.

Adding even more grammar, you could use "Had no", for lack of possession, like

It had no tooling for the fs?

Definitely this. The data is not likely gone, but before doing anything that could make things worse, try and get a full copy of the SD card somewhere. From there you may safely try repairing the partition or data carving tools.