In the end, they both end up learning effectively the same lesson

I tend to think people shit on Musk more than they should, but holy shit does it bug me when a CEO talks about engineering problems with such bravado.

they’ve got some decent ones on there. I just started playing Shredder’s Revenge and am having a lot of fun. Into The Breach is fantastic. They also have GTA 3, Vice City, and San Andreas, not that those are exactly new games.

It doesn’t matter what browser you’re using. Everything Google was tracking here is the stuff all browsers send in incognito mode. This lawsuit was totally frivolous

I played Mass Effect as female Shepard because i heard the voice acting was better. Generally for RPGs I play as “myself” though.

Ohhh good call. I saw ads on Facebook saying it was on sale and didn’t realize it was on Epic not Steam. Yeah, screw Epic.

Should I get RoboCop: Rogue City or Star Trek: Resurgence now while they’re on sale or wait to see if they go lower?

It’ll probably be 3-6 months before I get around to playing either

I’m a lot more worried about a DC/Star Trek crossover than I was about a Marvel/Star Wars crossover. The DC people are stupid enough to try it.

Only 8? Those are rookie numbers

I’m watching on my phone, and couldn’t unmute it. I tapped the mute icon and nothing changed, so I assumed that was telling me it had no audio

That’s… why we want the labels?

Car manufacturers should get out of the dashboard design business. Just have an API standard for devices to control the car, and a USB port for users to plug in whichever device works best for them. You want a bunch of physical buttons? Cool, go down to AutoZone and buy a button panel that matches your needs. You want a big screen with carplay and a bunch of widgets? Mount your old iPad there.

The regulatory side would be the hard part. Devices would have to meet some safety standards and the car would have to refuse to drive unless an approved dashboard was connected, but it could be done.

Software receives update. INTERNET PANICS

Looks like lots of people’s year end bonuses were contingent on them releasing something related to AI by the end of the year.

JavaScript is a language that runs on a user’s computer, when they visit a web page. It is often used for dynamic functionality, ie when you click “like” on a comment… JavaScript running in your web browser will make a request to the server letting it know that you liked the post, then the server will respond with a total number of people who liked it or something.

But, the server needs to know how to authenticate which user liked the comment (so you can’t like it twice etc). There are various authentication mechanisms to do this, with their own trade-offs. Over all, there’s secret information that the browser and the server have to share with each other, and we don’t want that information being accessed by the wrong people.

There’s also a common problem with web apps called “cross site scripting”. Basically somebody might craft a cleverly formatted comment that exploits a bug in the web page and causes the attacker’s code to run. One trivial example might be if every time a person read a comment thread, the attackers code caused that person to “like” a request. A more serious exploit would be one that finds out that secret authentication information I mentioned and shares it with the attacker. They can then pose as the victim user and do anything they want as that person. This would be bad.

So, on to the different approaches and their tradeoffs.

• HttpOnly cookies. Basically when you log in, the server gives your browser a cookie vouching for who you are. Each subsequent request to the server will include this cookie automatically. The browser handles attaching it to the request, and the browser hides it from any JavaScript running on the page. One trade off is that it requires some authentication to happen between the user and the service (ie enter your username and password), to generate the cookie in the first place. This is likely what OP’s customers want to avoid.
• bearer tokens: basically, when JavaScript code makes a request to the server, it can optionally add some tokens in the request headers and use those to authenticate the user. I’m assuming OP’s scenario involves his company providing a service that is used by another company’s web site. They want to log in the user on their system, then forward some info along to OP’s system describing that user. They can’t just set an HttpOnly cookie for his domain, since it would be private to him; so instead they store a magic token in the browser’s local storage or somewhere and send that on every request. The down side is that JavaScript has to be able to read that token, so it enables that malicious user we talked about to steal it if they exploit some other bug.

Anyhow, one common solution here is to set very short expiration dates on those bearer tokens. That way if somebody steals it, they can’t use it for long.

Another strategy is to limit what each token can do. OP needs to make it so you can like a comment using one of those bearer tokens, but more dangerous actions like purchasing things, deleting content, etc, should be guarded by a more secure mechanism. Then the damage is mitigated if the bearer token leaks.

I just want a game where I get to name my character after myself and the voice-acted NPCs use AI to dub my name into their lines instead of awkwardly avoiding using names.

There’s no way DS9’s bathrooms are that clean.

This is the internet. Everything we dislike is the same. Landlords are cops, Nazis, Russians, Israelis, authoritarians, libertarians, racists, homophobes, and transphobes; all at the same time.

I think the problem is that unions are famous for fighting for equal pay across the board for the workers they represent regardless of individual competency or market demand. For this example they’ll give COBOL developers a raise to 120K and give web developers a pay cut to 120K.

Or best case scenario they give the COBOL developers a short-term raise to 150, then raises across the industry stagnate in coming years to offset the fact that employers feel like they’re overpaying for some people. But sure, a few years later the union can come in to look like a hero arguing for a fraction of the raise the web devs could have already gotten.

Nah, they’re going to “solve” it by paying web developers less, not paying cobol developers more