Great, I’m so glad to hear that! Tartube can be a little intimidating with it’s sprawling menus and sub-menus, but when it comes down to it most of the core functionality is pretty accessible once you know where to look and can ignore all the hyper-specific options for power users.
1. No idea, to be honest. In the environment I tested this in (Windows 10 Sandbox) Windows Defender didn’t complain, and I’ve never had an issue with my actual install either. In fact, I just checked my installation folders on my PC and didn’t even find that executable (maybe it’s only used during installation?) although I do have it on my system for a different program. I only found one Google hit from 5 years ago on the glslang Github itself, and the user seemed to think it was a false positive for what it’s worth.
2. They are supposed to be there by default (they store metadata) but you can set up Tartube to put them in separate folders if you want to just have a nice clean folder with only videos or just not write them in the first place if you don’t want them. I believe the metadata is copied into Tartube’s database, so deleting them shouldn’t change anything (they’re mostly useful for archival purposes or if you want to do some processing with external tools), but Tartube references the thumbnail image files for display in the GUI so removing them will remove the thumbnail from the GUI like so:
This is pretty straightforward to configure, thankfully:
- Right-click the desired menu in the left-hand menu and select Downloads -> Edit download options…; this will bring up the same dialog we were using before, but we are just editing our existing profile instead of creating a new one.
- Click the Files tab, then the Write/move sub-tab.
- Here you’ll see options to instruct Tartube to move each of the file types to a separate folder and/or not write them in the first place. Select whichever options suit your preferences and then click OK.
3. (hosted externally due to Lemmy sanitization bug causing less-than symbols to be HTML escaped)
edit: accidentally left out a line in the externally hosted markdown
There’s a variable that contains the number of cores (called
cpus) which is hardcoded to max out at 8, but it doesn’t mean that cores aren’t utilized beyond 8 cores–it just means that the scheduling scaling factor will not change in either the linear or logarithmic case once you go above that number:code snippet
/* * Increase the granularity value when there are more CPUs, * because with more CPUs the 'effective latency' as visible * to users decreases. But the relationship is not linear, * so pick a second-best guess by going with the log2 of the * number of CPUs. * * This idea comes from the SD scheduler of Con Kolivas: */ static unsigned int get_update_sysctl_factor(void) { unsigned int cpus = min_t(unsigned int, num_online_cpus(), 8); unsigned int factor; switch (sysctl_sched_tunable_scaling) { case SCHED_TUNABLESCALING_NONE: factor = 1; break; case SCHED_TUNABLESCALING_LINEAR: factor = cpus; break; case SCHED_TUNABLESCALING_LOG: default: factor = 1 + ilog2(cpus); break; } return factor; }The core claim is this:
On this point, I have no idea (hope someone more knowledgeable will weigh in). But I’d say the headline is misleading at best.