I can already, completely above-board, sell someone a block of DRS'd IBM shares for crypto if I want to. Let's all be clear this isn't about denominating stocks in Bitcoin.

Rather, this is effectively about recording stock transactions on a blockchain. Nothing more and nothing less than swapping a distributed transaction log for a traditional ledger.

The implication is clear, the SEC is at least considering the idea of creating shares as a token cryptocurrency. In this case, the tokens are backed by real shares. That's not a technical requirement, though, and a future company might someday skip the major exchanges entirely to list only as a token. To be clear, there's nothing sacred about the exchanges and their "house rules"; there's nothing inherently wrong with using a blockchain vs a ledger; and to reiterate, this has nothing to do with "buying stocks with Bitcoin".

On that last point, I consider OKXICE's decision to accept payment in some nondescript "stablecoins" as extremely unfortunate. Not because I'm a cryptophobe, but because it muddies the waters as to the viability of the core concept of tokenized equity itself - Though that's a bit of a tautology, given stocks are already "tokenized equity". Whether we denominate them in USD or BTC or cowrie shells is an entirely separate issue.

How dare the people who create your revenue streams demand reasonable working conditions?

Of course employers are welcome to set the terms under which they'll give us money. And similarly, we're free to set the terms under which we'll accept their money. That's how it works.

Personally, I love companies announcing draconian new RTO policies - There aren't many better indicators their stock price is going to spike short-term then tank a few quarters later. But that has nothing to do with working for those companies. On that front, it's just a hard "no", to the point I'm seriously considering becoming a professional "interview troll" once I retire!

I hate ads more than the average bear, but I have to admit, I have no idea where people are seeing these either. Are "ads" someone intentionally loads and watches really ads, or are they merely short-form content?

That said, if these are everywhere and the very fact I'm using FF with uBlock Origin is the exact reason I haven't seen these... That is the sort of viral advertising most companies dream of.

There's a fuckton of cigarettes manufactured every year. "If all your friends jumped off a bridge"... Good riddance!

LPT: You can also turn your phone to watch the content. I know, mind blown, right? Pass it along!

I'm not saying I would or wouldn't take this particular buyout, but as you point out, it's not a safe assumption the default severance would be the same absent this artificially sweetened offer. At a quick glance, New Jersey is the only US state that requires any severance at all, beyond making employees whole for time worked and paying out accrued PTO. Many do have additional requirements around mass layoffs, but nothing comes anywhere near two weeks per year of service. Even NJ, as the best-of-the-best (honestly surprised it's not CA or MA, but not in this case), only requires one week per year of employment.

That said, I see the GP's argument come up quite often in any online discussion of layoffs, and it took me years to finally figure out, this topic basically comes down to a simple class issue: If someone is a moderately well-paid salaried employee, a severance offer is almost always going to beat UI by miles (and as you also pointed out, that's not a mutually exclusive choice, UI just picks up after severance ends). If someone is a low-paid nonexempt worker, by contrast, severance is usually nonexistent and employers playing games around UI claim appeals are a lot more common.

There's also other benefits to consider, most importantly health insurance. Severance offers usually allow employees to keep their group health insurance during the severance period, while COBRA is eye-wateringly expensive even for someone formerly paid well.

The highest UI check in the country is in Washington state, and only comes out to $1208/week, for a maximum of 26 weeks (barring certain exceptional circumstances). A Principal Engineer (level 65) at Microsoft averages just shy of $246k/year and this buyout is offering up to 39 weeks total.

Weekly, that's $4.7k vs $1.2k. Total, that's $184k vs 31k.

I can guarantee nobody smart enough to be an engineer at Microsoft (as much as we might make fun of their culture and products) is dumb enough to fail that one-question math exam.

Here's the problem, and why everyone resents this crap (your fellow IT folks most of all)...

Yeah, great, you're an Exchange admin and can send email "from" any random VP you want. And you have access to their recent document history so can "spice it up" by referencing actual projects we might really be assigned to. When your phishing tests are literally indistinguishable from legitimate emails, you're not "testing" anything, you're daring people to ignore legitimate work at risk of their continued employment.

If "my boss" sends me an email, which the headers show really came from his account, and asks me to take a look at a spreadsheet we worked on three days ago - You're not being clever, you're an asshole.

