• 7 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: June 28th, 2023

help-circle



  • Feel how you want, but Spotify has a very clear policy on hateful content. And sure, maybe you won’t listen to it, but do you know who will? Bigoted psychos that will go out and commit a hate crime. Allowing content like this on a popular platform will lead to hate crimes. There is nothing wrong with private platforms choosing to not platform certain kinds of content and it is entirely within their right.

    Spotify has the right to deplatfom hateful content and doing so is the ethical thing to do.









  • However, getting people used to double extensions is one quick way of increasing the success rate of attacks such as the infamous “.pdf.exe” invoice from an email attachment.

    Very good point. Though, i would argue that this would be much less of a problem if Windows stopped sometimes hiding file extensions.

    I can’t see how Windows’ convention is worse

    I don’t believe what you’re referring to is really a Windows versus Linux/Unix thing.

    If I zip a file, it doesn’t matter what it was in a previous life, it’s now a zip - this is also how Unix deals with many filetypes, I’ve never seen a .h264.mp4 file, even though the .mp4 container can actually represent different types of encoding.

    I disagree, but i do get what you’re saying here. I don’t think that example really works though, because a .mp4 file isn’t derived from a .h264 file. A .mp4 is a container that may include h264-encoded video, but it may also have a channel with Opus-encoded audio or something. It’s apples and oranges.

    Also, even though there shouldn’t be any technical issues with this on Windows, you can still use a typical short filename suffix if you wish, though i would argue that using the long filename suffix is more expressive. From “tar (computing)” on Wikipedia:

    Compressor Long Short
    bzip2 .tar.bz2 .tb2, .tbz, .tbz2, .tz2
    gzip .tar.gz .taz, .tgz
    lzip .tar.lz
    lzma .tar.lzma .tlz
    lzop .tar.lzo
    xz .tar.xz .tx
    compress .tar.Z .tZ, .taZ
    zstd .tar.zst .tzst





  • The problem here being that GnuPG does nothing really well.

    Could you elaborate? I’ve never had any issues with gpg before and curious what people are having issues with.

    Unfortunately currently there aren’t many options to use AV1 in a very meaningful way; you can encode your own media with it, but that’s about it; you can stream to YouTube, but YouTube will recode to another codec.

    AV1 has almost full browser support (iirc) and companies like YouTube, Netflix, and Meta have started moving over to AV1 from VP9 (since AV1 is the successor to VP9). But you’re right, it’s still working on adoption, but this is moreso just my dreamworld than it is a prediction for future standardization.