See: Bricodash for project details
Current Tasks Outstanding
- flesh out Bricodash Future Ideas, explaining known requirements for each
- confirm #thehaps bot knows about Friday Live Music default event
- redraft lists in calendar sections with tables
- add remaining sources to HM Cloud Log panel
- finish fleshing out remainder of movable feasts for Community Calendar
- enable toggling between Welcome header and holiday greetings ^
- refactor source files from initial launch
- squish and push upstream
Building Calendar Deduplication
Eventbrite events for Offside Tavern are sometimes listed on Meetup, under slightly different names, not always with the same start time. The recurring Friday Live Music event, meanwhile, very rarely also gets listed on Eventbrite, again with variations on the event name. The result is that the same event can be listed twice on the Building Calendar, which consumes one of few available calendar display lines, two with line wrapping.
A solution would identify duplicate events, and generate a single event listing, taking into account relevant information from variant titles, while incorporating decorations applicable to both listings. Namely, (i) noisy formatting and emoji; (ii) Meetup RSVP count; and (iii) Eventbrite-required URL.
- add Instagram to Weird Photos and HM Cloud Log — this requires creating pages on Facebook under the new Graph API
- add Twitter to Weird Photos and HM Cloud Log — this requires emailing to get a dev account, then honoring Twitter's Display Requirements
Slack Calendar Response Bot
- interactive bot response to "What's happening?"
MJPEG Gateway Server
At some point, the gateway should be migrated to a system service running on its own port.
- rewrite MJPG gateway as a dedicated server on own port
Buzzer-Activated IR Remote
Additionally, there are plans to tie a ceiling-mounted IR remote into the intercom buzzer to toggle inputs on the TV. The idea would be that when the buzzer sounds, the remote would switch from the dashboard (on Chromecast) to a dedicated full screen camera input. After a delay the input would be toggled back to the Chromecast-hosted dashboard. Such an arrangement would free up the dashboard screen real-estate currently devoted to an around-the-clock camera feed—as, realistically, the only time one needs a camera feed is when a visitor is buzzing to be let in.
Alternatively, the buzzer-activated full-screen display of the door camera might be implemented by conveying the door buzzer signal to the back-end server on bricolage, which could then trigger the full-screen effect on the dashboard. However, the potential latency of such a configuration, coupled with processing power limitations of the Chromecast, make this a less attractive option. Well, that, and why do with software what you can do by cannibalizing an old remote control?
- integrate with custom buzzer-activated IR remote hack