yeah I mostly commented that because the fact that the game itself is so much smaller than the audio is impressive and funny at the same time

650MB CD media. The game itself was 40-50MB and the rest 500-600MB was the audio in wav (CD player compatible) type

Less content, that is spread across multiple instances that can have duplicate communities.

on top of that, there redundant communities that are unnecessary even in the same instances. For example there is the android@ and the askandroid@. The first one has a decent amount of subscribers while the second one has a single digit number. I wanted to ask a question, I posted in the first one since it would make sense to reach more people. The post got deleted and I was told to go to the other one. In the first one they were posting only news articles.

This is ridiculous. Splitting communities in such way was the result of the huge traffic that such communities had in the past in other platforms. This makes sense only when the traffic is so huge that it is practically chaotic to navigate and moderate between news/articles and support questions. When both communities combined have 50 subscribers, such split only harms the platform and the users.

Everyone wanted to migrate by bringing an identical environment to what they had used to. However this should be adaptable to the current situation instead of directly copying it.

sure if you prefer to support the google monopoly

firefox for android + ublock origin and/or adguard-dns

ok, it will be funny if this is the case because I didn’t want to hit submit because I thought it would had been done immediately. I’ll check it next time. Thanks

from now on I’m having it open and shown on the screen show if it happens again I’ll see it. thanks

mostly on youtube, usually at 720p30fps. I think if I go to 60fps it crashes even faster. Also I’ve tried watching on freetube and on firefox + mpv, but it can crash in all combinations

thanks! nice idea, i’ll try it

i will try it but I’m quite confident that it will be unresponsive/not reachable since if the kernel was listening it would respond to the alt + PrntScr + REISUB by unmounting the drives and I would see it when I examine the logs afterwards