According to Arch Wiki they get generated and stored in the partition when it is formatted. So kinda like labels but automated and with (virtually) no collision risk.
No, third-party browsing engines are not a thing that's been implemented yet, and might never be by Firefox. This is about a screen that prompts EU users to pick a browser rather than defaulting to Safari and leaving it up to them to install another.
That's funny that you mention hardware, cause in Germany you pay a set fee for each device (13.19€ for a computer, 6.25€ for a phone) on purchase since it could be used to create copies of media.
I'm just getting my money's worth, officer.
Fun fact: w3schools has nothing to do with w3c and there used to be a whole website dedicated to giving them shit. They've apparently gotten much better these days though.
Arch is focused on being cutting-edge and lightweight which happens to be perfect for gaming performance in most cases but that's all.
Jesus what the hell is going on in those comments over there.
Files are still stored permanently and links inside the client stay permanent as well, only links accessed externally are affected. I don't like Discord either but anyone relying on it as their personal free CDN had it coming for them.
It is dev dependent, but I don't agree with "devs can implement it just as easily" at all. One only requires using a built-in API to create notification channels (which you have to call anyway), the other requires designing and programming your own page for it.
Even the Pi has lost its headphone jack...
I nuked my personal instance because of this :(
Dealing with pictrs is just frustrating currently since there's no tools for its database format and no frontend for the API. I half-expected this outcome but I hope it gets better in the future.
Beautiful reasons but there's an easier one... we don't want our flags to be straight (I only ironed my trans flag).