Pika

this is an absolutely toxic take of the issue. I took OP’s statement as less of a “I won’t read the manual” and more of a “I struggle to be able to read manuals”

Which is fully fair , there are many times I had read the manual, and then had to look up the issue further anyway because I either missed the poorly written section, or misunderstood what it was saying.

If you want a prime example of that, go look at ffmpeg and try to figure out how to select a specific language for subtitles on a video without looking it up online. its via -map as an advanced option, which is described as a parameter to extract specific streams (which also means they would need to map the video and the audio streams since including a -map removes every auto stream). but map doesn’t tell you subtitle tracks are index:s. it does tell you that you can look at stream specifiers for valid search options, which does include s as a type, and lets you know that you can use m for metadata tagging, but you would need to make the connection that the type is s, and the meta data search flag would be m:language:langcode, and you need to make the connection the entire string has to be concated so its index:s:m:language:langcode For someone who is learning ffmpeg and video transcoding, that is not a very good setup. The stream specifiers give a few examples of what the potentials are but, the location where it specifies the types are in a different area than the one where it specifies the metadata keys. At that point just asking online or searching is way easier.

Note: this is just an issue I have see people come across because ffmpeg is one of the more complicated programs (the man page is over 2300 lines)

is it in the manual? yes. is someone who doesn’t know how to use ffmpeg and is trying to learn it going to find it? that’s debatable.

If I was in that situation, my next step would be googling it, and if I couldn’t find it via searching, I would be reaching out to communities. At that point “RTFM” is useless to me.

there’s a standardized man format? News to me. I thought developers just threw everything in at random order.

it depends on the type of zip encryption, the default doesn’t encrypt metadata

edit: upon looking into it further, the other commenter is right, the zip format itself doesn’t actually support encrypting metadata at all, you would need to use a different format such as 7z to obtain it.

I forsee in the future Microsoft implementing a core electron service, one electron instance that is persistant and just runs, but sandboxes every app that calls it. so instead of an electron instance per app, its just an electron instance that has sandboxed pages that are only managable by the parent process.

it would still be pretty bloaty but, since core structure should only be present in the parent process, hopefully it would be less bloaty

In the US companies(where the company is located last I knew) are legally mandated to report specific things such as CSAM and other things if they come across it.

What the issue should be isn’t the fact that they are reporting it, the issue should be they have the capability to see it in the first place to be able to report it.

This isn’t me defending CSAM or anything like that but, in a decent storage system, google shouldn’t be able to even see what you have, let alone what the images actually are.

I’m not PC but, one benefit of using a central server for syncthing is an always on backup that doesn’t require another client device to be on, it also allows for easier creation of new shares.

For example, with syncthing you can set the “servers” client device to auto approve/accept any shares that are to trusted devices, then when you get a new device, instead of needing to add that device to every device you share on the syncthing network, you only need to add that device to the server and then you can have your other clients connect to the servers share instead of device to device. It’s easier. You can also configure the shares on the server to use encryption by default too, since you don’t really ever need to actually see the files on the server since it’s basically a install and forget style client.

As an example of what I mean:

I have 10 different devices that run syncthing, 9 clients and a “server” client. these clients are not always on at the same time, and as such when I change a file, the files can become desynced and cause issues with conflicts. By having a centralized server, as long as the server is on(it always is) and client itself is online, it’s going to always sync. I don’t need to worry about file conflicts between my clients as the server should always have the newest file.

Then for example say my phone died. Instead of needing to readd every seperate client that the phone needs to share with to the new device, I only need to add the phone as a trusted source on the “server” client via the webui -> click share to that device on every share the phone needs, and then remap the shares to the proper directories on the mobile device. this is vs having to add every device to the phone, and the phone to every device it needs access to ontop of reconfiguring all the shares. It’s simpler, but fair warning does cause a single point of failure if the server goes offline.

yea I have the machine backed up in case this happens. I have noticed that its a mess UI wise. But ipfire doesn’t seem to be stable. every few months it’ll randomly kill itself which will take everything on the network down until i manually restart the machine and then force tell it a new DNS server. It’s something I’ve never managed to resolve on the machine, and I don’t seem to have that issue with my test network with OPNsense.

I’m in the process of switching from ipfire to opnsense myself.

I hate how bloaty opnsense is at first glance but it has so much more control so once I copy my current config I’ll be leaving ipfire in the dust.

I have never thought of doing this. That’s now going on my server.

I love both of them. I just could never get into how resource nodes expired/ran out on factorio, Satisfactory really gave me a scare when they said that they were thinking about implementing limited time resource nodes. But I’m glad that they didn’t end up doing it.

I love how accurate to satisfactory that is. During that stage, it takes so long for reinforced frames to go through.