HN user

albuic

81 karma

Nothing

Posts4
Comments38
View on HN

No, native app is not platform lock-in... You just need to choose the OS correctly and also the app. The SDK for advertising can be present in both. The sandboxing does exist in OS. And you clearly loose control over the App when the website is taken down while you can still use the native app. If native platform remove support for USB or BLE, your web browser cannot use it either so no USB/BLE at all. Users can choose but native is a lot better for privacy and security if the OS and the app are chosen correctly.

It bas been and that's why Firefox refused to implement it. It's good that this is done with a plugin as it is not on by default as mist people do not understand the risks. Making it more difficult offers a bit more protection for most people. Google is known for launching stuff in the webbrowser without thought from a security and privacy standpoint. They are business oriented, not privacy oriented.

Using multiple vehicles also increase maintenance. It totally makes sense to use the right tool. You might not want to learn how to use a screw driver instead of a hammer but both have their use.

Most people do not understand any of the authorizations they give to apps and don't want to have to understand it. They will be interested in it only after they got burned. They just want a thing that "works and do x, y and z" without having to worry about it. I think the problem is that big corp got them used to easy security because nobody cared before but now that security is getting harder, big corp has no choice but to gave a sense of security they promised but cannot give anymore.

So you had to learn IPv6 the same way you learned IPv4. The question is: was it harder ? It seems you wanted to know IPv6 without learning it because you thought it would be the same as IPv4. And yes the Free boxes are hard to work with if you don't want to mess with vlan and still have TV services.

On the contrary, I would say that this is a garage you rent on a public space. The internet is open and I can do requests to any server. If you don't want your system to answer me, make sure it does not. If I am in front of an ATM on the public street, it doesn't give me money without authorization. Make sure your server does the same.

If the encryption info is derived from the password it can be done without visual encryption keys for the user. It is the case with Firefox Sync. They have no way to recover the data if you forget the password.

For me, it's wired with any technology that gives power and network over the same wire so that I can forget the thing when setup (no wireless issue and connection problem) and it doesn't stop working because your router is down.

In one branch I could work on something that has some database migrations, and then I can still switch to other branches without having to roll back the migrations.

This is a good use case of git worktree.

I didn't know about git worktrees though! I'm going to read up on this.

Indeed, you will like it.

The only limitation is that you cannot checkout the same branch in multiple worktree.