Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

I also want money, but I don't lie about my grandma dying to get it from my friends.


I don't worry about multi billions dollar company having to lobby a little more to update the default port format in 10 years. They are good at it.

I do worry about the invisible hand of the market not being a good balance for interoperability or sustainability.


Well, if you start enforcing quality standards, suddenly, local products become way more competitive.


Fun


For now, flatpack and snap sandboxes perf hit are quite significant, and devs don't manage the permissions well so you often end up with software that can't open the files you want.

When you fire and electron app from a sandbox, it's a hog riding a slug, then you try to open your files only to find yourself in a temp folder or chrooted to a config subdir.

It think those tech can bring a lot, but there is still work to do.


Flatpak doesn't hurt performance any worse than something like Docker. It's Snap that's slower since they keep the entire app compressed on disk. Permissions are also up to the app developer in the case of Flatpak so if they don't use portals like they're supposed to then they can just allow the app to access the whole host filesystem. You can change this easily too through your terminal or an app like Flatseal.


Snap permissions are a mess.

The fact that I have to give Remmina each of its permissions one at a time after installing with snap is silly.


Are other people experiencing too many corruption problems on encrypted disks?

I have a veracrypt drive, and I regularly have to run a scan and fix on it because it's very sensitive to power cut, brutal restart, etc.

Also, it's slow. I put my firefox conf folder in it, but it slows the browser down.

Once I went full encrypted disk, but one day corruption happened, and it stopped booting. So I went back.


Don’t generalize your problems with a specific software (Veracrypt) to all drive encryption software. Plenty of drive encryption solutions are fast, reliable, and resilient. (You could also be having a hardware problem exacerbated by adding an abstraction layer.)

I’ve used LUKS, GELI, ZFS encryption, FileVault, and BitLocker across numerous drives over the past decade (albeit in different individual proportions and timelines) with no corruption problems.


I’ve not used verycrypt, only normal Linux LUKS device mapper encryption, ZFS encryption and windows bitlocker full disk encryption with a paraphrase entered on boot (no tpm). But I haven’t had this problem with any of those.

I’d suggest either your SSD just loses data on power off which is a problem with some SSDs or it’s some veracrypt specific issue that I wouldn’t be familiar with.

Id encourage you to try out one of the above options.


You probably have some fun disk caching turned on in the OS or your disk has a built in cache that it’s not properly flushing. I’ve seen this before with cheap SSDs.


Maybe, I don't know enough about this, but I've been using this veracrypt disk on 6 machines, now, and I have the problem with each of them.

Also, I don't have any problem with non encrypted data.


Maybe a dumb question, but are you on windows? Check that Defender isn't scanning every single time data is written to your veracrypt drive. When I was on windows, the most painful slowdowns were almost invariably caused by Windows Defender.


Looks like a veracrypt problem then.


No. I run a server in my basement, and for the past 5+ years, every one of its drives have been LUKS encrypted, including external backup drives. I've had no issues with encryption (corruption, speed, or otherwise), only disk hardware failing outright.


Servers and consumer laptop are very different beast though, so not sure the comparison hold. You don't shut them off often, they don't go to sleep, rarely undergo shock, plane travel or forced shut down...


Friend, LUKS is reliable. LUKS doesn't just eat data in those edgecases you talk about, there would be tons of reports if that were the case. LUKS is used all over the place for non-server uses too.

I can count at least 3 devices that are all LUKS-encrypted that are used as consumer devices daily. I trip over the power cord, I let the battery die, I drop it, I fly regularly, etc, etc. Never once had a single issue.

In fact, the single time that I've had FS issues under Linux was running under Hyper-V but that's because of the slowly-being-uncovered serious issues w/ Hyper-V.


Never had a problem with LUKS over a decade of usage.

In fact, I'm actually having the opposite issue: I have a drive that is failing and LUKS is still able to decrypt it by some miracle.

> Also, it's slow.

