deif
The summaries of all these studies can effectively be summarised as: if you are raising children on a vegan diet, ensure you supplement and have adequate calory intake. Taking datapoints from figures and graphs without understanding the underlying causes and effects is how we spread misinformation. It's great that studies are measuring this so that we understand better how humans can develop successfully.
An example of this is in study 6 where you stated that vegan children were shorter and weighed less. Whilst true the study also stated "The energy intake of the vegan children was consistently lower than the recommended daily amounts". It then concluded that with a sensibly planned diet vegan children should have no intellectual or physical problems in their development.
So whilst I agree that all the studies did find differences, I disagree that they are somehow proving against my points that a vegan diet in children can be healthy if correctly planned. Due to how the animal agriculture industry creates meat (such as supplementing and fortifying the meat) it is extremely easy to get away with not planning meals with an omnivorous diet.
* https://www.mdpi.com/2072-6643/11/4/832/htm
* https://link.springer.com/article/10.1007/s00394-021-02753-3
* https://www.mdpi.com/2072-6643/13/5/1707/htm
* https://academic.oup.com/ajcn/article/113/6/1565/6178918
* https://anthropogoniquescom.files.wordpress.com/2019/08/grow...
* https://anthropogoniquescom.files.wordpress.com/2019/08/grow...
* https://onlinelibrary.wiley.com/doi/abs/10.1111/j.1365-277X....
* https://www.minervamedica.it/en/journals/minerva-pediatrics/...
* https://www.embopress.org/doi/full/10.15252/emmm.202013492
All concluded that vegan diets were healthy for children as long as the parents knew the common deficiencies (B12) and fed their children enough calories. The study you cited is on my list because it seems you didn't read the results where it stated that most children were not eating fortified or supplemented food like Vitamin D, which could easily explain why they have a lower bone density.
1. Spending so much time trying to get the project to stop what they were doing.
2. Peacefully come to a mutually beneficial arrangement.
3. Front page HN where I will most certainly be avoiding using any project the author is part of.
At it's core cryptocurrency is a way to bypass banks if one was so inclined. Specifically currencies like Monero allow a person to send and receive payments completely anonymously, hence its increased usage on darknet markets.
I still consider it quite extortionate however considering app devs are adding to the ecosystem and potentially driving sales.
'This is confusing, non-standard, and creates additional complexity'. Is it confusing and adding complexity? All you have to do is look down the list for what you want, it's hardly complex. It's not as if they're naming methods 'obtainChat', 'getUser', 'retrieveLogs', etc.
Which leaves the documentation on the website, which I find quite easy to follow. But let's say it is confusing and it's not as good as it should be. Does that mean the platform is dying? I didn't realise that designing an API to not use all HTTP verbs was such a big deal.
For data storage independent billing, go to Settings -> Dashboard. On Professional tier and above the data storage is a dropdown where you can increase the amount required.
For email filtering go to Settings -> Filters and create as many conditions as you want on a filter.
Apple would only approve the app if I integrated it into the existing app but not with the 2048 game because the name wouldn't match the functionality and a dead man switch app called 2048 doesn't make sense for the majority of users. You seem to be missing the fact that this app already exists with a current set of users already. Calling it Glorp Zonker Pro is not exactly relevant to them.
Thank you for your concern though.
As with any service you should assume that nothing is encrypted (even though it is) and follow other articles that I've written about how to securely maintain private information when using third party services.
If you can believe it originally this was a 2048 game (see the android version) but Apple suggested they would only approve the app if it was a hang man game and I named it 'Dead Man'. I wish I were joking. You have to understand that this functionality did not exist before today and my target audience previously were travellers, students, journalists, and privacy conscious people so I'm stuck trying to be relevant to multiple sets of audiences and a technical term that has 'dead' and 'man' in the name.
As I wrote in the article, the ideal scenario was that I had two separate apps where it has a completely different name, but due to Apple restrictions I was forced to name it Dead Man (actually suggested by Apple themselves when I spoke to them over the phone discussing this issue) as the name has to cover both parts of the functionality even though the target audiences are completely different.
But this is not really going to be used by abuse victims of their own accord, it's more likely to be picked up by charities that need to set up a robust support network. It's a fine balance of SEO, networking, naming relevance, and sensitivity that I am tuned into.
The problem is that even though this support network exists, victims often have their phones taken away from their abusers so they end up stuck. If friends and family go round to the house, their abusers can refuse entry and say that the victim is fine or sleeping when in fact they're in danger. This app does not intend to phone authorities, it is down to the individual support network to organise that as they see fit, this app only intends to reach out to the support network as fast as possible when it is needed. If there is a true emergency and they can call emergency services then they can do so, emergency services are set up to handle this. In the case that the victims only want to notify their support network then they can do so from the app using the panic button.
It might be the case in the future that I build contacts with emergency services for a more involved response but I simply do not have the contacts at this point in time.
In terms of redundancy and failover, barring a total region blackout on the AWS end, the remote service will continue to function forever due to the way I've set up the infrastructure. If I die then the service will simply be handed over to someone else.
More visibility is definitely key, and charities are already stretched so it's not like they have the resources to get this kind of thing done for them. I've been reaching out to various charities to open a channel of communication to let them know that this is available for them.
Apple are extremely restrictive on how you present your apps, so it will always be obvious what the app is from the listing (which is why I specifically had to use hang man, as the name of the app has to match the general functionality). I couldn't even release a separate app with the same functionality but completely reskinned as they classed it as spam. So I had a problem of only having 1 app and providing functionality to two different sets of users. One set only wants the dead man switch functionality and an initial screen that hides the app is useless to them, and the other set only wants the hidden functionality.
If they were less rigorous in applying their rules then a more secure app could be made and I'm always open to suggestions. This was actually made in conjunction with liasing with a US charity for domestic abuse as it was a feature they specifically asked for.