Difference between revisions of "Bricodash/Future"

From Hack Manhattan Wiki
Jump to: navigation, search
(Current Tasks Outstanding)
(Current Tasks Outstanding)
(One intermediate revision by the same user not shown)
Line 6: Line 6:
 
<onlyinclude>
 
<onlyinclude>
 
* calendars (short term)
 
* calendars (short term)
 +
** castles: icalevents: <code>ValueError: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware</code>
 
** correctly calculate date of International Astronomy Day (email out to Astronomical League for better calculation rules)
 
** correctly calculate date of International Astronomy Day (email out to Astronomical League for better calculation rules)
 
** confirm names on shared birthdays are randomized
 
** confirm names on shared birthdays are randomized
 
* reliability
 
* reliability
 +
** add decoration to indicate when a post is from a thread rather than from main channel
 
** add a webhook to ping #netops when camera feed is down
 
** add a webhook to ping #netops when camera feed is down
 
** enable SSL for camera feeds (requested for full conversion to new sous veil system)
 
** enable SSL for camera feeds (requested for full conversion to new sous veil system)
Line 30: Line 32:
 
** refactor source files from initial launch
 
** refactor source files from initial launch
 
** squish and push fork to upstream
 
** squish and push fork to upstream
** migrate bricolage to less power-hungry hardware</onlyinclude>
+
** migrate from bricolage to less power-hungry hardware
 +
** reimplement bricolage to run as embedded system under elixir/scenic/nerves</onlyinclude>
  
 
== Instagram Integration ==
 
== Instagram Integration ==

Revision as of 02:49, 14 June 2019

See: Bricodash for project details

Current Tasks Outstanding

  • calendars (short term)
    • castles: icalevents: ValueError: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware
    • correctly calculate date of International Astronomy Day (email out to Astronomical League for better calculation rules)
    • confirm names on shared birthdays are randomized
  • reliability
    • add decoration to indicate when a post is from a thread rather than from main channel
    • add a webhook to ping #netops when camera feed is down
    • enable SSL for camera feeds (requested for full conversion to new sous veil system)
    • find new sweet spot for camera throttling given new network conditions
    • replace failing microSD on pishop (and restart daily cron reboot)
    • add route to trigger a pishop browser cache flush
  • documentation
    • flesh out Bricodash Future Ideas, explaining known requirements for each
    • redraft lists in calendar sections as tables
  • cloud log
    • add boxrs-based git repositories to Cloud Log panel
    • add remaining sources to HM Cloud Log panel
  • calendars
    • refactor brite search by location routine to common library
    • add nyc resistor, fat cat fab lab, and makerbar to Community Calendar
    • finish fleshing out remainder of movable feasts for Community Calendar
    • enable toggling between Welcome header and holiday greetings ^
    • discard low priority "Holiday" events when today is overcrowded
  • cleanup
    • integrate citymapper API for local subway stations
    • refactor source files from initial launch
    • squish and push fork to upstream
    • migrate from bricolage to less power-hungry hardware
    • reimplement bricolage to run as embedded system under elixir/scenic/nerves

Instagram Integration

  • add Instagram to Weird Photos and HM Cloud Log — this requires creating pages on Facebook under the new Graph API

Twitter Integration

  • 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

Draft a Privacy Policy

  • draft privacy policy (per API reqs for public sites)

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