Yeah, it's made more for refining and confirming details than for adding entirely new objects.

When I want to add something that's not on the map yet, I either add a note in StreetComplete and come back to it later on my computer, or I add it using Vespucci. (I've been known to add items using Vespucci, then reload the data on StreetComplete so I can fill in details that aren't in the presets and that I can't remember how to tag manually!)

By that logic, there's no point in ever deleting anything online, so why even bother with hiding them? Just leave everything up there forever, whether the person who wrote it still wants it to be there or not.

Also, not everyone has the time, programming skills and resources to just fork a project, never mind run their own server. That's not a constructive approach to a "this feature ought to work better" discussion.

Mastodon has the same fatal flaw. They want to keep your history and relationships hostage so you can’t leave.

You can migrate your relationships to a new Mastodon server.

And while you can't directly transfer the history (the debate over how/whether to do this has gone on for literally years), you can export an archive you can keep locally, and there are tools out there to parse it and convert it to some other form (static website, whatever). Someone's probably written an importer by now, though I'd have to look.

The fact that other copies might be out there (assuming a crawler archived the particular page while a post was up) isn't a reason not to remove the copies you can control.

#Bookwyrm is a book review site like Goodreads

#WriteFreely is a blogging service, and Medium is actually working on Fediverse integration.

Even just caching the not-logged-in views can be a big help, as I've found with self-hosted WordPress.