Planètes, décors, machines, personnages... Je veux tout :P <@https://im-in.space/web/@noroanka/111913341057705258>

On moderating social media (from Reddit's ex-CEO)

https://nitter.net/yishan/status/1586956145813377024

2 in the morning is a great time to compare compression algorithms.

Ratio   File size   Filename            Command                     Algorithm
      1  1458553185 build/
  0.451   658022612 ../node-modules/
  0.322   469704387 build.tar.Z         compress -k build.tar       Lempel–Ziv–Welch (LZW) (oh, how far we've come)
  0.185   269780511 build.tar.gz        gzip -k9 build.tar          Deflate
  0.082   119839762 build.tar.bz2       bzip2 -zk9 build.tar        Burrows–Wheeler transform
  0.047    68258612 build.tar.br        brotli -kZ build.tar        Brotli
  0.047    67989604 build.tar.zst       zstd --ultra -22 build.tar  Zstandard
  0.046    67705992 build.tar.xz        xz -zk9e build.tar          Lempel–Ziv–Markov (LZMA)

0.046 is really mind-blowing. I don't need a torrent, we're approaching e-mail attachment file sizes here.

Good call tonight, touched on some interesting topics.

• Use cases for encrypted feeds (#770)
• Trying to reproduce "Bad Request" when replying to a twt (#ej6bbpq)
• Categorization of feeds (Lists) (#937)
• Media uploads using yarnc
• Handling NSFW content (#944)

@david I don't want to discourage any idea, indeed I think it's a good one. I've read the whole RFC 770, so I think I understand the result, but not the why. My concern comes from the overhead of having to:

• Manage a lot of keys (with the problems it creates of string private keys)
• Decrypt every message once it arrives
• Not having a way for the non-compatible browsers to hide this content.

Awk and roll: https://gitlab.com/snippets/1907701