restructure Nightscout is free discussion #149
Conversation
Again try to clarify and deescalate language used. This change makes explicit what is free and the ways in which it may not represent the free experience implied otherwise. Nightscout developers cannot control the price of third party servers. We can't make this cliam.
|
This lays out examples for how to discuss "what is free" without accusing participants of harming the ecosystem, and without confusing people expecting a year of free mission-critical application support for Loop. This offers a useful starting place to add fly.io and railway, as discusssed in #147 |
There was a problem hiding this comment.
I liked @sulkaharo comments and James's post as background data regarding this, and this is why I added them, but if you don't, no problem. Let's remove the background discussion from this documentation.
These do not change the developer recommendations or best practices.
This is more accurate as most DIY methods are for payment as well. The main difference is dedicated Nightscout as a service rather than pay vs not-pay for servers.
Add links to the vendors, as this will help others know where to participate.
|
Ok, they are removed from the front page with a bit more nuanced discussion, and updated with the latest information I could find. Also, all the vendors with some form of a stub page are linked. I think this will help people see where they can make a difference and participate. |
Again try to clarify and deescalate language used. This change makes explicit
what is free and the ways in which it may not represent the free experience
implied otherwise.
Nightscout developers cannot control the price of third party servers. We
can't make this claim and have never supported it. We are now being held responsible for making it true even though it's not feasible.