Do you believe pro-IDF groups should be allowed on campuses despite the fact that they are genocidal collaborators?

That's not what it means

That's because "cancel culture" doesn't actually mean anything.

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.

The act of book banning itself isn't the real issue. The issue is the homophobia/transphobia motivating the conservative book banning.

There are many, many good reasons to not use Brave. Being spyware is not one of those.

Boycott Brave for real reasons like their CEO and owner being a raging anti-gay reactionary or because of their cryptocurrency bs.

Unfortunately, adoption has been slow and Alliance for Open Media are pushing back somewhat (especially Google^1, who leads the group) in favor of their inferior .avif format.

Agreed, but i wish we could all just adopt the CommonMark standard with a few changes/additions (in order of how needed they are) to really complete it:

• anchors/heading identifiers

  • Creating a heading with a custom identifier:

  • Creating an anchor/heading identifier (clicking a link to an anchor would navigate the user to whatever block/paragraph contained the anchor):

    ## the name of my heading {#header-id}
    
    {#a-paragraph} Blah blah blah blah.
    
    {#list}
    - blah
    - blah
    - blah
    

  • Linking to an anchor/heading:

    Here's [a link](#list) to my list in my ["the name of my heading"](#header-id) section.
    

• footnotes

  • Note: The part in brackets is the reference. The part at the bottom is the reference definition.

  • But we should have it so that if the reference definition is just a link, it's treated as a link reference and presents as a normal link, but otherwise it's treated like a citation and just navigates you to the reference definition.

  • Example:

    I learned about blank[^footnote] after i saw someone mention it on [Lemmy].`
    
    [Lemmy]: https://join-lemmy.org/
    
    [^footnote]: Author's name, Date accessed. Title. https://www.example.com/.
    

• tables

• in-line strikethrough

• in-line spoilers

• superscript

  • But something less ambiguous than normal^super is needed (notice how, normally, the notation for all in-line formatting is surrounding text with some special character(s)). Something like normal^super^ may be better.

• subscript

  • Again, we should probably come up with something less ambiguous than normal_sub. Maybe something like normal_sub_? And yes, i know _text_ is sometimes used for italics instead of *text*, but that's something that just needs to stop honestly.

I think the best way to go about this would be adopting the CommonMark standard but adding/changing a couple things to really complete it:

• anchors/heading identifiers

  • Creating a heading with a custom identifier:

  • Creating an anchor/heading identifier (clicking a link to an anchor would navigate the user to whatever block/paragraph contained the anchor):

    ## the name of my heading {#header-id}
    
    {#a-paragraph} Blah blah blah blah.
    
    {#list}
    - blah
    - blah
    - blah
    

  • Linking to an anchor/heading:

    Here's [a link](#list) to my list in my ["the name of my heading"](#header-id) section.
    

• footnotes

  • Note: The part in brackets is the reference. The part at the bottom is the reference definition.

  • But we should have it so that if the reference definition is just a link, it's treated as a link reference and presents as a normal link, but otherwise it's treated like a citation and just navigates you to the reference definition.

  • Example:

    I learned about blank[^footnote] after i saw someone mention it on [Lemmy].`
    
    [Lemmy]: https://join-lemmy.org/
    
    [^footnote]: Author's name, Date accessed. Title. https://www.example.com/.
    

• tables

• in-line strikethrough

• superscript

  • But something less ambiguous than normal^super is needed (notice how, normally, the notation for all in-line formatting is surrounding text with some special character(s)). Something like normal^super^ may be better.

• subscript

  • Again, we should probably come up with something less ambiguous than normal_sub. Maybe something like normal_sub_? And yes, i know _text_ is sometimes used for italics instead of *text*, but that's something that just needs to stop honestly.

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:

I get the frustration, but Windows is the one that strayed from convention/standard.

Also, i should've asked this earlier, but doesn't Windows also only look at the characters following the last dot in the filename when determining the file type? If so, then this should be fine for Windows, since there's only one canonical file extension at a time, right?

Super interesting stuff! Thank you for sharing.

True, but it offered a much more secure alternative to opening up PDFs locally.

What's messed up is that, technically, we do. Originally, OpenDocument was the ISO standard document format. But then, baffling everyone, Microsoft got the ISO to also have .docx as an ISO standard. So now we have 2 competing document standards, the second of which is simply worse.

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.

Sounds like a Windows problem

AV1 can do lossy video as well as lossless video.

Different ways of compressing the initial .tar archive.

So there's a tool called tar that creates an archive (a .tar file. Then theres a tool called zstd that can be used to compress files, including .tar files, which then becomes a .tar.zst file. And then you can encrypt your .tar.zst file using a tool called gpg, which would leave you with an encrypted, compressed .tar.zst.gpg archive.

Now, most people aren't doing everything in the terminal, so the process for most people would be pretty much the same as creating a ZIP archive.

This is the kind of thing i think about all the time so i have a few.

• Archive files: .tar.zst
  • Produces better compression ratios than the DEFLATE compression algorithm (used by .zip and gzip/.gz) and does so faster.
  • By separating the jobs of archiving (.tar), compressing (.zst), and (if you so choose) encrypting (.gpg), .tar.zst follows the Unix philosophy of "Make each program do one thing well.".
  • .tar.xz is also very good and seems more popular (probably since it was released 6 years earlier in 2009), but, when tuned to it's maximum compression level, .tar.zst can achieve a compression ratio pretty close to LZMA (used by .tar.xz and .7z) and do it faster^1.

    zstd and xz trade blows in their compression ratio. Recompressing all packages to zstd with our options yields a total ~0.8% increase in package size on all of our packages combined, but the decompression time for all packages saw a ~1300% speedup.

• Image files: JPEG XL/.jxl
  • "Why JPEG XL"
  • Free and open format.
  • Can handle lossy images, lossless images, images with transparency, images with layers, and animated images, giving it the potential of being a universal image format.
  • Much better quality and compression efficiency than current lossy and lossless image formats (.jpeg, .png, .gif).
  • Produces much smaller files for lossless images than AVIF^2
  • Supports much larger resolutions than AVIF's 9-megapixel limit (important for lossless images).
  • Supports up to 24-bit color depth, much more than AVIF's 12-bit color depth limit (which, to be fair, is probably good enough).
• Videos (Codec): AV1
  • Free and open format.
  • Much more efficient than x264 (used by .mp4) and VP9^3.
• Documents: OpenDocument / ODF / .odt
  • @[email protected] says it best here. .odt is simply a better standard than .docx.

  it’s already a NATO standard for documents Because the Microsoft Word ones (.doc, .docx) are unusable outside the Microsoft Office ecosystem. I feel outraged every time I need to edit .docx file because it breaks the layout easily. And some older .doc files cannot even work with Microsoft Word.

You might like this

https://www.youtube.com/watch?v=R_b2B5tKBUM