1) Comcast could have started moving to fiber a decade before the upstarts and qualified for the same subisidies.
2) Comcast has received 2.6B in subsidies since 1987.
3) Remind us again, how long as Biden been out of office now?

Tovarishch, your sons are dying, cold, alone, in a Ukranian ditch; just waiting for one of the many overhead drones to notice them and blow off their manhood while they bleed out. And for what? So the ex-KGB gangster in Moscow can fantasize about reuniting a mythical Historical Russian Empire that never existed and never will?

Go home to the family farm and enjoy a peaceful life. There's no glory for you in Ukraine.

I'm curious where exactly he gets that $1500 figure from. When Spectrum installed my fiber, it was half an hour's labor for a lineman, 150m of such crappy fiber I wouldn't use it as a patch cable inside my house, a 4-port 1Gbit EPON, a mid-range pre-compromised bandwidth-stealing router I threw back in the box the second the tech left (if I don't have the real admin password, it's not going on my network!). That's it. Even at massively inflated replacement prices for captive customers, that's $600 total at most (and realistically more like half that).

Pssst, Jason - You need to realize the fictional numbers you use to justify rate increases to state PUCs are just that, fiction; and your competitors are eating your lunch precisely because you don't understand the difference. One year of "subsidizing" the installation on a two year contract is still net profitable! But then, they say to never correct your enemy when they're making a mistake, and I could not be happier to have escaped Comcast's footprint years ago. You go right ahead and pretend everyone else in the market is selling at a loss. Meanwhile, they're doing just fine, I don't need to deal with Comcast, and you won't be missed.

The preliminary results that previously sent their stock soaring "only" showed a 49% reduction. 42% over a much larger population still ain't bad!

I'm honestly stumped why the market reacted as badly as it did to this news - That's still a 100% viable product, and it targets people desperate for any reduction in recurrence! Exactly 0 people will turn down 42% who would have been thrilled with 49%.

Why does using a browser depend on an "account"? And why is an already-installed application (not tied to a single service provider) going to stop working ever? I might not have a very good time with it, but I could still run a 29 year old copy of NCSA Mosaic if I really wanted to.

Then again, both of those pretty much are the answers to my other top question, "what the hell are Arc and Dia, and why have I never heard of them": Proprietary garbage whose continued use depends on the Chief Sociopath having a good quarter. Nope, and good riddance!

This story really isn't about PHP. It's about AI easily finding multiple severity-9+ externally-exploitable server-side vulnerabilities without even breaking a sweat.

Over the next few months, this same story is going to repeat for Ruby, ASP, Python, Node (or JS in general), .Net, etc. And not all of them will be so easily fixed - Or for that matter, disclosed at all prior to a working exploit in the wild.

Running a public-facing webserver is about to become the losing side of an inevitable arms race.

LPT: Peacefully protesting is not illegal in the US. Guess who this will be primarily used against?

That said, this is the same LRAD system that the military unequivocally promised would never be used inside the US or against civilians. The same LRAD system that failed spectacularly when field-tested in Iraq against so-called "insurgents". It's trivially defeated by any amount of metal (e.g. tinfoil hats really do work against it), rain or even high humidity, plastic sheets more than a few mils thick, wet cloth - Basically anything except bone-dry thin woven fabric is substantially effective at blocking it.

So of course, they'll just crank up the power and actually cook innocent bystanders, but let's be honest, we all know they'll do that even if it worked spectacularly well, because cruelty is the point, and 11 is more cruel than 10.

The time has come when a full-body faraday cage is required gear for any serious protestor - So naturally, we should fully expect wearing anti-static clothing to a protest to become a felony as soon as police realize their intended victims aren't squirming in pain enough to sate their sadism.

Respectfully, that's not what banning "tasks that require significant effort or time, or would typically be performed by a cleaner" means. Unlisted ad-hoc requirements have been prohibited all along (though admittedly, not well enforced).

AirBNB / VRBO / whatever gets a cut of every dollar. They benefit from junk fees, and couldn't care less except to the extent it costs them customers or risks incurring regulatory oversight - And basic cleaning has been a pretty standard clause right from the beginning (albeit there's a legitimate concern over hosts double-dipping).