2 Commits

Include renames

Author	SHA1	Message	Date
thepraandClaude Opus 5.5	6f240828cf	A located post reaches no home, its author's included ... The fan-out put every post in its author's home, located ones too, while the Mastodon API looks past located posts everywhere else. In the author's home a located post showed as public (the mapper has no word for it) and every action on it answered 404: decePub's end-to-end runs, which write one from Milano for the globe, found it there. The fan-out now gives a located post no home, no stream and no notification, and the home timeline passes over the entries left from before. A located post is read through /clientapi/post/nearby and deleted through /clientapi/post/delete. NearbyTests checks it has no TimelineEntry; the suite passes (881). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw	2026-10-07 02:14:16 +02:00
thepraandClaude Opus 5.5	c00865d805	Located posts: local only, rounded, matched against their own radius ... A post given a latitude and longitude becomes LocalGeo: its position is rounded to two decimals (about a kilometre) and stored as a 2dsphere point, its radius clamped to 1-50 km, and it is local only - no Create, no delivery, no outbox, never in the Mastodon API or on a profile page. /clientapi/post/nearby takes the viewer's position for the query only (it is neither stored nor logged), runs $geoNear and keeps posts within each post's own radius, minus authors the viewer blocks or mutes. A located post cannot be direct or in a group. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB	2026-10-01 12:24:30 +02:00