plus these are benches too it looks like

This part is the most surprising. For something meant to go in urban areas, where’s the hostile architecture? No railings between seats? No spikes?

I prefer removing the -french language pack on every install. The command comes with a typo though, so you need to fix that for it by adding /* at the end

“The ‘elites’ are driving stock prices down to make Trump look bad. He’s being blamed for Democrat fraud” or something along those lines.

It certainly is more cultured than them, at least.

Greenland? That’s so 21st century.

Make a network state on Mars, guys. Take one of Elon’s Starship rockets up there too, while you’re at it.

After conservatives get to be on top, it’s conservative men on top. And then, white conservative men. Next, rich white conservative men.

It’s going to be one hell of a lemon party by the end.

JavaScript was a mistake, but this is one of the few things they did correctly. Implicitly importing everything from a package into the current scope makes it difficult to follow where variables or functions come from, and it’s prone to cause problems when two packages export the same identifier.

If you’re an absolute masochist, there’s always a workaround. Against all best practices, you can use the deprecated with statement. Or, you can Object.assign() the packages into the global object like a monster. Or if you’re using node, you can use the node:vm module to create a new V8 context with its own global object of your choosing.

If the passwords were properly salted, it wouldn’t. But if they’re not salted, helloooooo rainbow tables. Or the world’s greatest crossword puzzle, like that one Adobe accidentally made. Maybe even both!

They’re not generic adapters if they support the Switch. The Switch was intentionally designed to not work with generic USB C to HDMI adapters, and they did it by adding additional negotiation steps before the Switch would enter DisplayPort alt mode.

https://www.reddit.com/r/UsbCHardware/comments/171c3mj/comment/k3timvi/

It really should use a vertical line from 0 to 5 as a way to represent the welfare cliff, too.

We did it America! The red wave is here and the Dems are no more!

…

Wait… what?

…

That’s not a map of the United States?

…

What do you mean that’s the stock market?

…

Well, I don’t care. I don’t own any sto—

…

Of course I have a 401(k).

…

WHAT?!?!?!!1!11

And then lost the reflog by rm -rfing the project and cloning it again.

I actually jumped ship a while back. I agree that Plex is a business and they do deserve to get paid for development and infrastructure costs, but it’s the blatant enshitification that I have a big issue with.

They chose to lock a previously-free feature behind a paywall for everybody and asked for even more money to get it back. The less shitty alternative would have been to ask only the users who needed to use the relays to purchase a Plex Pass. Or, if they wanted to make it seem like a positive thing, they could have made the new subscription into an “enhanced quality” remote streaming experience that enabled higher bitrates over relays.

They gave their users the middle finger by picking the most transparently greedy option that they could get away with justifying.

Fair enough, although that actually has worse optics IMO. It goes from “this costs us money, so pay us” to “we need money, so we’re creating an artificial reason for you to pay us”

The self-hosted servers use UPnP and NAT-PMP to automatically forward the port used for media streaming.

Very, apparently.

They use UPnP and NAT-PMP1 to have clients directly stream the media from users’ own self-hosted servers. It costs them almost nothing in bandwidth to do that.

Software costs money how would they continue to developed it if not getting paid?

Apparently a hot take as evidenced the downvotes on my other comments here, but by adding things people want instead of taking away things people already have and charging more for it.

They don’t even have the excuse that they need to pay for the bandwidth costs of relaying video from servers to clients. Video is streamed directly from the user’s self-hosted server, using UPnP or NAT-PMP to make the server accessible from outside the local network.

And this isn’t a new feature they’re adding. Remote streaming was already implemented and generally available to users.

I don’t discount there being a cost in maintaining code over time, but it’s not as though they have to spend any significant employee time on improving it. They already support UPnP and NAT-PMP to have the clients connect directly to the self-hosted servers.

It would be nice if they added NAT hole punching on top of that, but it’s evidently good enough to work as-is in its current form. If they’re not even running relays to support more tricky networks (which the linked support article has no mention of), keeping this feature free costs them literally nothing extra.

No, it’s still wrong.

We have ways to do NAT traversal and hole punching on consumer routers. Failing that, UPnP and port forwarding exist. Or, god forbid, IPv6.

In the rare case that literally none of those are an option, they would have to use TURN to relay between an intermediary. That is a reasonable case to ask the user to pay for their bandwidth usage, but they don’t have to be greedy fuckers by making everyone pay for it.

This is enshittification and corporate greed. Nothing more, nothing less.

Regex is great, but PCRE deserves a special place in hell. You don’t know unreadable until you’ve encountered regex that uses recursive matching, backrefererences, and subroutine calls.