Did you know most coyotes are illiterate?
It looks like it might be; I just know someone that has a site using it and they use a different mascot, so I thought it would have been trivial. I kind of wonder why it wouldn’t be possible to just docker bind mount a couple images into the right path, but I’m guessing maybe they obfuscate/archive the file they’re reading from or something?
You can customize the images if you want: https://anubis.techaro.lol/docs/admin/botstopper#customizing-images
As far as I’m aware this is true (same with a lot of desktop linux distros), but I’m more interested in freeing myself from Android at the moment. I’m sure we can get there eventually w/r/t security, but it takes time, and we’ll never get there if we don’t start moving.
To me it reads like Graphene is saying /e/ is “actively attacking” them as a puppet of the government of France. How do you reconcile them both being perfectly good when either one is engaging in this behavior, or one is lying about it? It’s okay to support both projects overall and not agree with every action they take, but that doesn’t mean you have to turn a blind eye to accountability when they are making bad choices (to put it lightly). In any other project, criticism would lead to positive changes and correction of bad behavior. Because Graphene doesn’t work like that, I think it’s important to understand their history so that everyone is more informed when they make serious accusations about other innocent projects like this.
It mainly makes me pine for linux phones. I think Graphene is the best we have at the moment in the mobile space, but that’s far more of a testament to our lack of options than how valuable Graphene is. I have no doubts that we’ll eventually kick Graphene to the curb when it stops being useful, so I’m not overly concerned with its future. Worst-case, I think many of us would be just fine on any other AOSP rom for a few extra years until linux phones can come save us all.
This is actually a really relevant note, because all of us are the “wolf-watchers” in that sense. We’re all trying to keep track of accountability on stuff like this and use what little power we have to protest and counteract government overreach and abuse. When hyperbole and gaslighting are used by those “crying wolf” it makes our jobs that much more difficult. Even after reading through the HN thread I still am not sure if the threat is real or imagined. There are a couple paranoid leaps in logic asserted as fact, and that makes it impossible to know which other “facts” are actually just opinions. By all means, they should GTFO of France if they feel they might be threatened, but turning around and saying they’re being imminently attacked by France makes it so much harder to understand what’s actually happening.
I did skim through some similar discussion on the HN link, which you can read here: https://news.ycombinator.com/item?id=45999024
I honestly don’t know or care enough to figure out how much exaggeration is taking place, but it seems like there’s at least a possibility that this is a nothingburger from a powerless journalist that’s being extrapolated like crazy. There might be a definite answer in that thread but I don’t have the time to evaluate all angles of this incident right now.
Graphene (more specifically its founder) is always in a vicious cycle of claiming that everyone asking for proof of Graphene being “under attack” is in itself making an “attack”. You can consider yourself Graphene’s enemy for life for your transgression.
Watching these youtube links makes you an attacker also, so be careful: https://youtu.be/Dx7CZ-2Bajg https://youtu.be/4To-F6W1NT0
I don’t want to write up a whole paper at the moment but I’ll note that you really shouldn’t be trusting any cloud providers with your data, because you should always be fully encrypting your data before they get their hands on it. Plasma Vaults (if you use KDE) are one way to do this, or you can use something like Cryptomator, gocryptfs, etc. Basically how it works is that you store files encrypted in one directory (/home/me/Encrypted), then transparently unencrypt that data to another mountpoint for your regular usage (/home/me/Unencrypted). Modifications in the Unencrypted directory will automatically affect the Encrypted directory through the use of magic. The cloud provider will only sync the Encrypted directory, and without the key they know nearly nothing about what your data is.
Given this sort of workflow, you can store your data anywhere, as long as you have a nice (open-source) way of syncing to that provider that can’t introduce any further vulnerability.
Absolutely not trusting this. Uninstalling until we know more, and ideally just getting a different solution entirely. A new account tried to impersonate Catfriend1 directly at first, and then they switched to researchxxl when someone called it out (both are new accounts). Meanwhile the original Catfriend1 has provided no information about this, and we only have the new person’s word as to what’s going on. There’s way too many red flags here.
I just want to note that Jellyfin MPV Shim exists and can do most of this MPV stuff while still getting the benefits of Jellyfin. You’re putting a lot of emphasis on Plex-specific limitations (which Jellyfin doesn’t have obviously) and transcoding (which is a FEATURE to stopgap an improper media player setup, not a limitation of Jellyfin).
Pretty much every single “Pro” is not exclusive to pure MPV vs. Jellyfin MPV Shim, which mainly leaves you with the cons. Also as another commenter said, I set my Jellyfin up so that my friends and family can use it, and that’s its primary value to me. I feel like a lot of this post should be re-oriented towards MPV as a great media player, not against Jellyfin as a media platform.
Yep, I forgot it’s not a company. The point stands though; someone has to pay for the servers and administration, and if they run out of money or the foundation falls apart, then the problem happens in the same way. I don’t know much about Wikipedia’s structure, but I would guess it’s a similar situation in terms of needing money to stay running and also being able to be salvaged by the community if it does go down.
I don’t think it will be a big deal to transcode MP3 to Opus as long as you’re okay with for-sure having theoretically-scuffed-up audio files. Every time an encoder has a go at the files (especially different encoders) they’ll leave little artifacting marks all over the waveforms, typically seen as little “blocks”. Are they audible? Doubtful. If you want to keep a neat and high-quality library I’d recommend collecting FLAC next time around.
Also, this won’t work on Win11, and I don’t think you can make it transcode MP3, but if anyone happens to have slightly different requirements I’ll plug https://gitlab.com/beep_street/mkopuslibrary, which I use to keep my FLAC library in sync with a parallel Opus library for mobile use.
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/.
Check their transparency log for subpoenas etc: https://signal.org/bigbrother/
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.
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.
Apparently the price increase happened yesterday; I hadn’t heard anything about it until just now. Gave me the push I needed to switch to self-hosted vaultwarden in like 15 minutes. Very pleased with how simple the docker compose and export->import were. I’ll note that I’m running it privately on my local network, which I’m assuming should work fine as my devices enter that network semi-frequently and should keep everything synced up(?).