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

help-circle








  • Speaking specifically about npm: A ton of packages used as dependencies for a million different things have very loose quality control, some even merge community PRs straight to release without checking the code in any way. More often than not I have run into packages maintained by people with no connection to the original dev and don’t even know how its code actually works.

    I remember a couple years ago I needed to read zip64 files so I picked up the zip file definition and implemented the read operation for it in the package we were using for zips. I only implemented a very small subset of the format to strictly solve my problem. I opened a pr to them saying “here’s some quickstart of you plan to add full support for zip64” - next time I checked they has merged my pr as if was and now were having folks registering issues for incomplete zip64 support.


  • I don’t know. If done well this could be a much better option than pausing whatever you’re watching to show an ad.

    If youtube showed ads on the corner of the screen while you’re browsing around searching for something to watch, it would be a much better platform than what it is today and it would probably make more money too. If Netflix did this they would triple their revenue.




  • Ah I had that popup confused with one of our own; Now that I checked the text on google translate I figured out what’s happening.

    The meet.jit.si domain is a public jitsi instance that is kept by jitsi themselves. They recently implemented this login requirement on that domain (one user in every meeting must authenticate); They probably assumed that those meetings would always be in a browser and our desktop app is not handling that authentication flow properly. I’ll register a task for someone from our app’s team to take a look.

    If you host your own jitsi instance, this login requirement won’t be there and you won’t have this specific issue (though I assume you probably won’t stay with Rocket.Chat anyway due to the E2EE requirement).