I started with podman and wanted to like it. Ultimately moved to docker because of docker compose
I started with podman and wanted to like it. Ultimately moved to docker because of docker compose
This is madness. How does this keep getting upvoted when the article has nothing to do with the actual code integrity and functionality of this browser.
At least it’s open source, if there is something shady point it out in the code.
Oh no. Man that sucks. Which one? The lemur pro by system76 was a clevo I had it for a bit and thought it was really good all around. I would have kept it but the specs on a M1 were just ridiculous compared to anything out there. No fans, no dust collection was something I didn’t know I appreciated so much
Always wanted to try a star labs product. What always stops me are the specs. Not enough ram or storage or CPU to justify the price. Even though I know the premium is there because they aren’t just white labeled clevos like every other Linux focused PC company
I feel really dumb but I can’t find any documentation on his to use it other than instructions on how to install a node
No different than syncing to a server. Many video calls are implemented with p2p up to a certain amount of participants. Text is less demanding in comparison. I’ve not dived into the code yet but p2p relays typically just coordinate what IPs need to connect. In your case, once the connection is established the phone is directly transferring data with your laptop. No server in between.
So actual hover boards soon?
Yeah waiting for this too! I’ve not dug into hosting the node yet, I wonder if any one has or if there is even documentation for it. I don’t see a way to point the app to the another sync node. Could be I’d have to compile the front end myself to point it to another node
Yep. I’ve not tried it yet. Finally came around to playing around with it though. What I noticed is by default it syncs to the backup and I can’t figure out how to turn it off yet. That said the files are decrypted locally with the keys made when the account is created. About to look more into the privacy policy.
I like affine.pro and appflowy but both were not really usuable last I tried them. The self hosted options are barely functioning so at the end of the day it’s just local. For a nice looking self hosted wiki I got outline working after tinkering for some time. Affine has been promising!
In their FAQ they explain making money initially by offering paid backups. What’s interesting is their future plans, their vision of a cooporitive ecosystem or whatever, they make money off namespaces/domains, publishing/work contribution, in addition to the backups. This is of course if it gets engagement like notion, it will demonstrate ways to make money from an open network.
If you’re betting on the tech culture moving to decentralized services this could be a way to have a foot in it.
They tout it being made ‘local first’ all data would then be stored locally so the user can access it offline. The 1 GB limitation is for paid backups which a user doesn’t have to do. If I wanted a backup, I could just share p2p share from my laptop to my PC for example. Both would have copies.
The p2p relay is a way to coordinate p2p connections, data doesn’t pass through them. Once a connection is made between my laptop and my PC data is transferred directly.
On the topic of the p2p relay it could expose IP addresses and device meta data. I’ve not done digging yet into the relays. But then again most DHTs do and even something like synthing has relays like this.
It will all be over soon. In the not too distant future these will just be vending machines.
Self hosted? Looks like everything runs locally, what is being hosted? Are you talking about the p2p relays?
Will need to check the UI and post again. The buzzwords are directly speaking to remote work culture and a migration away from central services. The ecosystem, their plans to make money off that network are an interesting way to get ahead of those market movements. I’m not opposed but I am suspicious of it.
Skiff was kind if a disappointment when it came down to it. Using decentralized storage web3 privacy buzzwords but finding different ways to vendor lock and track.
This needs a pin