Citation needed. I know folks using the free plan that have gotten ddos’d and cloudflare kept them online. Can you point me to an article where cloudflare disconnected someone for getting attacked

I do something similar. I bootstrap all my new installs with brew cask https://github.com/fastily/autobots/tree/master/macOS/setup

I bootstrap it using Brewfile (plaintext file read by Homebrew), which supports Casks too.

Same here.

Probably easy enough to write a script that will iterate that list and run the proper xattr command to remove each from quarantine.

> They know that with enough reports in a short period of time they can get the content removed for a while

This can be accomplished with bogus dmca notices too. Since google gets such a high volume of notices the default action is just to shoot first and ask questions later. Alarmingly, there are 0 consequences (financial or legal) for sending bogus dmca notices

Action against DMCA abusers has happened in a few instances, but it's still largely an unsolved problem without sufficient deterrence from abuse.

https://techhq.com/news/dmca-takedown-notices-case-in-califo...

it is a weapon the music industry wanted, but now has this unintended consequence.

I think it's high time google stopped acting as judge jury and executioner in the court of copyright enforcement.

The law says they have to.

The law also says a counter claim can be immediately filed. Google don’t follow that part.

Google has nothing to do with filing a counter claim except accepting it if filed. The content owner is the only one who is allowed to file it.

Google do not immediately reinstate on counter claims.

They shouldn’t, because the original claimant has 10-14 days (depending on exact timing) to sue. If they don’t, they reinstate. Which considering many other folks it can take 6 months…

[https://copyrightalliance.org/education/copyright-law-explai...]

Not saying Google is good or anything, but this is well trod ground at this point.

There’s also hummingbird: https://github.com/hummingbird-project/hummingbird

Sadly this project is getting steadily slower. Adopting async made it slower than Django. But this is due to Swift limitations. Hopefully Swift replaces Codable and improves async performance.

Personally I gave up a long time ago and just installed Debian Linux. But it’s wild to me that the average non-technical/casual windows user has to put up with so much bs… it’s an atrocious ux

I’m using steam on Ubuntu 24.04 with 9y old hardware (which was mid-tier when new), playing mostly 2d platformer games and older resident evil titles. Never had any issues, this setup runs like a champ

There’s already a free self-hosted version of this that’s significantly more capable: https://github.com/C4illin/ConvertX. Not sure what your path to profitability is here but you may want to rethink your approach

Not everything is about profit :)

you're still avoiding the question. Why does Microsoft decide RTO "layoffs" are the right tool for 2025, but not 2022-2024? Many companies used both tools at the same time. Why did Microsoft wait until 2025?

Because it's politically expedient. They know the political climate is currently hostile to them requesting H1Bs while doing layoffs. RTO lets them get another round of layoffs without calling them layoffs and avoid the bad PR.

Microsoft compensates less than other top tech companies and remote work aligns with their lifestyle-first approach to compensation. Being on the early end of RTO would have worked against the perception that Microsoft is "the tech company with good work life balance," but now that most other companies have done it first they can get away with it as just them following the industry trend.

the curse of bgp strikes again

Also can be confirmed by Cloudflare's own route leak detection tool - https://radar.cloudflare.com/routing/anomalies/hijack-107469

First hit on google: https://jellyfin.org/docs/general/server/media/shows/

Thanks, I can google. For some reason Jellyfin totally ignores folder structures for me.

Actually after reading it more carefully I probably see why it didn't work for me, but the notes in the page are bizarre:

* Avoid special characters such as * in M*A*S*H, use MASH instead.

Since when a common ASCII character is a special one? What about more common unicode characters I use?

* Do not abbreviate the Season folder with S01 or SE01 or alike.

I.e. if I put anything not in the folder named "Season XX" it won't work? Ugh... really?

* Season folders shouldn't contain the series name, otherwise Jellyfin can in certain cases (Stargate SG-1 due to the dash and one, for instance) misdetect your episodes and put them all under the same season.

Well, how about to fix it?

* Episode numbering for specials may vary from metadata provider to metadata provider.

Very helpful, so the "Series XX" required above won't always work.

And even if everything above fails why not to sort by name? It should not be hard for any engineer, right?