This is a known security issue in Telegram, the one they stubbornly refuse to fix.
Ah, yes, I see... Are the known security issues that Telegram stubbornly refuse to fix in the room with us right now?
Readit NewsDead Comment
Dead Comment
ZeroConcerns commented on Telegram recovery model allows permanent lockout after phishing bugs.telegram.org/c/58477... · Posted by u/saloed
ZeroConcerns commented on Telegram recovery model allows permanent lockout after phishing bugs.telegram.org/c/58477... · Posted by u/saloed
Yeah, I have some bad news about that huge bug bounty you're expecting... ChatGPT was wrong, and there is no way to close the HackerNews account you just created, so all the abuse that deservedly comes your way will, in fact, be on your permanent record.
ZeroConcerns commented on How problematic is resampling audio from 44.1 to 48 kHz? kevinboone.me/sample48.ht... · Posted by u/brewmarche
If only it was that simple T_T
I'm working on a game. My game stores audio files as 44.1kHz .ogg files. If my game is the only thing playing audio, then great, the system sound mixer can configure the DAC to work in 44.1kHz mode.
But if other software is trying to play 48kHz sound files at the same time? Either my game has to resample from 44.1kHz to 48kHz before sending it to the system, or the system sound mixer needs to resample it to 48kHz, or the system sound mixer needs to resample the other software from 48kHz to 44.1kHz.
Unless I'm missing something?
DAC frequency and the audio format requirements for whatever you supply to your platform audio API have literally nothing to do with each other.
My reply was from an audio mastering perspective.
ZeroConcerns commented on How problematic is resampling audio from 44.1 to 48 kHz? kevinboone.me/sample48.ht... · Posted by u/brewmarche
> it's probably worth avoiding the resampling of 44.1 to 48 kHz
Ehhm, yeah, duh? You don't resample unless there is a clear need, and even then you don't upsample and only downsample, and you tell anyone that tries to convince you otherwise to go away and find the original (analog) source, so you can do a proper transfer.
ZeroConcerns commented on My Home Fibre Network Disintegrated alienchow.dev/post/fibre_... · Posted by u/alienchow
> Another thing that should not have happened is installing the cable in loops in this way: any 'building' or 'underground' type cable needs to be of the exact length required at the demarcation point...
This hasn't been my experience with fiber entrance cables terminated by ILECs, Spectrum, and Lumen. They typically leave a significant service loop bound to the cable ladder or backer board-- usually 15-20 feet.
Depends on the type of cable assembly. If it's fiber strands inside a soft-ish plastic jacket (and most of the cable is in fact in conduit), a service loop is fine, albeit a bit pointless for most repair scenarios. For armored cables (which are significantly stiffer), you only do these loops in situations where you expect to need to replace significant sections (think 'getting hit by a falling tree' or 'particularly aggressive rodents') and you have the space.
ZeroConcerns commented on My Home Fibre Network Disintegrated alienchow.dev/post/fibre_... · Posted by u/alienchow
Thanks, I really appreciate the SMEs commenting here. I'm learning a lot.
Definitely learnt it the hard way this time. You're right that buried cables should be exact in length and fastened to a patch panel. I'll probably look into better conduit design as well for the next time (in 15 years?). Having shared conduits means I would risk damaging other cables if I tried to pull a new cable through.
Good conduit and patch panel design is definitely key for a happy life. Leaving some extra space/capacity initially is also a good idea, especially since (unless you're covering truly great distances) there's not exactly a lot of innovation in the single mode fibre space: strands you put in today (even if it's 'the cheapest stuff your vendor sells most of', which is generally my philosophy for selecting cables) will still be viable a few years down the road.
Sharing/in-place-repurposing conduit is not something I'd recommend, but if you must, leave a few dummy cables (a.k.a. 'pieces of string') on the initial install...
ZeroConcerns commented on My Home Fibre Network Disintegrated alienchow.dev/post/fibre_... · Posted by u/alienchow
From one of the photos, the cable spec "G657A2" is visible on the outside - and specs listed for that indicate it's "bending insensitive single-mode fibre", apparently it can tolerate 10 loops around 15mm mandrel. (Which does surprise me).
But yes, agreed, a lot of "Er... why would you do it like that?" bits.
Those 10 loops definitely only apply to the single mode fibre itself, not the entire assembly with armor and everything, because that's just... physically impossible.
Cables for direct burial only like to be bent once or twice, and then only gently. Anything else may very well break the armor (whether plastic or metal), after which all bets are off.
Still, for the outer jacket to become brittle to the extent described, something else is required, which may very well turn out to be "shoddy manufacturing"...
Basically, it rebuilds Windows DPAPI from first principles, which is fine (I've done it many times myself!), and something non-Windows platforms sorely need. It changes the impact of malware from "they dumped all our secrets from prod to their C2" to "they got some encrypted values, and now someone will need to figure out our methodology and underlying keys", which is a meaningfully higher bar.