JGrffn

As someone who has a profile only for Whatsapp (used to also be Instagram), a profile for banking & finances, a profile for some stuff that needs play services, and a profile for most other stuff (main profile)…don’t use profiles unless you’re only creating one more at the most, and you’re absolutely certain there’s no need to share information between the profiles.

Graphene has had a long-standing bug from upstream AOSP, if I recall correctly, where it’ll always ask for your pin when changing profiles, and only sometimes will it allow you to use your fingerprint or alternative methods to get into your profiles. I almost never get the fingerprint option for my main profile, and have to tap back from the pin input on other profiles to get the option to use fingerprint, and not always. They do sometimes push something that loosely resembles a fix, but it’ll go back to not working after another update.

Regarding communicating between profiles, that’s hard to pull off. The curveball of having to send screenshots from banking apps, say, confirming transactions, it’s made a lot worse with profiles. I’m currently relying on my nextcloud instance to upload screenshots from finances, then downloading those screenshots from nextcloud into my WhatsApp profile, just to send a proof of transfer to someone. I’m definitely not keeping my phone like this for much longer.

All else considered, however, I’m not going back to a ROM that doesn’t respect me as the owner of my device. I’m happy to have switched to graphene and I am here to stay.

Yeah, as someone else mentioned, this step is just for creating a folder. You probably need to get more intimate with the commands you’re running to understand the process better, but I would honestly take a step back and use something more streamlined for these things.

Someone mentioned Proxmox for these things. I would also mention TrueNAS Scale. Both of those make it so that the process of spinning up containers and VMs becomes a lot more streamlined and easy to follow. They also forego a UI on the equipment you’re using, opting for a web UI you’d access from another device instead. Make no mistake, this is a good thing. 99% of things you’ll be wanting to do anywhere will be through web UIs, so that’s where you’ll want to be. The 1% of the time where you’ll be seeing your laptop server’s screen (or an SSH terminal) will be the most painful 1% of your life, and it will be when you misconfigured something and the web UI becomes inaccessible (on that note, also make sure to at least configure SSH access on something so you understand how that works). I’ve had to do this plenty of times with my pfsense box, and as a relative noob to these things as well, having to use nano and vim for editing pfsense configs to revive my server…it’s fucking horrible (sorry vim enjoyers). The good news is, you learn the hard way, but you learn. Try not to have this happen to you, or you’ll be back here soon. Once you’ve had a lot more experience with your tinkering, this will seem less daunting and you’ll be more comfortable debugging directly on your laptop server screen.

TrueNAS Scale, as the name implies, is better suited for when you want to include NAS Capatbilities on your setup. Since you mention things meant for Plex/Jellyfin setups, I’d say you could start there.

However you do mention a laptop, so I’m imagining a very basic setup where you probably have limited space or a couple of USB drives or something. You could, instead, opt for Proxmox. You lose the specific capabilities of creating complex RAID setups that TrueNAS would give you, but it sounds like you wouldn’t be needing those anyways, as they better fit a setup where you have a bunch of disks connected through SATA or PCIe interfaces. Proxmox is a lot more specialized for containers and VMs so it’s probably a good tool to get acquainted with, and might be better suited for a setup where you have just the laptop and maybe a couple of drives to toy around with.

Whichever you choose, make sure to watch YouTube videos about it, read the docs, truly understand what’s going on with that tool first, as well as how to set it up correctly. This will introduce networking concepts to you in the process, as you’ll need to understand how to access the computer through the network with a browser, as well as with SSH. Make sure you don’t ignore networking knowledge. It might seem daunting, or skippable (why bother with local domain names when you can just use the IP and port number?), but a lot of networking concepts are actually rather simple to follow, take a moment on the first few tries but become very easy to reproduce afterwards, and it will make your life easier (yeah turns out, now there’s 20 services and you forgot what ports are for what service…if only you had dedicated time to telling the network that port 69420 was for radarr.localdomain and port 42069 was for sonarr.localdomain).

I’d check out Lawrence Systems on YouTube. They make videos covering networking configs with pfsense and the like, as well as TrueNAS configs, and maybe they’ve delved on Proxmox? Craft Computing, another YouTube channel, for sure teaches about Proxmox. There’s tons of video guides for *arr services, I haven’t looked for platform-specific configs, but I’m sure you can find both videos for Proxmox and TrueNAS Scale configs. Once you get your first one, most other *arr services are very similarly configured (though not all are, some are very quirky).

