I think there's a balance. if you really don't care anymore, you'll become a bad person that nobody wants around
only if that feature wouldn't have a massive memory leak... can't update even to 10.9 because it crashes the whole system the first time it tries to rescan a library.
there's an issue, and they have a hard time figuring out the problem.
turns out OBS does not have a software encoder for it, only encoding with a hardware encoder is supported. it is mentioned in the 2nd table of the video formats heading herev https://obsproject.com/kb/audio-video-formats-guide
there is no screen protection on either of the 2 phones
No it doesn't? There is only one Lemmy implementation
Beehaw is not very happy with the Lemmy project, and was looking for alternative implementations a few months ago. I remember to have read that they have found something written in Java, and maybe another one, that was basically a separate implementation of Lemmy.
There is really no such thing as a "platform type" - it's all ActvityPub under the hood.
Try to view a Peertube stream on Lemmy, then. Or subscribe to a Mastodon user. There are platform types, and there will be at least until the platform has to implement its own way to interpret and render the content of an other platform that hosts content of a different kind. Even when a platform type implements full AP compatibility, there will often be things a specific platform won't be able to display.
that does not mean javascript is essential, and mox's point is still very valid.
using WASM instead of JS is not better either. you simply don't need any clientside executable code on a read-only view of a page
you should be able to turn it up always, to some extent. it's in the settings on web
for example by being aware that the format is harmful to psychological health
possibly, but couldn't that be said about instagram and tiktok too?
when I tried it, it lagged like no other app does. it genuinely had 10-20 fps
forgot the most important part. I'm storing twitch streams from a variety channel with lots of Minecraft.
they roughly do 7 streams a week, 2-4 hours each, and the size of the collection that has all streams from 2020 October is almost 11 TB.
it sure is, but where did you see it?
and OBS doesn't support h265
are you sure about that? I'm pretty sure it should. maybe you'll find it as _x_265, as that's the name of the encoder it uses
twitch - the gameplay streaming platform - limits 1080p streams to 8000 kbps at most, at 60 FPS. I think it exclusively uses H264 encoding. For most games this is plenty.
There are some where it can be felt that it's not enough, but in those cases it's always the bitrate.
these games include
- escape from tarkov because of it's environment, especially if the player has taken I think painkillers, and in turn has sharper/different vision. compression is really struggling there
- no mans sky when traveling in hyperspace, this is the most extreme case I have seen so far
- any games that have darker scenes (not necessarily in a "bright night" style) will have it visible
unless you are playing a quick action first person shooter, 165 fps is totally unnecessary, 60 is plenty.
1440p, I'm not sure. if thats your screen resolution, maybe it's better to not lose quality to downscaling, more so because it can't be done by just averaging every 2 pixels, it would bea weird ratio I think
for encoding.. what hardware you have?
x265 is more efficient than x264, if you can afford the performance, but if you have a graphics card with hardware accelerated AV1 encoding, that may be even better. do some test recordings though.
tbh I don't think any of the 2 sides here could know that their opinion is the truth. we can't say that it's intentional, but can't either that it's just a honest mistake, so far everyone saying that just sounds to apply wishful thinking. let's see what happens in a few years, and then we may be able to judge future incidents better.
except that the case of winamp and bitwarden couldn't be more different.
they pulled the fixes, but couldn't build because google fucked up the NDK. my other comment has more details
it was mentioned in a This Week In F-droid blog post around September. basically google fucked up an important development library, and any firefox forks (possibly some other apps too) could not be built anymore normally. of course google was unwilling to fix the issue, so linsui (and F-droid member) fixed the build process somehow, possibly temporarily.
you may ask how is this not a problem for the official release of the firefox app, and my answer is that they probably build this component for themselves, and fixed the problem in house (if they had it at all)
the content stays there once it's there
my bookmarked/liked videos lists don't agree. A lot of videos, and even a few complete channels have disappeared over time. This is not a new issue.
Premium gives what it promises
well it does not promise to respect you and your privacy
Fairphone 4 user here too. I also got it second hand, but immediately replaced the OS with CalyxOS. It seems fast to me. My last phone wasn't.
My only problems with it so far is the lack of a jack, that I need to remove the battery to remove the SD or SIM card, and the screen seems too easily scratched. It was scratched when I got it, but not this mutch. Its in my pocket with nothing else, but the screen is basically full of micro scratches while my previous phone of 8 years has (which was a very cheap phone even back then) almost no scratches at all.