Key dates from Bluesky - #109
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe event records now include key dates for volunteer applications, hotel bookings, dealers, DJs, and performances. Each entry includes source, timestamp, and confidence metadata. ChangesEvent key-date updates
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: 🔵 Low · up to The change adds event registration, hotel, dealer, DJ, and performance dates. Inaccurate source-post timing metadata could mislead consumers about when information was published, so the change remains low risk but needs owner awareness or follow-up. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1e9a58b to
ee8e23b
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: 945d1596-6970-460e-8f85-b0680ea8f831
📒 Files selected for processing (1)
michigan-anthro-weekend.json
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.
| "opens": { | ||
| "date": "2026-07-01", | ||
| "source": "https://bsky.app/profile/did:plc:fwt566qqg3uhf36kswpmuqx2/post/3mp25bwxoqs2y", | ||
| "asOf": "2026-06-24T14:37:15.062Z", |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Store the exact source post timestamps in asOf.
The README.md contract defines asOf as the source post's createdAt. The linked posts report 2026-06-24T14:37:19.664Z, 2026-05-26T18:27:12.570Z, and 2026-06-23T16:06:09.472Z, but this file stores earlier timestamps: 14:37:15.062Z, 18:27:10.300Z, and 16:06:05.974Z. (bsky.app)
Update all three asOf values to the exact createdAt values.
Also applies to: 34-34, 42-42
17c0246 to
a4b789d
Compare
a4b789d to
ff2eb0d
Compare
Key dates from Bluesky
Extract:
openai/gpt-oss-20b· Verify (unanimous):openai/gpt-oss-120b+openai/gpt-oss-20b· 2026-09-12Applied (unanimously verified —
/reject <event> <category>.<kind>to drop a bad entry for good)capital-fur-con.json —
capital-fur-con-2027panels.opens → 2026-08-02 (add, conf 0.9)japan-meeting-of-furries.json —
japan-meeting-of-furries-2027volunteers.opens → 2026-09-12 (add, conf 0.9)michigan-anthro-weekend.json —
michigan-anthro-weekend-2026hotel.opens → 2026-07-01 (add, conf 1.0)michigan-anthro-weekend.json —
michigan-anthro-weekend-2026djs.closes → 2026-06-30 (add, conf 1.0)michigan-anthro-weekend.json —
michigan-anthro-weekend-2026dealers.closes → 2026-06-01 (add, conf 1.0)fluufff.json —
fluufff-2026performances.closes → 2026-11-01 (add, conf 0.95)pawsome.json —
pawsome-2026registration.closes → 2026-08-22 (add, conf 1)pawsome.json —
pawsome-2026volunteers.closes → 2026-08-07 (add, conf 1)furry-migration.json —
furry-migration-2026registration.closes → 2026-08-10 (add, conf 1)furry-migration.json —
furry-migration-2026hotel.closes → 2026-08-20 (add, conf 1)furry-migration.json —
furry-migration-2026performances.closes → 2026-08-28 (add, conf 1)furnal-equinox.json —
furnal-equinox-2027panels.closes → 2026-10-24 (add, conf 0.9)furnal-equinox.json —
furnal-equinox-2027dealers.closes → 2026-07-15 (add, conf 0.9)Refuted by verification (not applied)
capital-fur-con-2027hotel.opens 2026-08-25 — The post says "THIS WEDNESDAY" relative to the post date (2026-08-25, a Tuesday), indicating the hotel room block opens on 2026-08-26, not the claimed 2026-08-2capital-fur-con-2027dealers.closes 2027-08-31 — The post (2026-08-17) mentions the dealer's den applications close on "August 31st" without specifying a year; the default interpretation is August 31 2026, notcapital-fur-con-2027djs.closes 2027-12-01 — Post on 2026‑07‑14 says "DEADLINE: DEC 1ST" for DJ applications, which logically refers to Dec 1 2026, not the claimed 2027‑12‑01.