Modern CPUs have AES instructions built-in. I would check to make sure you're utilizing them. You should not see any slowdown when using encryption.


The better solution to these kind of problems is having a backup concept with an implementation and regular testing of backups.

The encryption exposed a problem with your disks or system in general. Depending on what the problem was, the problem is still there but you are not seeing it. Now you have a possible problem and unencrypted files.


I have a backup, but this is not a solution. Only a crutch. I had those problems on several machines, including brand new ones.


I started using full disk encryption (except /boot) this year, so far no problems at all. I'm using ordinary luks on Fedora.


Same but I already find ajax based app very slow if they implement optimist updates, now with this system, you have to wait a round trip for each interactions. This means click a counter will round trip before updating?


You can apply this to any interaction where you have to wait for a round-trip anyway. It saves you coming up with a JSON schema and endpoint for the request, and then gluing it all together.

It doesn't mean that you don't use javascript at all, you just use it in a limited fashion for enhancing specific bits of your website. Just like it was in the 2000s when making websites was easy.


If you want to save state for the counter to the server you would do a round trip. Otherwise you’d use some light weight JS lib, most popular one for simple interactions is Alpine.js. So simple ui JavaScript use Alpine and something like form validation and showing errors will do a round trip and save you writing validation twice (on the client and on the server).


Ok, so the trade off is a less snappy UI as soon as you have a state, because you can't do optimistic updates on the view, send the request, then deal with the error.

But you write only the code of the validation, and the vue, once, so it's more productive, and the state is always consistent.

I assume this means no PWA mode, although I don't really miss this.


The round trip is very quick, websocket with a tiny payload in most cases. This video does a great job of discussing the advantages (skip forward to 6:50) https://youtu.be/8xJzHq8ru0M


Payload size doesn't matter that much, a ping is ping.

Currently my ping to this website is 167 ms:

ping news.ycombinator.com PING news.ycombinator.com (209.216.230.240) 56(84) bytes of data. 64 bytes from news.ycombinator.com (209.216.230.240): icmp_seq=1 ttl=49 time=167 ms 64 bytes from news.ycombinator.com (209.216.230.240): icmp_seq=2 ttl=49 time=167 ms 64 bytes from news.ycombinator.com (209.216.230.240): icmp_seq=3 ttl=49 time=167 ms

Which means it's a cost I have to pay, before payload matters, before parsing matters, before rendering matters.

I'm at home, on fiber, on an ethernet cable, so ping should be very fast. And it can be:

ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=5.63 ms

Unfortunately, the network is not uniform.

It's of course, worse on Wifi, and even worse on mobile phone, on the go. Depending on your location, YMMV quite a lot as well. Then you have hardware quality playing a role, the user may use other software (torrenting, streaming, playing) that can also affect that.

Bottom line, you cannot assume the internet connection is snappy. Or stable (which is a problem with websocket, as you have to implement robust automatic reconnect, and it is slow and expensive, but then your use cannot use your software).

So knowing the trade off you make is important. On a local network in the corporate world, life view seems like a terrific deal. On a heavy mobile user centric app, it will probably hinder your app ergonomics.


Does this mean the entire state of each connected user is hold on the server?

What's the resource cost ?

And that adding an element on a list don't show it up before a server round trip ?

What's the latency cost ?


It's a tough ethical choice. On one hand, you want a company to avoid leaking data to bad actors, on the other hand, this would probably first used against legitimate whistleblowers.


As the basis we offer our technology that works as a converter, it has only a positive effect. You can use our platform to upload documents, share with contractors, with the internal team and be sure that all these sensitive documents are marked with invisible marks, and in case of a leak using an investigation tool, you will be able to find the source of the leak. Additionally, we can help to mark documents sent via email our printed out, once again it has just a positive function for the company to be sure that all their info is under the control. With our technology, we want to help to create a preventive effect.


I don't see how you address the whistle blower issue.

I get how useful it can be, but repeating "positive" is not a magical solution.


There is already type inference in Python type tooling.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: