Nit: Self-diagnosis is the first step towards a formal diagnosis. You don't go to the doctor to get antibiotics before self-diagnosing that you're sick.
That said, as useful as a formal diagnosis is (getting proper help, and even meds), don't skip it if you can afford to do it.
> The same logic holds for things like recurring subscriptions or ad-supported content - much smaller amounts, but many more sources, adding up to mitigate this problem.
And at some point your customers are saturated. How many subscriptions before they can't afford another subscription? After all, if they're subscribed to the max, it's not as if their budget will have room for another one next month, or even next year. It's fully allocated, and will likely remain so.
Here's the problem with that - there's not enough room for every company and their subscription model. So where you have a chance to get money from someone with a one time purchase, you're going to have to fight to get another piece of their subscription budget.
And more and more - you're not going get that piece.
Customers only have so much money and so much time. Expecting them to make a long term commitment is going to be a worse and worse business model in the coming years.
1password - the non-SAAS version - works a charm on my phone. I haven't needed an update. And aside from compiling for newer phone versions, I haven't noticed an update.
Except on the desktop which was updated to be crippled (can't edit items) and it advertises for the SAAS version with every other click. Which, fuck them. Their move to SAAS has done nothing but corrupt what was a good software company.
> it is hard to know when to try to get help, or whether you are just seeing what you want to see and looking for an excuse
And that's why you see a professional. If you don't, you'll never know. It's hard, it's embarrassing, and ultimately, it can be redeeming to know that no, you're not just lazy.
Respectfully, this doesn't change the advice. Always assume the network is compromised - that someone who shouldn't has access your hosts via the network. A user's device is taken, a new user is added via social engineering, a computer is left unlocked, a host is compromised...
First - congratulations! I like the idea behind your product. Easily configured VPN tunnels are something I enjoy having.
But, and I'm probably just shouting into the void at this point, relying upon your network being secured as a method of securing your office/product will only result in heartache.
If you're a company SEO or similar trying to protect your company from threats, your first assumption must be "the network is compromised" no matter whether it's on the internet, or VPN tunnels, or firewalled local network.
To add on to every other sibling comment, switching threads or processes requires a trip back up to the kernel space (a context switch), instead of just remaining in user space. in this switch, all of your caches get busted.
Not a problem for most folks, but when you want the greatest possible performance, you want to avoid these kinds of transitions. Basically, the same reason some folks use user-space networking stacks.
Per research tests which look at load times and abandonment, under 1 second has the same retention as instant. So, AMP provides no practical benefits here.
> How [is AMP problematic]?
A large number of electrons have been spilled on this topic. I recommend reading one of those. It really comes across as an attempt to argue in bad faith by ignoring these well-distributed (especially on HN) concerns; even worse to try and paint RSS and similar as harmful.
I would disagree, given how the major sports franchise games and multiplayer FPS games use gacha mechanics too.