Kasra from CapRover. Feel free to open a Feature Request on Github. There is no architectural design limitation that prevents this. It can certainly be added.
On top of all security measures, Meta, Google and other big tech that offer Auth-as-a-service need to offer paid service to reclaim an account. I am sure people would be happy to pay to talk to a real human and take back their account.
Kasra here from CapRover.
Regarding "netdata image":
- sneak and I have fundamental differences in what we call spyware. The issue that was brought up in that thread is standard analytics events - nothing like stealing passwords or etc.
- Regardless, CapRover uses NetData 1.8 [1] . According to NetData's github page, they added analytics in NetData 1.12 [2] , so even if you're concern with analytics events, this issue won't apply to you anymore.
Regarding two factor auth:
CapRover blocks brute-force attacks by limiting number of wrong passwords per minute.
Thanks Kasra, yes it seemed 'spyware' was disputed and I didn't want to jump to any conclusions. But it's good to know it's a non issue.
RE: 2fa. Brute force protection is a step in the right direction, but passwords can leak in various ways, brute force isn't the only attack vector. I'll comment in the actual two factor auth discussion on the CapRover GitHub issue though.
It's easier because for many cases you don't even need to search the document ro know what command to run to fire up a database. You just select it from a GUI list.
Agreed. There is a lot of params that are not included in this simple model. As for Healthcare System Capacity and hospitalization and mortality rate, since these are all flat multipliers, I haven't included them in the model. The point of the Healthcare Capacity is just a flat line in the system. 25% is a fair capacity when you consider the hospitalization rate of 10-15%.
All other parameters included in the model have much more complex effect on the growth rate.
In https://medium.com/@joschabach/flattening-the-curve-is-a-dea... the estimation is that the number of ventilators is only a 2% of the total of the population that will need them. So the curved need to be flattened even more. (I don't know if that is really the limiting factor of the attention.)
The numbers of the days in the x axis follow a strange pattern. What about using the multiples of 5 or 7?
If I change the number of "Random People Met Daily" to 1, the peak of the curve is outside the range of the graph. I guess the scale should be configurable.
The number in the "Close Circle Size" is used to simulate small clusters, or each day it is used to pick someone at random from the population? (Does each sim has it's "family"?)
With regards to the need for flattening even more, I totally agree. But I think you are under the impression that the y axis in this model can simulate the real world. That's not the case. This is a "super simplified model" to show the effect of simple changes - relative to other scenarios, not necessary being an absolute measure.
The close circle size is the family/close friend size. In actual scientific models, this is a decimal value to represent the average of the community, but in this model, I kept it as a whole number to simplify my calculations. If I get a chance, I'll improve this further.
Anything that falls into more than 150 days is way beyond any sane model can predict. Cutting the "Random Contact" to 1 greatly drops the rate for at least 150 days - this is exactly the point of this model on showing how important it is to reduce social interactions.
I just noticed that the simulation does not have a field for the total size of the population. The initial state is 5 sick people in a population of 5000.
The initial grow is exponential until the logistic part of the curve kicks in. The current grow is something like 25% daily, so a x10 in the population is a delay of the peak of 3 days or something like that. It would be more days if we flatten the curve. (With the initial values in your simulation, the peak is at 60 days. For a big city with 1 million people, the delay is like 2 weeks.)
It's clear that this is a very simplified model, but they are useful to get a feeling of how the parameters affect the epidemy.
Author here. Just to be clear, this is false information. It's a toxic thread.
1)
The author of that thread is calling a software with analytics a spyware. By that definition, any website you use, including this very website you left a comment on, is spyware.
2)
NetData is built-in, but it's not enabled by default. Use is free to install/ or not to install the package.
Silent surveillance, which is not disclosed to the user. Additionally, the user's IP (and thus location) is also provided to Google with the surveillance data.
Webpages and local software are not the same thing. Local software does not need to report my activity to Google, a third party, to work. Webpages do require second party communication to function.
Surely you realize the difference. Your attempt to conflate the two is not productive.
If you believe they're the same thing, let's call it "analytics" then, exactly what it is. Let's avoid using the terms like spyware or etc which is an umbrella term which covers very serious damages such as stealing your bank info.
Getting Started section is aimed for beginners. You surely don't have to disable firewalls entirely. There's a section in the docs outlining the ports that are being used by Captain.
