• 0 Posts
  • 95 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle


  • That basic idea is roughly how compression works in general. Think zip, tar, etc. files. Identify snippets of highly used byte sequences and create a “map of where each sequence is used. These methods work great on simple types of data like text files where there’s a lot of repetition. Photos have a lot more randomness and tend not to compress as well. At least not so simply.

    You could apply the same methods to multiple image files but I think you’ll run into the same challenge. They won’t compress very well. So you’d have to come up with a more nuanced strategy. It’s a fascinating idea that’s worth exploring. But you’re definitely in the realm of advanced algorithms, file formats, and storage devices.

    That’s apparently my long response for “the other responses are right”


  • I looked into proton pass ~9 months ago and it just wasn’t ready. Needed a few more features before I was willing to move from Bitwarden. However, I gave it another look 2 weeks ago and proton pass satisfied all of my needs. Since I was already paying for proton unlimited, it just made sense for me to change. And it’s been a perfectly good experience so far! A couple of thoughts:

    While I do run Linux, I don’t need a native app for it. I exclusively use a browser extension on my desktop. It does everything that I need. I do use a native app on IOS and it works quite well.

    The 2fa in proton is pretty good now, which I needed. It can also store other types of data like credit cards, identities, etc. But it’s not quite as good at identifying fields for auto fill. Pretty close though so I’m not bothered by this.

    My biggest ”complaint” is protecting my proton account. I use it for email, storage, etc. so I can’t accept a weak password for it. But I also need to have reliable access to other passwords stored in proton pass. For this, I want something long yet memorable and easy enough to type out. These two requirements are roughly at odds with each other.

    My solution for now is to keep my Bitwarden account and use it as a source to recover my proton account when necessary. I think it’s a good pattern actually and I may expand this in the future with methods like syncing data between the two tools.



  • Interesting feature but I’m a little disappointed that this is a feature for business accounts only. I have a Duo account; are there any features that would allow me to share certain emails with my wife? For example, it would be great if we could both receive the exact same emails related to our credit card statements. Or car loan. Or electric bill. Etc.

    Anyone have tips?



  • I only have anecdotal info for based on some reading I did last year. As far as I recall, the program and software are new. So they’re slowly building up features for more complicated tax scenarios an in turn, slowly making it accessible to more of the population.

    It’s just a matter of time before this is widely available. I read the post title as “we succeeded in this first year’s test and plan to continue the program”.













  • Ok that is an impressive number but it feels a little disingenuous. You still need to something on your machine to interpret the js code, right? Is that included in the 13k? How much storage does that take?

    EDIT: Well this is by far my most negative comment here. That’s almost entertaining. I’ll share a few more of my thoughts here rather than respond to individual comments. Maybe the context will make this more palatable.

    First, I expect that the js language is doing most of the work here. Which makes sense. But having a browser installed as a prerequisite is an enormous dependency.

    How would that stack up against other languages? Can I build a 13k binary using C? How about C#? I think Go is maybe the most interesting because the binary is entirely self contained by default. No external dependencies aside from the OS. I don’t think this or a similar game is viable with only 13k. Which is fine! I just that I find 13k is disingenuous.

    That brings up the question of whether or not we should include the OS in the storage size. I would think not. But that’s only because the OS is (usually) the least common denominator when we talk about developing software. It’s generally assumed by default. But if someone wants to compare with a game that interfaces with hardware directly, then yes, we should absolutely include the OS as a dependency.

    Now that I’m giving this more thought, I suspect that the devs wrote 13k of code + assets to make the game functional. Still impressive. But the more I think about this, the more meaningless that number gets. Does pre or post compiling matter more? What if we compress the thing as tarball? There’s just too many ways to manipulate this number.