Another thing you’ll need to understand is how containers work, as well as how to map things from outside the containers into them. Containers are, well, contained, and mappings are how you expose parts of the container to the outside. You’ll probably be guided to map things such as your data and the service’s config files from outside the container to better organize and persist those things. Make sure you understand this concept, where things are on your setup, where they’re getting mapped to in the container, and what this means when it comes to modifying the container (hint: it means you can delete or upgrade the container and things still work exactly as you configured them once your container is back up).

Maybe a controversial advice, but I’d steer clear of the console unless it can’t be helped, since you honestly can do a lot from the UI for the vast majority of things you’ll need to do. If you DO need to use the console, however, I’d bother ChatGPT and documentation for whatever youre doing, to make sure you understand what every command you try does. Things like “sudo mkdir xyz” should be crystal clear to you. In the case of this failed command, for instance, you should be aware that mkdir doesn’t create entire paths, but rather only specific folders. If the preceding folder doesn’t exist, the command fails, so if /home doesn’t exist, nothing else will work. If /home/user doesn’t exist, you’re not going to be creating /jackett_config, and so on. Sudo is also a very powerful keyword, which means whatever follows it is an order from the big boss and must be obeyed. As such, absolutely make sure you understand any command that starts with “sudo”, as those are the ones that can easily set fire to your entire config. If you don’t understand what it’s doing, don’t run it.

While we are on the subject of folder structures, theres no shame in looking up videos and docs explaining the Unix file structure. If youre coming from windows, this is a veeeeery easily confusing bit, and understanding where you are is very helpful.

Hopefully some of my ramblings make sense to you. Hit me up, or hit the community up, if you need more specific guidance. Things can seem daunting at first, especially if you’re new to Unix, but I promise you it becomes easier as you build good foundational knowledge.

Huh, last I checked, the professional standard was Mac, at least for recording instruments. From what I vaguely recall, Windows has a latency issue due to how they handle audio stream inputs. I went through these woes myself once while using my guitar & Amp through my computer to practice with headphones on and having the music playing on top. The latency just doesn’t allow you to concentrate on what you’re playing, it completely distracts you. You can get it lower by doing something, I don’t remember what, but that solution ends up introducing random new bugs such as certain audio streams suddenly not playing at all for a while before fixing themselves, and it still doesn’t quite get latency low enough to not notice it.

Note 9, stock Samsung. Looking to jumping into the Pixel 8/Pro with Graphene in the coming months, but gotta save up a bit first.

Still absolutely not true

Lol that’s absolutely not true

Hard to follow that as a rule. Consider any YouTube video, the video id isn’t exactly human readable.

I’m relatively new to usenet myself and have both torrent and usenet tied to my *arr automations. From what I can tell, for newer stuff they’re less distinguishable than for older stuff. Things basically get uploaded in both places for the most part, so you can also get duds on usenet, the same duds you’d get on torrents.

They do! All of these backbone comply with takedown requests. Some comply with DMCA requests only, some comply with NTD requests only, and some comply with both. It’s actually another thing you could consider when selecting your providers, you check their takedown policies. By mixing and matching, you increase your chances of finding every part of your file.

So, the thing saving usenet in particular, is that the pieces of the file get scattered through the usenet, and you require indexers to find the whole thing. This makes it difficult for takedown requests to actually take down the whole file. Sometimes the best they can do is remove a few parts, and you can repair your file with what’s left. Sometimes they do win, but it happens infrequently enough that you should be able to complete most of your media library without issue.

You gotta pay. I posted an explanation on usenet as a reply to this post. You can find more info, such as specific providers and indexers, in the /r/usenet wiki.

OK, let me mention some important caveats, just so you can keep them in mind:

You can think of usenet like the internet. You have data on servers all around the world, you have sites such as Google which index these sites and content, and you have your ISP which gives you access to the internet.

