Difference between revisions of "Bricodash/Future"

From Hack Manhattan Wiki
Jump to: navigation, search
(Current Tasks Outstanding)
(Current Tasks Outstanding)
(2 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
<onlyinclude>
 
<onlyinclude>
 
* reliability
 
* reliability
** migrate webhook from #bottest to #netops once latency period determined
 
 
** migrate to standard ports (once relayd installed on router)
 
** migrate to standard ports (once relayd installed on router)
** enable SSL for camera feeds (requested for full conversion to new sous veil system)
 
 
** configure X-Forwarded-For logging in apache (pending relayd)
 
** configure X-Forwarded-For logging in apache (pending relayd)
** replace failing microSD on pishop (and restart daily cron reboot)
+
** enable SSL for camera feeds (requested for full conversion to new sous veil system)
 
** add route to trigger a pishop browser cache flush
 
** add route to trigger a pishop browser cache flush
 
* documentation
 
* documentation
** flesh out [[:Bricodash/Future|Bricodash Future Ideas]], explaining known requirements for each
+
** recent edits monitor to trigger cache purge on transcluded Bricodash documentation updates
 +
** help get mediawiki server 504 issues resolved (currently an obstacle to '''Bricodash''' documentation)
 
** redraft lists in [[Bricodash#Event_Calendars|calendar sections]] as tables
 
** redraft lists in [[Bricodash#Event_Calendars|calendar sections]] as tables
 +
** flesh out [[:Bricodash/Future|Bricodash Future Ideas]], explaining known requirements for each
 
* cloud log
 
* cloud log
 
** add boxrs-based git repositories to Cloud Log panel
 
** add boxrs-based git repositories to Cloud Log panel
Line 21: Line 21:
 
** 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)
 
** finish fleshing out remainder of movable feasts for [[Bricodash#Community_Calendar|Community Calendar]] (June forward)
 
** finish fleshing out remainder of movable feasts for [[Bricodash#Community_Calendar|Community Calendar]] (June forward)
** add nyc resistor, fat cat fab lab, and makerbar to [[Bricodash#Community_Calendar|Community Calendar]]
 
 
** refactor brite search by location routine to common library
 
** refactor brite search by location routine to common library
 +
** add nyc resistor, fat cat fab lab, and makerbar to [[Bricodash#Community_Calendar|Community Calendar]]
 +
** concise calendar response for interactive slackbot
 
** enable toggling between Welcome header and holiday greetings [[Bricodash#Community_Calendar|^]]
 
** enable toggling between Welcome header and holiday greetings [[Bricodash#Community_Calendar|^]]
 
* cleanup
 
* cleanup
Line 28: Line 29:
 
** refactor source files from initial launch
 
** refactor source files from initial launch
 
** squish and push fork to upstream
 
** squish and push fork to upstream
 +
** reimplement camera gateway as system service
 
** migrate from bricolage to less power-hungry hardware
 
** migrate from bricolage to less power-hungry hardware
 
** reimplement bricolage to run as embedded system under elixir/scenic/nerves</onlyinclude>
 
** reimplement bricolage to run as embedded system under elixir/scenic/nerves</onlyinclude>

Revision as of 00:53, 11 July 2019

See: Bricodash for project details

Current Tasks Outstanding

  • reliability
    • migrate to standard ports (once relayd installed on router)
    • configure X-Forwarded-For logging in apache (pending relayd)
    • enable SSL for camera feeds (requested for full conversion to new sous veil system)
    • add route to trigger a pishop browser cache flush
  • documentation
    • recent edits monitor to trigger cache purge on transcluded Bricodash documentation updates
    • help get mediawiki server 504 issues resolved (currently an obstacle to Bricodash documentation)
    • redraft lists in calendar sections as tables
    • flesh out Bricodash Future Ideas, explaining known requirements for each
  • cloud log
    • add boxrs-based git repositories to Cloud Log panel
    • add remaining sources to HM Cloud Log panel
  • calendars
    • correctly calculate date of International Astronomy Day (email out to Astronomical League for better calculation rules)
    • finish fleshing out remainder of movable feasts for Community Calendar (June forward)
    • refactor brite search by location routine to common library
    • add nyc resistor, fat cat fab lab, and makerbar to Community Calendar
    • concise calendar response for interactive slackbot
    • enable toggling between Welcome header and holiday greetings ^
  • cleanup
    • integrate citymapper API for local subway stations
    • refactor source files from initial launch
    • squish and push fork to upstream
    • reimplement camera gateway as system service
    • 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