This may not be the best advice, but it is what I did for a project that was required to have these statements. There are online templates and services that will create and host your terms and data privacy policy for free, with upgrades of you want more customized wording. The format is clunky and in my case allowed for more data collection than the app would ever actually do because I did not pay to customize it, but it serves the purpose. Termsfeed.com privacypolicygenerator.com You could just generate one to see the general idea and then customize it yourself if you don’t need the hosting.

Used to be considered simply prudent to back up the vhs tapes you bought and people were encouraged to tape their favorite shows off the tv. Now some random CEO of the month has the right to bury decades worth of creative works?

Yeah, I hadn’t heard of it, but it looks really cool. Gonna have to try that out.

I use osmand on Android. Bit of a leaning curve to start as you need to download the maps you want and set up features, but then it is available offline as well and can include topographical and trails or other data if you’re not just traveling in cities.

Oh. I don’t know anything about this. Is it weird for an app to be pulled from all of these sites? Do they have a way for the original developer to take it down if they want or some kind of flagging? Does your new phone have a higher Android build, maybe the site checks somehow to match with the right version and then fails? Wild guesses

https://apkgamezona.com/everyday-wallpaper-pro-ad-free.html

But the fact that so many stores have dropped it recently, though it’s clear they once had it, may mean something, idk.

Thanks, I understand the problem with using memory after it’s been freed and possibly access it changed by another part of the process. I guess I was confused by the double free explanation I read, which didn’t really say how it could be exploited, but I think you are right it still needs to be accessed later by the original program, which would not happen in Rust.

Thank you, that is very clear.

The way I understand it, it is a bug in C implementation of free() that causes it to do something weird when you call it twice on the same memory. Maybe In Rust you can never call free twice, so you would never come across this bug. But, also Rust probably doesn’t have the same bug.

My point is it seems it is a bug in the underlying implementation of free(), not to be caught by the compiler, and can’t Rust have such errors no matter its superior design?

They should have one for heterosexuality, too, if it’s all about tastes.