That remains to be seen… And that’s why we have mods. I need a raise sigh

The actual numbers:

For every $1 given to each of the 1000 test subjects, income dropped by $0.12 cents on average. That means that the overall drop in pay was $12 per month, or less than 2 hours per month, at minimum wage.

Now, let’s extrapolate more info from this:

Prior to receiving $1000 per month, the average income was $30,000 per annum , which is ~$14.42 an hour. This means that the average number of hours worked dropped less than an hour a month.

The reporting you are sharing is amazingly biased, with sensationalistic headlines determined to skew views against UBI.

Source for my numbers.

I did just that. I clearly here a je as in college at the end.

I don’t like Fox or anything they stand for, but this level of hair splitting is just bad.

This is a rare exception to rule 6. Yes it’s a video, but it does qualify as news.

I’d be looking to see who made the most shorting the stock.

A corrupt file wouldn’t be nulled. I’ve never ran across a file with all zeroes that wasn’t intentional.

There aren’t any backbone outages right now that are being discussed. Many servers that run MANY services are on Windows, using Crowdstrike. Flights, banks, entertainment (some Netflix, for example).

The overall result: it looks like a backbone outage, but isn’t.

Microsoft, Azure, and Crowdstrike have all stated the root cause at this point. Furthermore, this tells me most of the Falcon sensor installs are done bad, as we also use Crowdstrke and have ours set to “latest version - 1” to ensure this exact thing doesn’t happen.

• https://status.cloud.google.com/incidents/DK3LfKowzJPpZq4Q9YqP
• https://www.crowdstrike.com/blog/statement-on-windows-sensor-update/
• https://azure.status.microsoft/en-us/status/

Article has been updated with the root cause - Crowdstrike. The reason is simple: Azure has tons of Windows systems that are protected with CrowdStrike Falcon. Crowdstrke released a bad version that is causing boot loops on Windows computers, including Windows VM servers.

I’ll respond to you directly about why you decided to comment a month after my comment. You were given a ban in !news@lemmy.world, for saying “Talk shit get shot.” about someone shooting former U.S. President Trump.

Number 1, that’s a rule violation of the community. Number 2, that’s advocating assassination. Number 3, we are in damage control mode right now, so we are handing out 1-day bans like candy to keep on top of moderation of a thread about one of the biggest political events in many of the reader’s lifetimes.

If you have a problem with that, I really don’t care.

People who would sit at home and not vote may be more likely to vote. I hope every able person votes, but this may turn the tide if the other side doesn’t turn out in full force.

every family has crazies. With that said, we don’t know who it was, their reasoning, or their political leaning.

I added some of yours to the mega thread - the ones not directly depicting death.

I added that to the mega thread. Thanks!

Thanks. Added your link and context to the mega thread

God, but I wish I could say this won’t help him, but I’d be an idiot if I did.

We all must do our part to ensure that the private prisons are filled to the levels in the contracts. /s

“I’m always the victim, if you ignore my past actions!”

I’m out. Later Felicia.

Me pointing to your comments isn’t an attack. You just said the same thing as “don’t point out my past actions!”

Sorry if your post history embarrassed you. Me pointing to it is in no was an attack.

Rule enforcement. As stated elsewhere, your modlogs are freely available to be perused.

1. Not “butt hurt” - I volunteered for a job, and I do it. You broke rules. Rule 1 - “be civil” - you personally attacked another member of the community.

2. There’s always the mod logs.

Just keeping the place civil by enforcing the rules. As I can see, you’ve been banned (temp/perma) 8 times.