Add SepiaSearch URL as default search index

I updated my weird wording but.. you and they said something about the default [index] URL

If OP asked when global search was implemented the answer is 5 years ago. If they asked when SepiaSearch became the default index then sure, ChatGPT was wrong, but I'd bet they asked the first question

https://github.com/Chocobozzz/PeerTube/releases/tag/v2.3.0

ChatGPT is correct? The irony of people confidently asserting that ChatGPT is wrong, while being wrong, seems to be lost on the crowd here. Kinda makes you understand why ChatGPT is often so confident even when wrong.

In May 2020, Framasoft published a roadmap of the software for the later half of the year and created a fundraising campaign requiring €60,000 for aiding the development.[18] Five months later (in October 2020), PeerTube announced that they reached their fundraising goal of €60,000 after a €10,000 donation from Debian.[19][20] Throughout the later half of 2020, PeerTube has added features such as global search, improved playlists, and more moderation tools

End 2020, the meta-search engine Sepia Search was launched by Framasoft, allowing a global search on all PeerTube instances at once. As of 2021, Sepia Search covered close to 800 individual instances

https://en.m.wikipedia.org/wiki/PeerTube

https://github.com/Chocobozzz/PeerTube/releases/tag/v2.3.0

I don't want to tell you one way or the other because it's kinda dubious anyway, but if all services run as the same user the need for root is kinda moot when it comes to crossing between services or expanding the scope of an attack. Of course it is better than all things running as root, but if I popped a machine as some "low privilege" user that still had access to all running services I'm not sure I'd care so much about escalating to root.

Woah, no. Sure escaping via a kernel bug or some issue in the container runtime is unexpected, but I "escape" containers all the time in my job because of configuration issues, poorly considered bind mounts, or the "contained" service itself ends up being designed to manage some things outside of the container.

Might be valid to not consider it with the services you run, but that reasoning is very wrong.

It did give the right answer...

Gonna be even worse now too with the National Park Service cuts: there are so many foreign tourists at the parks. As there should be too! Our National Parks are amazing!

You can unlock the bootloader on a Pixel in about a minute.

I can understand some people finding the whole process a bit daunting, but it's not actually that difficult with Graphene.

LXC is containerization. Both it and Docker are using the same kernel APIs.

Agreed

Not really, but I'd probably try to organize those into sub structures where it made sense. A data structure holding the UI state and FFT data all flat is kinda messy imo since it becomes unclear what is actually required where.