Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)C
Posts
3
Comments
105
Joined
6 mo. ago

  • Since you've clearly not read or comprehended any of the subpoenas that I linked, nor the encryption analysis, nor read any of Signal's blogposts, I see no point with responding any further. You are spreading FUD, and I question your motives.

  • No, and in fact they have fought to unseal and publish the articles they have. The point is that if you read the subpoenas, they request a lot of data from Signal and Signal can only ever return the phone number, account creation date, and last connected timestamp. So either Signal is consistently lying to various governments or they actually don't have any of that data. Signal's client is also open-source and has been audited, and they have published many blogposts about how the technology works.

    I'd strongly recommend digging deeper into this and trusting the auditors and experts instead of dismissing it based on lazy and cynical guesses. If you don't trust anyone you're welcome to read the source code of the client yourself. Soatok recently posted an 8-part series going through Signal's encryption that you can read as a primer: https://soatok.blog/2025/02/18/reviewing-the-cryptography-used-by-signal/.

  • Doing your own encodes is also really cool. I'm not too sure what the AV1 compatibility of your friends' players would be, but yes AV1 encodes are a very efficient way to microsize. If you happen to be on PTP, there's a giant AV1 research thread with people testing stuff out. It looks like they prefer SVT-AV1-PSYEX as of the latest posts, though I don't know enough to understand which encoding settings are the most impactful.

  • E-Fund, yes, for sure put that in an HYSA so that you can access it when needed. However, if a person is keeping non-E-fund money out of the market for fear of volatility, they're actually technically undertaking a larger risk than being in the market because their money will never outpace inflation, whereas investing in a low-cost broad index fund has an extremely high chance to outpace inflation over a 5-10+ year horizon. Not to mention that when an investor undertakes market risk they're also getting a positive risk-adjusted return in exchange for doing so.

    Also, keep in mind that HYSAs don't always offer such high rates every year, whereas inflation will always be present. And despite the "official" inflation numbers being around 3%, my actual expenses say otherwise, so I'd still be eyeing 3-4% as treading water at best.

    If at all possible, get the snowball rolling on compound interest and let gravity do the rest; your future self will thank you to bits. Head over to one of the finance communities and they should set you straight. Personal finance is effectively a solved math problem; there's really only one good answer that people will give you as long as they're not trying to reach into your pockets for a cut, and the skill required to invest is zero. All you need is any amount of extra cash every month to pack onto the snowball. Time is by far the most valuable part of investing, so the earlier you start, the less of your cash you need to invest to get the same outcome: a reasonable retirement age with a body that isn't burnt-out.

  • I'd definitely start considering inflation. If your money is stagnant and not earning interest, it is shedding value. Like it or not, we're all inherently playing the game; it's in everyone's best interest to learn the rules.

  • There's nothing wrong with Signal's centralization model in a worrying sense. It acts only as a clueless message relay, and it has near-zero information on any of its users, even as it delivers messages from person to person. The only information Signal knows is if a phone number is registered and the last time it connected to the server. There is great care taken to make sure everything else is completely end-to-end encrypted and unknowable, even by subpoena.

    The only real issue with Signal's centralization is that if Signal the company goes down, then all clients can no longer work until someone stands up a new server to act as a relay again. Signal isn't the endgame of privacy, but it's the best we have right now for a lot of usecases, and it's the only one I've had any luck converting normies to as it's very polished and has a lot of features. IMO, by the time the central Signal server turns into an actual problem we'll hopefully have excellent options available to migrate to.

    Also TMK, the only reason you still need a phone number for Signal is to combat spam. You can disable your phone number being shown to anyone else in the app and only use temporary invite codes to connect with people, so I don't count the phone number as a huge problem, though the requirement does still annoy me as it makes having multiple accounts more difficult and asserts a certain level of privilege.

  • If you're only at 10mbps upload you'll have to be very careful about selecting microsized 1080p (4-9mbps) or quality 720p (6-9mbps) encodes, and even then I really wouldn't bother. If you're not able to get any more upload speed from your plan then you'll either have to cancel the idea or host everything from a VPS.

    You can go with a VPS and maybe make people chip in for the storage space, but in that case I'd still lean towards either microsized 1080p encodes or 1080p WEB-DL (which are inherently efficient for the size) if you want to have a big content base without breaking the bank. E.g, these prices look pretty doable if you've got people that can chip in: https://hostingby.design/app-hosting/. I'm not very familiar with what VPS options are available or reputable so you'll have to shop around. Anything with a big harddrive should pretty much work, though I'd probably recommend at least a few gigs of RAM just for Jellyfin (my long-running local instance is taking 1.3GB at the moment; no idea what the usual range might be). Also, you likely won't be able to transcode video, so you'll have to be a little careful about what everyone's playback devices support.

    Edit: Also, if you're not familiar with microsized encodes, look for groups like BHDStudio, NAN0, hallowed, TAoE, QxR, HONE, PxHD, and such. I know at least BHDStudio, NAN0, and hallowed are well-regarded, but intentionally microsizing for streaming is a relatively new concept, and it's hard to sleuth out who's doing a good job and who's just crushing the hell out of the source and making a mess - especially because a lot of these groups don't even post source<->encode comparisons (I can guess why). You can find a lot of them on TL, ATH, and HUNO, if those acronyms mean anything to you. Otherwise, a lot of these groups post completely publicly as well, since most private trackers do not allow microsizing.

  • SuccessfulCrab only does WEB-DLs so "subjective quality" isn't as much of an issue as it would be with the encoding groups, but yeah I agree that scene is usually best avoided if you have access to reliable P2P sources. Quality > speed for me any day.

  • SuccessfulCrab is a legitimate scene group and ELiTE appears to be some sort of P2P x265-1080p transcode bot/group (their releases on IPT/TL look fine and go back quite a ways). I'd stop using whatever you're indexing from that's either serving you malware or failing to regulate the malware in its users' uploads. The real problem is that someone is mimicking these groups and putting out fake releases, so playing whackamole with the fake tags that that person is using is only treating the symptoms, and they can easily change the tag again.

  • Screen-sharing is part of chat apps nowadays. You're fully within your rights to stay on IRC and pretend that featureful chat is not the norm these days, but that doesn't mean society is going to move to IRC with you. Like it or not, encrypted chat apps have to become even more usable for the average person for adoption to go up. This reminds me of how all the old Linux-heads insisted that gaming was for children and that Linux didn't need gaming. Suddenly now that Linux has gaming, adoption is going way up - what a coincidence.

    Edit: Also for the record, I have a tech-savvy friend who refuses to move to Signal until there are custom emoji reactions, of all things. You can definitely direct your ire towards these people, but the reality is some people have a certain comfort target, and convincing them to settle for less is often harder than improving the app itself.

  • Yeah h264 is the base codec (also known as AVC), x264 is the dominant encoder that encodes in that codec. So the base BDs are just plain h264, and remuxes will take that h264 and put it into an mkv container. Colloquially, people tag WEB-DL and BDs/remuxes as "h264" as they're raw/untampered-with, and anything that's been encoded by a person as "x264". Same thing for h265/HEVC and x265, and same for h266/VVC and x266.

  • Yeah I'm reading a little bit on it, and it seems like apt-get can't install new packages during an upgrade. On initial reading I was thinking there were specific packages it couldn't download or something, but this makes sense too. Regardless, this is news to me; I always assumed that apt and apt-get were the same process, just with apt-get having stable text output for awk'ing and apt being human-readable. I've been using nala for a long time anyway, but this is very useful knowledge.

  • Whoa, do you have something to read up on that? I'd be extremely surprised, since apt-get is supposed to be the script-safe variant, i.e. I'd imagine it's the more stable of the two.

  • As an idea, I use an SSD as a "Default Download Directory" within qBittorrent itself, and then qB automatically moves it to a HDD when the download is fully finished. I do this because I want the write to be sequential going into my ZFS pool, since ZFS has no defragmentation capabilities.

    Hardlinks are only important if you want to continue seeding the media in its original form and also have a cleaned-up/renamed copy in your Jellyfin library. If you're going to continue to seed from the HDD, it doesn't matter that the initial download is done on the SSD. The *arr stack will make the hardlink only after the download is finished.

  • I've just discovered kids toothpaste recently, which doesn't have this problem. All my life I've hated mint so much, and no one ever told me you can have candy as a toothpaste flavor. Just make sure you check the active ingredients for a regular amount of sodium/stannous fluoride; all the rest of the marketing gimmicks of adult toothpaste are mostly meaningless. Also, you should try to not swish water around your mouth after brushing anyway, since you want the fluoride/paste to sit on your teeth for a while.

  • Forks found in kitchen.

  • Yep, fully agree. At least BluRays still exist for now. Building a beefy NAS and collecting full BluRay disks allows us to brute force the picture quality through sheer bitrate at least. There are a number of other problems to think about as well before we even get to the encoder stage, such as many (most?) 4k movies/TV shows being mastered in 2k (aka 1080p) and then upscaled to 4k. Not to mention a lot of 2k BluRays are upscaled from 720p! It just goes on and on. As a whole, we're barely using the capabilities of true 4k in our current day. Most of this UHD/4k "quality" craze is being driven by HDR, which also has its own share of design/cultural problems. The more you dig into all this stuff the worse it gets. 4k is billed as "the last resolution we'll ever need", which IMO is probably true, but they don't tell you that the 4k discs they're selling you aren't really 4k.

  • The nice thing is that Linux is always improving and Windows is always in retrograde. The more users Linux has, the faster it will improve. If the current state of Linux is acceptable enough for you as a user, then it should be possible to get your foot in the door and ride the wave upwards. If not, wait for the wave to reach your comfort level. People always say

    <CURRENT_YEAR>

    is the year of the Linux desktop but IMO the real year of the Linux desktop was like 4 or 5 years ago now, and hopefully that captured momentum will keep going until critical mass is achieved (optimistically, I think we're basically already there).