Should public-space AR notes expire unless a venue keeps them?

I’m uneasy with user-created AR notes, signs, and virtual objects becoming permanent fixtures in public places. My default would be expiration unless the venue—museum, station, shop, or park—deliberately preserves a layer. A warning that was useful last month can become false; an abandoned announcement can clutter the view; and harassment can remain invisible to people who do not use the same app.

The technical case points the same way. Anchors can persist across sessions and devices, but relocalization depends on recognizing the environment. Renovations, moved furniture, or weak matching can leave an object misplaced or out of sync. Expiration limits stale content and reduces the moderation and retention burden, though it will not stop screenshots or deliberate reposting.

The hard question is authority: who owns a location layer, who can remove it, and who gets an appeal? Should venues have the final say, or merely one voice?

Expiration is sensible, but “venue preserves it” needs a real protocol, not a checkbox. You need ownership, leases, deletion semantics, and a way to tell clients that an anchor was intentionally retired rather than merely unreachable. Otherwise old cached content becomes the undead layer of the system.

I like the default because it makes persistence feel earned. A venue choosing to keep a layer is a social signal: this belongs here, at least for now. Anonymous users silently claiming walls and doorways creates a norm before anyone has agreed to it.

I would not call expiration a harassment fix. A hostile note can be re-uploaded every week, mirrored across accounts, or shown only to a targeted group. The useful property is reducing the lifespan of one artifact, not preventing abuse. Identity, reporting, and access controls still matter.

There’s a product problem too: people hate losing useful context. If every local recommendation disappears, users may stop contributing. I’d make short-lived content the default, then let venues or trusted community moderators renew it with a visible “last reviewed” date.

The brief distinction matters here: persistent anchors are feasible, but that does not establish any general rule about who controls public-place content. I’d be cautious about presenting venue authority as settled. It is a governance choice that still needs to be designed and justified.

A sign that expires is just a notification. A sign that survives needs maintenance. We already know what happens when nobody is assigned maintenance.

Please include deletion for the creator, the venue, and the platform, with an audit trail that does not expose everyone who viewed the object. “Gone” should mean gone from active resolution, not necessarily erased from every backup—but the retention policy should be explicit.

Venue preservation could work without making one company the landlord of reality. Store a signed object with an expiry, let clients verify the venue’s authorization, and keep the basic metadata portable. Offline clients still need a safe rule when they cannot check revocation.

I’m not convinced venues should automatically get final say. A public transit agency might preserve official notices while suppressing criticism. Expiration by default is good, but preservation should perhaps require transparent ownership and an appeal process rather than simple institutional privilege.

The operational detail I’d want is a visible review date, not just a hidden TTL. Staff need a queue for renewals, removals, and disputes. Otherwise “preserved” becomes permanent by neglect, which is exactly the failure mode expiration was meant to avoid.