How is creating or operating a community “painting a bullseye” ?

And tbh now more than ever I think it’s important for communities like this to exist.

Interpreting Animats' question as concern for the user population, I think it's a valid one.

The new administration in the US is openly hostile, and a lot of damage could be done to peoples' lives if, say, the community was hacked and private email addresses (or other PII) was leaked.

And I also agree with you -- now's the time for those of us who can afford it, to fly our ally flags as loudly and proudly as possible.

OP: Please make sure your secure coding and operational security practices are excellent and meet the challenge here.

> if, say, the community was hacked and private email addresses (or other PII) was leaked.

Or just basic ISP, or other provider, logging domains visited per user.

Threat model this shit.

I would dead man switch the storage's Azure instance. Mayybe the whole thing. Mayybe shouldn't be on azure.

Nm assumed RLS as a MS TLA. PGsql has it as well. Comment stands, watch data residency.

5 mile range is pretty serious, it narrows someones locations down to a single town in the entire world. Just dont store it at all and you're all good.

You'd need just a little more data to find the individual.

Why even keep location data at all?

One of the main selling points of the app is that you can filter posts by distance, to facilitate people meeting and talking with their community.

So list a city?

I'm wondering if it's more or less safe (from doxxers attacking individual users, or the entire service being compromised) to share location with this app vs. Lex. In any case I chose not to share location yet, and don't know if Lex is any safer (they require location).

email me if you need a code review

Without wishing to appear overly snippy, this is how I would begin hacking such a site.

Offer to do a "code review".

"Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith."

https://news.ycombinator.com/newsguidelines.html

I got an offer of a "code review" like that once for an authentication system and never heard back; it was open source anyway so anybody could have downloaded it and found my rookie mistakes like

  signed_token = content + MD5(secret_key+content)

which doesn't stop anyone from appending to the content (might not have really been exploitable, but any honest review from somebody who knew more than me would have turned it up)