u/MattCW1701

I was in the Bluewater Marsh at night and found the houseboat. I was on it when I saw a red dot on my map moving quickly. I grabbed my shotgun and jumped to shore, but it was gone, and I couldn't find an alligator that would have made it. I got on my horse and circled for a bit and it appeared again and I chased it down and still found nothing, not even a snake trail. Any idea what it was? I was hoping it was a night folk, but they never appeared, it actually moved too fast for an alligator. The ghost lady appears as a white dot not red so not her. Any ideas?

I received a rejection reason from Apple under guideline 5.1.1(iv). Currently, my app is location-gated to the United States since I do not yet want to spend the effort to try and comply with regulations in other countries (The app is ad-supported with a premium no-ads version, and includes some basic analytics including coarse [two-decimal place lat/lon] user location). So if the user denies location information, they are given a message explaining why and they can either exit, or go to the settings screen to request location access. I responded to Apple requesting clarification from them and I'm waiting. Does anyone have any guidance/experience for this? Is it enough to rely on the App Store's location-gating? The scenario I'm trying to avoid is a U.S. user downloading the app, then going to the UK and thus the app would be required to meet UK regulations.

Periodically, my base unit seems to lose WiFi connection. When it does, it starts chirping, like a smoke detector, and will do this for hours. There's no notification on the app so when I'm out, I have no idea this is going on. I have cats and they hate this noise. When I get back, there's nothing I can do to stop it myself, it reports good signal, and doing the communication test doesn't fix it. So I call support, give them the technician code and they fiddle with it and shut the noise off. This happens about once a month now. Finally they sent a tech out and all he did was tell me that I had to have an ADT-only 2.4GHz WiFi network. My current WiFi setup has both 2.4GHz and 5GHz with the same SSID. The tech was saying that I should change the 2.4GHz SSID and attach the base to that one. That doesn't seem right. Has anyone else had to do something like this?

I'm asking mostly from the U.S. perspective, but would evidence of crimes in country A, that is acquired in country B, be admissible in country A? To be more concrete, someone commits a murder in the U.S. and flies to the UK. The UK police do a search of their phone (not necessarily at the border) and find evidence that they committed the crime in the U.S. Could the UK police just send that evidence to the U.S. and it be admissible? What about another country? Especially if that country were a little looser on what constitutes "civil rights." I don't think I'm specifically asking about extradition, that usually requires initiation by the extraditing country.

I didn't see another place to ask about the site. I'm using the paid service online, I must have submitted before my app was fully approved by Google, I got a notification to update the link. I did and sent the email, but then I got a return email from support asking me to enable all countries. However the app I need tested is U.S. only, that's how it will be in Google Play (and later Apple). Do I just set all countries and include U.S. only in the instructions? Even in-app, someone that tries to use it in another country will get a notification that it doesn't work there (which could be part of the testing I guess). Has anyone else run into something like this before? Thank you!

I've started using DigitalOcean as the backend for a mobile app and I'm starting to see some limitations that seem to be put in place to prevent system abuse. In my architecture, I have one main serving droplet, and about once a week I intend to spin up a more capable droplet, have it do some work, and upload the product of that work to the serving droplet, then destroy it. It seems like create->run->destroy would be exactly the kind of process I'd expect DO to protect against. I know there are limits on the total number of droplets so it is mitigated somewhat. I'm just worried about running into a limit on the frequency of droplet creation at some point since this process is integral to my app's functioning. Has anyone run into anything like this?