• 0 Posts
  • 288 Comments
Joined 3 years ago
cake
Cake day: June 17th, 2023

help-circle
  • Everything is a tradeoff. At this point there are more valuable things to be spending money on than making chargers that are as fast as possible. Not all cars can charge at 500+kWhs many cannot even do 100kWhs. IMO better to spend money upgrading all the slow 7-50kWh chargers. As well as putting in more slow charging near residents. Kerb charging for people that dont have a driveway in cities or chargers for those living in flats. That would serve people better then spending more money on something very few can actually benefit from.


  • They need a basic remote API and SKD first. Now we have that anyone can implement these local daemons/translation layers if they want to. This is still early days.

    They could at least have implemented a shell

    They do have an interactive shells:

    You can also run interactive shell. Just type ./proton-drive and then the commands directly.

    Though the commands are not the same as Linux equivalents that is IMO not a big concern. Similar things like AWS S3, or even ftp also don’t have the exact same commands. It is really a trivial thing to learn how it works.

    And again, anyone is free to build on this now if they want to.

    I would not be surprised to see a fuse fs popup at somepoint around this.


  • Where’s sftp? s3? smb?

    I would highly suspect this is because they don’t want to handle encryption and decryption on their servers where ever they can. Yes they need encryption for emails they receive but for every thing else they want to have as end to end protected as they can. Which means client side encryption and decryption for almost every thing. That is the big feature that a lot of people are buying into from them.

    All these protocols don’t feal with encryption on the client at all. Which means if they supported them they would need to handle encryption and decryption on the server side. Which I doubt they want to do and likely work hard to avoid at all.


  • Even if you exceed 20W it doesn’t matter. The only real thing that matters is the average draw and the total duration of a session. If you spend most of the time drawing 10W and peek at 50W for a minute then you can run off a 20W powersupply forever.

    But a faster power supply does offer you more benefits. You can play unplugged until the battery is low, plug it in and continue. It will charge sooner letting you unplug it again sooner. If the wires bother you then that can be a big advantage.


  • Yes it is a problem. But a temporary one that IMO is worth the tradeoff. You might not get multiple devices up front but that means other people can have a device at all. Why should you get 3-5 devices and stop 3-5 other people from having one at all? You can share a single device for several months while the initial wave die down and stock is able to be replenished. Then they will remove the restrictions and you can get multiple devices. In the meantime it means more people can get a device and helps to stop scalpers from getting them all. It is a tradeoff, ideally it would be better if there was enough devices for everyone that wants one to get one. But you can only scale production up so fast.


  • I would rather let a few people scalp some devices then give up ownership over the devices I buy. I would not want valve to have a remote way to brick something I have bought.

    The fact you need an account in good standing and it’s limited to one per address helps a lot in cutting down on the number of devices that can be scalped. It is basically just a few individuals that can do that and not a few people systematically buying up all the stock at once to resell.

    I would rather them focus on upping the supply then preventing every single scalper.



  • The time to beat a game is generally for the main story if you don’t take ages doing other things. Quite often with side quests or other non essential steps like collecting things or trying to 100% a game it will take way longer then the estimated time to complete. This is epically true for more open-world type of games with lots of places to explore.



  • I don’t think this is the win we want. Sounds like palwprld change the game to no longer infringe on Nintendo copyright claims. So Nintendo can no longer seek an injunction. They are still seeking damages.

    I really want to see the copyright claims be challenged in court so we know where we stand. Rather then the continual settling out of court because Nintendo has more money.

    It doesn’t sound like Nintendo are on track to win or lose this. Just Palworld changed the game to limit the impact of the lawsuit. Which is in a way a small win for Nintendo.







  • Yeah, Steam may be effectively a monopoly, but it’s because nobody else really wants to compete with them at their level.

    Steam has two types of customers. Us the gamers where we can decide which platform to use. They have an effective monopoly on us because they provide a good service. But with a large game library we are locked into steam as well and cannot just switch to a different platform. If valve ever did decide to be evil then we are screwed.

    But developers are also customers of valve. And this is arguably where valve makes their money. They take a cut from the developers sales. Devs cannot just use a different platform without cutting out a huge userbase. This gives valve a real monopolistic control over developers.


  • Its hard to argue that 2 config files both multiple lines long is simpler then a single line in an existing file. Adding a service to cron is just simpler. But adding all the extra bit you are going to want on top increases the things you need to learn to do and configure correctly.

    IMO systemd timers are simpler to get right at a little bit more of an upfront cost to learning how they work. But cron is still simpler to just get something working without caring that much. I still find that ends up biting you in the longer term though though all the missing features you need to add manually on top of that one basic line you added.


  • Cron jobs are nice and simple to create. Until they go wrong then they are a pain in the ass. You need to manage logging yourself. If you forget you root mail will fill up your disk and crash the system. If you forget the mailto setting. If you remember it you justlose all logs and have no clue why something is not working. You need to redirect the output to a logfile yourself. And then risk filling up the disk with logs unless you remember to also set up logrotate. And you then still don’t know when something last ran or if it ran successfully.

    So many traps and that is just the logging side of things.