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

help-circle



  • If they bought the domains and fired the people it should be easy for someone else to start a new site using the available talent pool to quickly become a relevant name as well.

    Me personally, I strongly dislike IGN because (other than all the common reasons) they force me to access a poorly translated version of their content when I’m perfectly capable of reading their originals in English, so even if they have an article I’m interested on, I can’t easily access any decent version of it because or my geographic location.





  • I was pretty much the opposite lol. Really loved the quest system on the first one and strongly disliked the cast of the second. The third is generally my favorite.

    I got xenogears as a kid who didn’t even speak English after returning a non-functional Medievel 2 and picking xenogears as a replacement simply because it was more expensive and I realized the salesman at the store wouldn’t check the price as long as I was trading one game by another. I didn’t understand most of the game but I still fell in love with it back then. To this day it is still the first game I think of when someone ask me what my favorite is.







  • 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.



  • They don’t really need to be high skilled if they are already employed. They’d be bringing money with them, so its basically an expansion on tourism. Opening opportunities for people to travel without having to disconnect from work. It’s specially useful to attract Americans who notoriously don’t get to take vacation leaves.


  • If I were a billionaire I would be investing hard into opening a series of farm hotels for remote workers all over the world, with some sort of membership system that allowed folks to stay in any of them without hassle. I would provide high speed internet, small office rooms and vast contact to nature, healthy food options, sightseeing deals and that sort of stuff, all of them at locations chosen to keep the city centers at arms length - avoiding the city noise but not going too far from it.

    I’m sure this will eventually be a common business, not many years from now (though probably with lower standards than what I described).


  • 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).