Skip Navigation

Posts
23
Comments
362
Joined
2 yr. ago

Mostly a backup account for now, other @Deebsters are available.

  • The idea of having Verso as a self-updating shared webview library is interesting, although runs the danger that your Tauri app could break at a random point in the future, especially if you're doing something slightly strange to work around a bug or shortcoming.

    you know which xkcd I'm thinking of, no need to actually link it, right?

  • Given the sub, I was expecting to be surprised that Solarpunk was one of these difficult topics.

  • fd is a massive upgrade to find - I appreciate the better UI and skipping hidden files is usually a big time saver (although I do find myself needing -H or specifying the directory a fair amount).

  • I've never known how to pronounce it... Arr ziːv? Arr shɪv?

    Edit: that'll teach me to not comment before reading:

    it’s pronounced like “archive”

  • They always used to break for us, and we'd have to go back to the trusty Competition Pro:

  • Deleted

    Permanently Deleted

    Jump
  • So they rewrote Nepenthes (or Iocaine, Spigot, Django-llm-poison, Quixotic, Konterfai, Caddy-defender, plus inevitably some Rust versions)

    Edit, but with ✨AI✨ and apparently only true facts

  • Good catch - he's updated the graphic but this is still wrong.

  • He's mixed up the first two diagrams - Pluto should be coloured in for the first and not for the second.

  • hey hey

    Jump
  • It looks like there was a text box bottom-left that was cropped out, but I think it's funnier without it.

  • Zero

    Jump
  • What's the name of the book?

  • I think I need to spend a while watching and reading everything this guy's ever done, especially if it's in this dry, understated humour.

    The old footage looked like Robot Wars if they didn't have any safety requirements.

  • After being virtually dead, it's had a lot more development over the last few years(?), with steady progress towards passing the tests and supporting the specs (including reporting spec bugs and vagueness). It's still a long way from being generally usable.

    The focus is on making something that could be embeddable, although there are basic browsers using that embed. The focus seems to be on for use-cases like Electron, which doesn't need all of the web APIs.

    I don't use it or contribute (yet), but I have their blog in my RSS reader and so keep an eye on it.

  • What names has this process come up with?

  • !nowhereelsetoshare@sh.itjust.works, for when you want to share something, but can't figure out where it fits

    Jump
  • I like that one of the first things I see is The UX of LEGO Interface Panels - you've got yourself another subscriber!

  • Not really a "not the onion" story.

  • I'm not sure how the Mastodon--(ActivityPub)-->Lemmy bit works, but Lemmy doesn't have a concept of a gallery. The first(?) media is your video, and that's showing up in Lemmy. I assume it's dropping the other images since there's no Lemmy structure to put the other media items into.

    btw, now I'm on Firefox/Win10 with the default Lemmy frontend and I can see that video and play it from Lemmy's embed, so perhaps most people can see it (as long as they don't click on the .mp4 link).

  • By "linked" I meant that it's where the URL field of a Lemmy post is pointed at, not the other pages you linked in the post body. Now I'm on a PC again, I see that that link is to the leafy-backgrounded .mp4 (so there's no chance the embedder would have found the other post images if Lemmy didn't present them).

    I think the mp4s-not-playing problem is a Mastodon bug/quirk as I've seen it before - neither Firefox nor Chrome can play them when navigated to, but both can play embedded and they work when downloaded. From the console logs, it seems to be a problem with the Content Security Policy stopping the rest of the video loading (since browsers only load the first chunk of a video to allow streaming):

    Chrome:

    Refused to load media from 'https://furry.engineer/system/media_attachments/files/114/090/866/048/236/635/original/897a5752b038f3e3.mp4' because it violates the following Content Security Policy directive: "default-src 'none'". Note that 'media-src' was not explicitly set, so 'default-src' is used as a fallback.

    Firefox:

    Content-Security-Policy: The page’s settings blocked the loading of a resource (media-src) at https://furry.engineer/system/media_attachments/files/114/090/866/048/236/635/original/897a5752b038f3e3.mp4 because it violates the following directive: “default-src 'none'”

  • Huh, so there is. I'm not 100% on how Voyager works - specifically I think (but don't know) that it's got the video because it's connected to the linked URL (your original post in this case) and pulled down data to make the link preview.

    If that's right, it means Lemmy isn't handing the media at all.