• 🇦🇺𝕄𝕦𝕟𝕥𝕖𝕕𝕔𝕣𝕠𝕔𝕕𝕚𝕝𝕖@lemm.eeEnglish
    1·
    5 days ago

    The next step would be instance agnostic content links. Could probably keep it so instances still serve images/link content but instead of sending out the raw link to clients send em a “lemmy link (https://instance/link/hash” that redirects to the og link where the hash is a value in a DHT for bittorrent. This should avoid breaking most clients while also letting the client bittorrent the content distributing load.

    U could also probably create an option to then use this to serve caches/archived pages instead of the originals making lemmy and the associated distributed torrent data an internet archive of popular links.

  • PhilipTheBucket@ponder.cat
    4·
    7 days ago

    Looks like it’s brand new. The fix was only committed in September, and maybe not even on the main branch? I’m not completely sure, but it looks like it’s coming, as opposed to something that’s already here.

    • Spzi@lemm.eeEnglish
      4·
      7 days ago

      Makes me happy to hear this important feature is about to become reality! <3

      • PhilipTheBucket@ponder.cat
        5·
        7 days ago

        Looks to me like it’s in the “main” branch but not in 0.19.7. Maybe the release branch was forked before it went in? Maybe there’s active development on a 0.20-targeted line, with some fixes getting backported to 0.19 as they’re needed? I don’t know. But I think it’s in the development branch, but hasn’t made it to production quite yet.

        $ git checkout main
Switched to branch 'main'
Your branch is up to date with 'origin/main'.
$ grep 'Rewrite markdown' api_tests/src/post.spec.ts
test("Rewrite markdown links", async () => {
$ git checkout 0.19.7
HEAD is now at fc8280a9b Version 0.19.7
$ grep 'Rewrite markdown' api_tests/src/post.spec.ts
$