Other accounts (verify ownership):

  • @moseschrute@lemmy.ml
  • @moseschrute@lemmy.zip

aspe:keyoxide.org:JOVNV7OHSJCZMPZCCWS5TZI34A

  • 6 Posts
  • 140 Comments
Joined 1 year ago
cake
Cake day: October 6th, 2024

help-circle

  • I don’t think caching benefits Lemmy and PieFed content that is changing very rapidly (e.g. new comments). That type of caching makes more sense for Lemmy/PieFed images.

    However, bot traffic can get very expensive these days with all the AI crawlers. Cloudflare offers very good tooling to block these bots. I know there are other open source tools and I’m not defending Cloudflare, but it’s also easy to criticize when you’re not the person running the instance. From what I’ve seen, all the admins work very hard to keep the threadiverse running. I’m guessing that’s why a lot of instances are using Cloudflare.











  • Not that you should vibe code, but you could vibe code this so easily. Have it output a static website. Give the source code a scan if you’re paranoid. Check the network tab if you’re really really paranoid. But literally you could have it output this as a static index.html file that you drop into your browser of choice.

    This is the only type of coding LLMs should ever be used for imo. A small, very clearly defined task that is very easy to verify if it works. And code that won’t infect a larger project.

    Edit: as others pointed out, that url isn’t base64 encoded. You would have to clearly define what you are trying to do if you want this to work. For example, do all urls follow the same format as the above?





  • There were 15 stakeholders, 1 full time developer and 20 overseas contracted developers with a 12 hour time zone difference from the full time dev. All designs were done in PowerPoint by one of the stakeholders. The single full time developer was only ever able to talk to the PowerPoint design stakeholder, and the other 14 stakeholders communicated through the single PowerPoint stakeholder. Now that I think about it, the 15 stakeholders may have actually just been the 1 stakeholder pretending to be multiple people.

    I once had a job that worked like that lol





  • Interesting. I run a Threadiverse client on iOS and Android. I haven’t run into any issues with Google, yet.

    Apple has this rule I had to comply with:

    • You must be able to delete your account from the app
    • Lemmy delete account via the API requires password entry, even if you’re already logged in
    • Apple however, claims password entry is too much friction for the user to delete their account
    • A workaround is to link out to Lemmy website to delete your account. Even if you have to enter your password on the website, in Apple’s mind, this is somehow allowed despite being more friction?

    I get the sense Apple wrote these rules to improve user experience, and they’re applied without anyone really considering what effect they’re having on the UX.