• 13 Posts
  • 77 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle



  • Go see a dermatologist.

    A few years ago I would get patches on the back of my hand that would itch and have tiny blisters. They were persistent and over the counter ointments weren’t helping. Finally went to a dermatologist when they got unbearable. The first one I went to prescribed an ointment that sorta worked, but not that great. Ended up going to a second dermatologist when I found out the first one was an anti-vaxxer.

    The second one was on top of his game. He straight up said the first ointment wasn’t a good one to use and prescribed something much better. It knocked out the spots and itchiness after a week or two. I’ve had a couple of minor flair ups since, but the ointment eliminates it pretty quick. Haven’t had any problems for at least a year.

    If you can, go see a dermatologist.


  • That depends. Are you looking at preserving the music without loss of information? Then you need to use a lossless format like flac. Formats like aac, mp3, opus can throw away information you’re less likely to hear to achieve better compression ratios. Flac can’t, so it needs more storage space to preserve the exact waveform.

    You can use a lossy format if you want. On most consumer level equipment, you probably won’t notice a difference. However, if you start to notice artifacting in songs, you’ll need to go back to the originals to re-rip and encode.


  • There’s talk on the Linux kernel mailing list. The same person made recent contributions there.

    Andrew (and anyone else), please do not take this code right now.

    Until the backdooring of upstream xz[1] is fully understood, we should not accept any code from Jia Tan, Lasse Collin, or any other folks associated with tukaani.org. It appears the domain, or at least credentials associated with Jia Tan, have been used to create an obfuscated ssh server backdoor via the xz upstream releases since at least 5.6.0. Without extensive analysis, we should not take any associated code. It may be worth doing some retrospective analysis of past contributions as well…








  • Tom’s Guide has shit reporting. This was the same site that repeated the bogus DDoS smart toothbrushes story. And they’re at it again with more sensationalism.

    From something more reputable:

    The use of the victims’ faces for bank fraud is an assumption by Group-IB, also corroborated by the Thai police, based on the fact that many financial institutes added biometric checks last year for transactions above a certain amount.

    It is essential to clarify that while GoldPickaxe can steal images from iOS and Android phones showing the victim’s face and trick the users into disclosing their face on video through social engineering, the malware does not hijack Face ID data or exploit any vulnerability on the two mobile OSes.

    More from bleeping computer:

    A new iOS and Android trojan named ‘GoldPickaxe’ employs a social engineering scheme to trick victims into scanning their faces and ID documents, which are believed to be used to generate deepfakes for unauthorized banking access.

    Now, don’t get me wrong, you should take malware and social engineering attacks seriously. But get your information from sites that do real security journalism.