• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle





  • Ugh word does this. I didn’t realize until I wrote some documentation for a cli tool I made for a client and I wrote the documentation in word because they are fairly non technical so I wrote in the documentation sample arguments they can copy and paste and shipped it feeling good that it would work flawlessly because I tested the crap out of it. Or so I thought because they immediately hit back with it doesn’t work. I spent hours recreating their environment and watching it work no matter what I tried to get it to not work. Then I hopped on a call and had the client step by step show me what they did and they opened the word doc and copied the example commands, changed the arguments to be correct and run it. I followed along on my own machine and then I fucking saw what had happened. Fucking Microsoft Word replaced my " " with “ ” (straight quotes for smart quotes for those who cant see the difference). A quick patch of the cli to properly parse those and things were working again.







  • He bought a company that got bought by PayPal. He didn’t build anything he didn’t run anything. He bought an existing company that got bought out. At SpaceX and Tesla they have entire structures created to stop Elon from fucking up shit and to manage him. If you need your company organized to manage the owner and stop them from fucking shit up you don’t get to claim to be smart or to build amazing stuff. In every case it’s the engineers that build amazing things despite Elon’s involvement. Elon himself is an idiot.



  • 1.) Turns out this is no longer true because the cors issue is fixed as of two weeks ago.

    But to answer your question:

    Well that’s the really silly part about it. You see, the way CORS works is that it only works if the client making the request implements cors. In this case when I say client I’m talking about your web browser itself. Native applications, or hitting an API directly via network calls, don’t implement cors and thus you can make the calls all you want and the server responds. So even when cors was configured to only allow requests from the correct domain it only affected people with web browsers.

    However two weeks ago a PR was merged into the Lemmy source code setting the cors to by default allow requests from anyone instead of a specific domain.



  • Web front ends currently require a backend service that then routes to your intended destination because Lemmy servers by default are configured with cors to only allow requests from their intended domain. There is a PR to fix it but I don’t believe it’s been merged in. This may be out of date but that was true as of a few weeks ago per the dev of Voyager which is the web frontend I use

    edit: this is no longer true. A PR 2 weeks ago fixed this issue and web front ends are able to work just as well as a native app now.