[–] 2 points 2 days ago

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.

  • source
  • parent
  • context
  • [–] 6 points 2 days ago (2 children)

    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.

  • source
  • parent
  • context
  • [–] 4 points 3 days ago

    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.

  • source
  • parent
  • context
  • [–] 11 points 4 days ago (2 children)

    I find that if you don't finish that last 10% now than if you do ever find a use for it you won't bother with that last 10% and will just find a quicker work around to finish the project you were working on instead. Then that last 10% will never get done.

  • source
  • [–] 1 point 2 weeks ago (1 child)

    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.

  • source
  • parent
  • context
  • [–] 28 points 2 weeks ago (25 children)

    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.

  • source
  • parent
  • context
  • view more: next ›