dngit

> if you need that level of documentation, trying to shoehorn it into package.json is just the wrong place for it. Soon enough your package.json looks like a graffiti wall.

So the right place is to make a graffiti out of another place, instead of in the place where people actually declare the dependencies?

I find it bizarre when people believe in one true way of doing things. I mean, you can declare your dependencies how you like, but if others do it differently, then they're clueless?

I would argue that the gain is more than "negligible" in some cases. I'm building an app involving storing and serving images and I'm surprised that for the same images with the same resolution/quality, WebP is often 3x-4x smaller than PNG, which translates to lower storage cost, faster serving time, and happier users. You made a good point that people with older devices wouldn't be able to use apps like mine. But for me, the gain is so significant that I might just accept that.

Would an app like this work with TV? Would be super cool if it would.

Care to expand? Is it alternative to magic link / OAuth?

Ah, sorry, I didn't notice the website itself was that old.

Now, it's been a very long time since I see a mention of "Internet Explore 5". Kudos for highlighting the support for it but does it matter, who in the world are still using Internet Explorer 5?

Wish all browsers, at least the big ones, would do this by default. It would save regular users like us from fumbling around trying to figure out what works.

Tor's great if you're okay with browsing the web at "stealth mode" speed! Have you found it practical for everyday use?

Thanks. I'm a bit confused by this tool. I ran and got this result

> Our tests indicate that you have strong protection against Web tracking.

Which sounds like a good thing. Then it follows with:

> Your browser has a nearly-unique fingerprint

This sounds like a bad thing to me because uniqueness makes me more identifiable. Do I interpret it correctly? What's the value I should look for?

Great point on focusing on high-impact tests. I agree that LLMs risk giving a false sense of coverage. Maybe a smart strategy is generating boilerplate tests while we focus on custom edge cases.

Are there any browser extensions or tools that effectively prevent fingerprinting including canvas fingerprinting? Or is this one of those privacy battles we just have to accept as unwinnable?

Sounds like you're living the dream! I definitely agree that a few months of safety net doesn't feel "safe" at all and 1-2 years is more reasonable. One question, how did you initially start building that network of clients to reach a point where word of mouth sustains the business?

Thanks for sharing your journey, it's very inspiring. I'm curious, how did you find your first enterprise clients, and what strategies helped you secure long-term projects? Any advice for building that initial trust as a solo consultant?