Because some people want to filter it out. So it gets a label.
Because some people want to filter it out. So it gets a label.
I think so. IIRC there are a few different implementations. But if you configure any of them Android will automatically use it to run non-native apps.
Do you have an ARM emulator installed? I don’t think the game ships an x86 build. Other than that it just worked.
I would try to avoid VP9. Hardware support is spotty and I suspect that new hardware is going to relatively quickly phase it out. AV1 is better in most circumstances except for a few devices that have hardware VP9 support but not AV1 (a few years of Android phones mostly). So unless you need a specific device you currently own to have hardware decoding support (only really matters if you are on battery for <=1080p content) just skip VP8.
I would avoid h265 if you prefer free (libre). The only real advantage it has over AV1 is that devices started shipping hardware decoding support a few years earlier. If you need that and care about file size/quality then yes, you may need to go h265. But otherwise I would lean towards AV1 (better quality) or h264 (basically 100% compatibility).
My short opinion:
h264 is the best option for compatibility. There have been free software encoders and decoders forever and IIRC all patents have expired. Basically every device you will encounter and every software system can play h264 videos and the encoders are fairly good.
AV1 is the best option for quality. It is completely free and is becoming widely supported. It will likely be supported for a long time as it is the first widely available high quality free codec. It is significantly better quality than h264 so will result in smaller files for the same quality or better quality for the same file size. Hardware decoding support has only really become common in devices that hit the market in the last few years. But most new devices will have hardware decoding.
Both of these are web-compatible as well which is nice.
Opus for lossy and FLAC for lossless are both some of the best codecs in their class, completely free and widely available. There are also both web-compatible.
Although the Android kernel is slightly customized isn’t it? I thought it exposed a few extra syscalls. How do these work on Waydroid?
On NixOS I did this:
services.displayManager.autoLogin = {
enable = true;
user = "kevincox";
};
# Avoid setting up a keyring every time I do a non-auto login.
# https://gitlab.gnome.org/GNOME/seahorse/-/issues/159
security.pam.services.login.enableGnomeKeyring = lib.mkForce false;
Can you configure KWallet with no password? Often you can do something like set an empty password and it will auto-decrypt with no prompt.
This may be undesirable as apps running in your user can access what is in KWallet but honestly this is probably the case anyways. If you are running unsandboxed untrusted applications you have already lost.
I like the option to preserve originals. I wonder if this is now always done or if it is configurable. Often times I am preserving the original footage and project files anyways so don’t need an original. However other times I am just throwing footage straight from the camera and the archive is nice.
It also opens interesting possibilities like re-encoding down the road to new or better codecs or even just better encoders. For example it would be interesting to dedicate one background thread to re-encoding in a much higher effort, and possibly re-running this every few years to take advantage of encoder upgrades.
Most archiver programs will set the modified time of a file to the modified time recorded in the archive (if present). Many archive formats support recording modification times because they were intended for backups and aim to perfectly record the original files including all data and metadata.
I also agree that this is not what I want when using GUI modification programs (in my case file-roller
) but the exact options available will depend on which program you use.
What do you think you’re doing by putting that link in every comment? Lemmy doesn’t have a terms of service that assigns a license to your text anyways. So if you just say nothing you own your comment and they can’t use it. If they cared about the licence they would already not be able to use it.
Or just use it in a web browser. I don’t really want to run their proprietary spyware outside of a sandbox anyways.
Honestly my biggest complaint is header wrapping. Technically you need to wrap lines at 998 bytes (not that any reasonable server actually cares). But in order to wrap a header you need to add spaces (because you can only break a line after whitespace). But where spaces are unimportant depends on each specific header. So you need to have custom wrapping rules for each header.
In practice no one does this. They just hope that headers naturally have spaces or break them in random locations (corrupting them) because the protocol was too stupid.
Binary protocols are just so much simpler. Give the length, then the data. Problem solved. Maybe we could even use a standard format for structured headers. But that would be harder to do while maintaining backwards compatibility.
I want us to stop using communication protocols that are tied to our connectivity providers. Let alone tied to a specific piece of hardware (SIM card).
“Telephone providers” should be just another ISP. And whatever I do over the network shouldn’t care if it is running on a mobile network or a landline fibre.
While we are at it let’s fuck off with this SIM shit. You don’t get to run code on my device. Give me an authentication key that I can use to connect to your network and then just transfer my packets. My device runs my code.
Facebook had an XMPP client API. It didn’t federate (and wasn’t really true XMPP resulting in many quirks).
SMTP is a terrible protocol. Text based for sending effectively binary data with complex header wrapping and “generate a random delimiter” framing. We really need a HTTP/2 of SMTP.
That being said I agree that it exists and works. The biggest blocker to more IM-style communication is largely the UI and user expectations. I have no problem having quick back-and-forths over email but most people don’t expect it.
greylisting will typically only be applied to people who you haven’t interacted before, so I don’t think it is a big deal. It would be similar to how many major chat apps hide away suspicious messages from new people in some “invites” section that is often hidden by default.
I want both. When I am typing code in my editor I want it to follow the styles of the project. Then when I run the linter/formatter it will fix the mistakes.
The last thing I want is to start a new if foo {
statement and the indent is half of the indent of the if above. That would be too distracting.
Yeah, just jump in.
To get started it is best to keep Windows around, then if you need to get something done urgently you can go back to what you know then figure out how to do it in Linux later. Dual-booting is probably the best option if you are gaming as GPU passthrough can be difficult to get great performance. That is the approach I took a long time ago and then at some point I realized that I hadn’t booted into Windows for months and just deleted the partition.