Likewise, on usenet you have the data scrambled on servers all around the world, on different backbones of the usenet. These backbones are accessed through service providers for the backbones (sometimes they’re resellers, sometimes it’s the backbone selling access). These service providers operate just like an ISP, selling you monthly or yearly access to the usenet backbone of your choosing.

Then there’s the Googles of usenet, Indexers. There’s a ton, they vary a bit from one another, but essentially they find all there is to find on usenet, presenting the files to you as a whole. You want a specific… Ahem… Linux iso? An indexer will know where all the pieces are and it will tell you with an NZB file, kind of like how torrent files tell you where to look. Indexers can be a monthly subscription, but some of them offer lifetime subscriptions as well, and they don’t break the bank.

The last bit you’ll need is your download client, to do what you do for torrents. These are free tools, sabnzbd and nzbget. Either one works.

So, I did mention there’s multiple backbones of usenet. Indexers don’t lock themselves to specific backbones, and no indexer covers everything there is on usenet, which means that to get the most out of usenet, you’d ideally have multiple indexers and multiple providers (making sure you don’t get providers from the same backbone as they’d essentially have the same data). Multiple indexers give higher chances of finding something on a search, while multiple backbones increase your chances of finding all the pieces needed to complete a file. This is not absolutely necessary, but dare I say you’ll notice the difference as soon as you bump things up to 2 of each.

So, essentially, usenet is by far the best method for completing your media library (leaving torrents as a desperate backup route), but it can become expensive.

Are you for real here? Reducing the dependability on user interactions also reduces the chance for user error, and helps keep people alive in some cases. Even if that weren’t the case, it’s not your place to call out someone’s medical treatments and compare them to your (at best) anecdotal experiences. It’s not outrageous to want a CGM.

I actually hate the new whatsapp desktop app on windows. They somehow managed to turn it into this nearly unusable mess, where absolutely everything is super slow (5950x CPU be damned), most times textboxes just refuse to take focus and you just don’t type at all until you click on something other than whatsapp and then click back in, and the app sometimes just completely disappears from my Taskbar. I’ve noticed similar trends of bugginess on the android app, every now and then the textbox will just shoot up to the top of the screen, or just behave erratically. Feels like I’m watching the spiritual rebirth of post-MS acquisition Skype.

GUI alternatives are constantly improving and becoming more visually pleasing throughout distros, and besides, there’s real scenarios where normal people HAVE to use Powershell or CMD to get stuff done on Windows. This is becoming less and less of a hurdle.

I think a more appropriate approach is just to mention lemmy to your circles of friends and try to get any redditors you personally know to give lemmy a try, at least get the app installed so they can browse both reddit and lemmy. Lemmy won’t be able to handle millions upon millions of new people, especially ones with no guidance, but communities aren’t built overnight and we should do our best to get those who could use lemmy to use lemmy, one at a time. We shouldn’t be trying to overthrow reddit, just give a viable alternative to those willing to try one. It’s the more organic approach.

Right, but we all live under capitalism and have bills to pay. It’s true that youtubers quite generally rely on sponsored ads to make probably most of their profit, but YouTube ad revenue still is a decent chunk of it. And that’s not even getting into hosting an instance.

The only real way peertube works is if it implements some sort of subscription system (I think instance-wide subscriptions following the nebula pattern would be ideal). It’s easier for text-based platforms to stay afloat with random small donations from less than 1% of users since the storage requirements aren’t as egregious, but we do need to remember that even YouTube operated at a loss last I heard. It was only kept afloat by Google. Hell, even image hosting sites get the short end of the stick sometimes (still mourning gfycat), I can’t imagine a free video hosting platform staying afloat at all, let alone pull serious content creators to it.

I’m not too confident in peertube ever going big, if I’m honest. I’m not confident in monolithic gif/image sites either, but that’s a lot easier to self-host than a giant library of random videos that could far outgrow your system if you aren’t careful. You wouldn’t expect a federated free Netflix to work, would you? And yet that’s a fraction of the amount of content a successful PeerTube instance could end up with if it goes anywhere near as viral as a lemmy instance. Hell, even if channels ended up hosting an instance each and not letting anyone else upload to their instance, there’s some channels/companies that put out multiple videos a day every single day. No way to keep that afloat long term without a strong revenue system. Like it or not, money is always going to be an issue, especially for peertube.