= Nesting =

''Various DIY/smarthome and other projects about (or related to) the domicile.''

<div style="float:right; padding-left: 20px; padding-bottom: 10px">__TOC__</div>

== Outreach ==

There's been some discussion of pursuing more active outreach and membership development for the space, including:

=== Scannable Code for Donations Flyer ===

Want to redo the donations notice at the space to include a QR Code or two to allow folk to quickly make donations from their mobile device if so inclined.

=== Creating a More Comfortable Environment ===

First step we're considering tackling is the kegerator/dishrack area. Ideas on the table:

Installing trays within the kegerator to store bottled beverages. There has been standing water at the bottom of the kegerator at times (whether due to a leak in the water keg or condensation), so trays would make things a bit less unpleasantly damp on retrieval. Related to this, we ought to have some sort of signage that makes clear what is on offer for the sake of visitors at such time as informed members are not present to explain what's what.

We're also examining options for rehanging or replacing the bathroom door to free up space on the bathroom wall now behind the swing of the door. The idea would be to install shelving on that wall for drying racks and dish storage.

=== Tag-Team Community Cross-Pollination ===

Going to conduct a survey to identify progressive-adjacent Meetup groups and other local orgs that we might want to develop ties with. The goal would be to find likeminded subject domain experts who might be interested in sharing knowledge and expertise within the HM community—fostering such relationships may also serve to bring new members to HM who might otherwise not have found us absent such outreach. Several members have expressed an interest in helping with this initiative.

Relatedly, am wanting to tap the broader (even global) hackerspace/makerspace community to bring in folk to offer talks or presentations on the history of the hacker, maker and DIY movements.

== Maintenance ==

=== Crafts Event Prep ===

Flyers for October and November are due. Craft ideas research: mask making (for October); doll making (to find a use for many dozens of knitted dolly caps). Need to do an audit of our craft supplies and prepare orders to restock.

=== Paperwork Backlog ===

Have been sorely derelict on a heap of household and client bookkeeping and filing, while immersed in other recent making projects. This includes scheduling of long-overdue appointments and restocking our household pantry. Made some significant headway on this, might as well keep ball rolling.

=== Roomba Repair ===

Cliff sensors have been successfully disabled, and original left wheel reinstalled. Still unhappy with side brush performance—and will return to this eventually—but presently just glad to have this robot back in service.

=== Darn Socks ===

They're actually quite nice socks, but yeah, they've got holes. Quite a few of them do, darnit.

== Hackerspace ==

=== Astronomical Device ===

One of our members has a telescope rig powered by a Raspberry Pi, but wants to tweak the UI running on the Raspbian desktop. Have promised to help them figure out what needs reconfiguring next time we're both in the space.

=== Office Chair Repair ===

Having already repaired three other office chairs of various designs and defects, another chair presents itself for fixing. This time, it's an old brown chair that is already an heirloom hack. A some time in the past, the bottom of the seat has been replaced/augmented with a wooden construction that appears to secure the seat cushion to the caster-base column. Since that time, the bolts holding this wooden bottom to the cushion have come loose on the front corners. A user who naively reached under the front of the chair to lift and move it, can accidentally catch their hand between the cushion and the wooden bottom.

The chair currently has the word "NO" inscribed in blue tape across the top of the cushion seat, to warn users, if not that they might get bitten by the chair, then at least that they ought to exercise caution.

On best examination, it appears the repair will involve removing the wooden bottom from the cushion, and then resecuring or replacing nuts that had previously held the wooden base bolted to the cushion seat.

==== Steelcase Leap Chair ====

The cylinder button began getting depressed unintentionally again. PLA+ failed in about 30 days—the straddle legs snapped off rather than the washer ring failing due to compression. Dug out the old spacer and replaced with another 70% infill PLA, pending the creation of a molded graphite replacement. Rising is a bit stiff and requires multiple pulls on lever, but does then stay up until released. Will monitor. (as of 10/11/19)

=== Member Storage Audit ===

Planning to go through our member storage shelves, identifying left-overs from former members, and moving less actively used bins to higher shelves, to better facilitate storage needs of new members in the future.

== Roommmate Tech/Organizing Consult ==

* electronic birthday calendaring
* charitable giving analysis
* pruning their electronic task list
* research piano instruction apps for android
* getting them up and running to learn the ins and outs of using video conferencing tools
* organizing teaching materials filing system
* substitute teaching go pack strategy
* prepping unique favor packs for Halloweens

== DIY ==

=== Dashboard Door Buzzer Integration ===

Wanting to wire a single-board device in to the building intercom system to detect the door buzzer. This will allow us to use the dashboard real-estate for other displays than the door camera, while still switching back to the camera swiftly when someone is buzzing for entry.

=== Household Repairs ===

Various small and large projects have been waiting in the wings, including:
* Appliances
** rebuild/redesign Lego water fountain
** repair of a glitchy flat-screen monitor
** replacing broken window blinds
** retouching nylon on dishwasher racks
* Space
** repairing vinyl floor in kitchen
** securing a set of shoe holder mounts
** refurbishing an old hammer drill
** ceiling hook over bed
* Sewing
** replace wrights on lampshade of a standing lamp
** darning/patching bedsheets
** hem favorite scarf

=== Installing Storage ===

Once repairs are out of the way, a number of household storage projects are on the agenda, including: a corner bar for hanging clothes and installing rack shelving in our kitchen

Completed: Bathroom storage tower has been cut to accommodate shut off valves, urethane and fresh paint applied, and installed in its new home.

=== Custom Craft Material Dollies ===

Our community crafts group has accumulated more donations than could every easily fit in our existing carts. We've resorted to lugging surplus around in oversize retail shopping bags. Moreover, the carts we do have aren't for outdoors use. They're fine for moving materials from our apartment to the community room the same building, but if we want (or need) to set up for an event in another building, the casters are not equipped for even well-maintained sidewalks, and we tend to see drawers slide open or and containers slide off shelves and topple to the ground as we trundle along on sloped grades. Finally, we've got some craft materials, namely yarn, fabrics and collage materials, that really need to be in larger containers that display their contents in an inviting way without having to unpack and repack those materials for each session.

Thus, there are three goals. First, to design a pair of dollies with custom, quick-assemble cage frameworks. The idea is that our existing craft carts could be lifted onto the dollies, providing heavy duty casters to get around outdoors, and then hemmed in by bars or slats that would keep drawers and shelf contents secure pending arrival at a destination. Providing for cover against rain or other weather would be a bonus. Second, to design a similar dolly for stacking larger containers than we currently aren't using, but would serve for bulk craft materials. Third, to design containers for bulk craft materials that quickly deploy as inviting displays of those same materials on site.

== Technology ==

=== Data Processing Tower ===

The Tellurium project is proving very CPU-intensive. Generating a batch of 99 one-of-a-kind bespoke handbills easily takes six hours for my current computer to generate, plus another hour of post-processing, and then two hours of printer time. Further, the new toolchain (once gdp spelunking resolves current segfaults) will rely heavily on NLP processing, where parsing for word counts is already proving computation intensive.

Going to explore building out a custom box to handle chugging through these processes. In addition to building the toolchain to leverage multi-threading and multi-process techniques, as appropriate, am also considering the possibility of pushing some computations to GPU. The actual assembly of each word cloud (placing objects on a two-dimensional field) seems especially suited to GPU-based computation. This, of course, would require learning something about GPU-based solutions and figuring out what libraries exist or could be rewritten for GPU before specing out the new machine build.

=== Network Management ===

The various electronic components on the table-level of my IKEA-built standing desk have become an unmanageable tangle. The plan is to build a pair of LackRack component mounts under the standing desk and transfer various Ethernet and power connected devices thereto. As part of this process, will build out a heat ducting system to channel air from below the desk to the intake vent of the convector a few feet away — taking advantage of the chiller cooled pipes that feed the convector in the summer.

Also want to run Ethernet to the back of our apartment, rather than rely on spotty performance of EoP extender currently in use. This will support the development of audio notification relays planned throughout the apartment for telephony and other applications listed below. Also, gonna set up a Pi as a wifi router for our wifi-only printer, as it has become a nuisance rebooting the main router every time the printer loses connectivity with the network.

=== Sleep-Hygenic Lighting ===

Intending to replace current lighting fixtures with programmable smart bulbs and a custom driver that will adjust the level of blue light throughout the day, in accordance with my 2nd/graveyard-shift work cycle. This includes the appliance bulb in the refrigerator, so that one isn't treated to a blast of bright white light when scrounging a "midnight" snack. Also part of this project will be running motion-detector activated red LEDs along the hallways, to allow my roommate to get around early morning without disturbing my sleep by flipping on room lighting.

The first step will be to set up a dedicated console-cable managed wifi router and management hub that will allow for control of smart bulbs without exposing those devices to the Internet.

== Audio Computing ==

===Telephony===
* integrated caller ID announcer
* mode-switchable caller ID blacklist/whitelist

===Appliances===
* whistle-activated battery-powered nebulizer
* whistle/tone detector/alterter network for hearing impaired
* rice cooker setup detector
* no-brainer portable stereo media player

===Advanced===
* multi-output audio stream relay
* nighttime noise machine lashup
* research hearing loop tech

== Miscellaneous ==
* mezzanine rack for a compact dishwasher
* DIY kitchen counter LED hydroponics enclosure
* intensive file cabinet purge
* paint apartment
* empty storage unit
* guinea pig hutch with integrated hydroponic garden
* learn to bake
* learn to ride a bike
* learn ASL

Bricodash/Future

2019-10-11T02:21:18Z

Beadsland: /* Other Cloud Services */

''See:'' <span style="white-space: nowrap">[[File:Bricodash_screenshot.png|35px]] [[Bricodash]] </span> for project details

<table width="100%">
<tr>
<td valign="top" width="48%">

== Current Tasks Outstanding ==

<onlyinclude>

=== BindSight :2020 ===

''See also:'' [[BindSight]] project page

{{:BindSight}}

=== Webhook Notifications ===

Javascript client-side triggers to deliver messages to our Slack channels to provide alerts when the camera feed or client devices stall.

* migrate sleep macro to general purpose library
* migrate from webhooks integration to webhooks feature of bricodash app (and update notice)
* server-side webhook on stall of any given device
* when wonkiness addressed: downthrottle chromecast reboots to 1x per day; stream swap-in to never

=== Server ===

Standardize Web server setup and fully integrate BindSight.

* migrate to standard web port (now that relayd installed on router)
* configure X-Forwarded-For logging in apache
* enable SSL for camera feeds (requested for full conversion to new sous veil system)
* enable SSL directly via daemon's listening port (i.e., elixir rather than apache)
* transfer slackbot snapshots to bricolage gateway

=== Documentation ===

Flesh out project documentation—after fixing existing problems with our Mediawiki server.

* 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)
* broach discussion of absent Copyrights page on Wiki -- do we want to adopt a license??
* redraft lists in [[Bricodash#Event_Calendars|calendar sections]] as tables
* flesh out [[:Bricodash/Future|Bricodash Future Ideas]], explaining known requirements for each

=== Cloud Log ===

Incorporate remaining sources into rolling update log shown in lower left-hand corner.

==== User Repositories ====
* refactor cloud/github to abstract away github/gitlab/etc
* allow more than most recent pushed repository to be shown
* add boxrs-based git repositories to Cloud Log panel

==== Other Cloud Services ====
* Mediawiki — pending new account requests
* Zendesk — count of unread/open inquiries
* Status updates on donations: Patreon, Paypal, Amazon Smile...
* write up requirements for [[Bricodash/Future#Instagram_Integration|Instagram Integration]]
* write up requirements for [[Bricodash/Future#Twitter_Integration|Twitter Integration]]

==== Retire IFFF Wiki Updates ====
* bot to post daily cloud log update to #general on our slack

=== Calendars ===

Incorporate additional calculated and externally sourced calendar events.

==== Fixes ====
* almanac alt for almanac events
* add enum of event sources for sorting priority (when same start time)
* move HM anniversary dates to special .cal that takes precedence on HM calendar (and also appears on NYC)
* swap out icalendar (buggy repetition exception handling) in favor of true API

==== Calculation ====
* correctly calculate dates of International Astronomy Day (email out to Astronomical League for better calculation rules)
* calculate dates of Manhattanhenge (email out to library of American Museum of Natural History for formula)
* add eclipses and other significant astronomical events to holidays
* finish fleshing out remainder of movable feasts for [[Bricodash#Community_Calendar|Community Calendar]] (June 2019 forward)

==== Integration ====
* use google search to find Offside Tavern Meetup events
* add placeholder events for non-Meetup Offside Tavern events
* refactor brite search by location routine to common library
* add nyc mesh, nyc resistor, fat cat fab lab, makerbar, makerspace nyc (SI), futureworks (BK/SI) to [[Bricodash#Community_Calendar|Community Calendar]]
* also add grow with google (if still in NYC), 2600, Off the Hook (if still broadcasting), blick, michaels, local library branches, makerish meetup events

==== Advanced ====
* revise #thehaps formatting to provide headers per day
* embed hotlinks in #thehaps channel event listings
* concise calendar response for interactive slackbot
* auto-capture of #thehaps posted events to [[Bricodash/Extra:Calendar]]
* automation/streamlining tools for cross-posting HM Meetup events to Spingo
* enable toggling between Welcome header and holiday greetings [[Bricodash#Community_Calendar|^]]

=== Cleanup ===

Remaining features and code maintenance before calling it a major release.

* integrate citymapper API for local subway stations
* refactor source files from initial launch
* find owners to adopt data sourcing projects that require more than passive API calls (see sections below)
* squish and push fork to upstream

=== Upgrades ===

Once built, streamline and rewrite as a truly beautiful application.

* migrate from bricolage to less power-hungry hardware
* combined community slack calendar to wiki page (requires privacy policy under brite license)
* reimplement bricolage to run as embedded system under elixir/scenic/nerves</onlyinclude>
* import python directly using beamparticle

</td><td width="1%" style="border-right:solid 1px #a7d7f9;"></td><td width="1%"></td><td valign="top" width="50%">

<div style="float:right; padding-left: 20px; padding-bottom: 10px">__TOC__</div>

== Sub-Projects Needing Owners ==

The projects below require an investment of time—such as active coordination with an API's owners—to be implemented, but would provide meaningful improvements to the overall feature-set of Bricodash if completed.

At some point the description for each will be fleshed out to provide a full functional specification, together with an exploration of the requirements to move forward. For now, capsule bullet points serve as place holders. For more information, touch base with [[User:Beadsland]].

=== 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 [https://developer.twitter.com/en/developer-terms/display-requirements.html Display Requirements]

=== Slack Calendar Response Bot ===

* interactive bot response to "What's happening?"

=== 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

</td></tr></table>

2019-09-28T02:20:25Z

Beadsland: /* Upgrades */

''See:'' <span style="white-space: nowrap">[[File:Bricodash_screenshot.png|35px]] [[Bricodash]] </span> for project details

<table width="100%">
<tr>
<td valign="top" width="48%">

== Current Tasks Outstanding ==

<onlyinclude>

=== BindSight :2020 ===

''See also:'' [[BindSight]] project page

{{:BindSight}}

=== Webhook Notifications ===

Javascript client-side triggers to deliver messages to our Slack channels to provide alerts when the camera feed or client devices stall.

* migrate sleep macro to general purpose library
* migrate from webhooks integration to webhooks feature of bricodash app (and update notice)
* server-side webhook on stall of any given device
* when wonkiness addressed: downthrottle chromecast reboots to 1x per day; stream swap-in to never

=== Server ===

Standardize Web server setup and fully integrate BindSight.

* migrate to standard web port (now that relayd installed on router)
* configure X-Forwarded-For logging in apache
* enable SSL for camera feeds (requested for full conversion to new sous veil system)
* enable SSL directly via daemon's listening port (i.e., elixir rather than apache)
* transfer slackbot snapshots to bricolage gateway

=== Documentation ===

Flesh out project documentation—after fixing existing problems with our Mediawiki server.

* 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)
* broach discussion of absent Copyrights page on Wiki -- do we want to adopt a license??
* redraft lists in [[Bricodash#Event_Calendars|calendar sections]] as tables
* flesh out [[:Bricodash/Future|Bricodash Future Ideas]], explaining known requirements for each

=== Cloud Log ===

Incorporate remaining sources into rolling update log shown in lower left-hand corner.

==== User Repositories ====
* refactor cloud/github to abstract away github/gitlab/etc
* allow more than most recent pushed repository to be shown
* add boxrs-based git repositories to Cloud Log panel

==== Other Cloud Services ====
* Zendesk — count of unread/open inquiries
* Status updates on donations: Patreon, Paypal, Amazon Smile...
* write up requirements for [[Bricodash/Future#Instagram_Integration|Instagram Integration]]
* write up requirements for [[Bricodash/Future#Twitter_Integration|Twitter Integration]]

==== Retire IFFF Wiki Updates ====
* bot to post daily cloud log update to #general on our slack

=== Calendars ===

Incorporate additional calculated and externally sourced calendar events.

==== Calculation ====
* move HM anniversary dates to special .cal that takes precedence on HM calendar (and also appears on NYC)
* correctly calculate dates of International Astronomy Day (email out to Astronomical League for better calculation rules)
* calculate dates of Manhattanhenge (email out to library of American Museum of Natural History for formula)
* add eclipses and other significant astronomical events to holidays
* finish fleshing out remainder of movable feasts for [[Bricodash#Community_Calendar|Community Calendar]] (June forward)

==== Integration ====
* almanac alt for almanac events
* add enum of event sources for sorting priority (when same start time)
* use google search to find Offside Tavern Meetup events
* add placeholder events for non-Meetup Offside Tavern events
* refactor brite search by location routine to common library
* add nyc mesh, nyc resistor, fat cat fab lab, makerbar, makerspace nyc (SI), futureworks (BK/SI) to [[Bricodash#Community_Calendar|Community Calendar]]
* also add grow with google (if still in NYC), blick, michaels, local library branches, makerish meetup events

==== Advanced ====
* embed hotlinks in #thehaps channel event listings
* concise calendar response for interactive slackbot
* auto-capture of #thehaps posted events to [[Bricodash/Extra:Calendar]]
* automation/streamlining tools for cross-posting HM Meetup events to Spingo
* enable toggling between Welcome header and holiday greetings [[Bricodash#Community_Calendar|^]]

=== Cleanup ===

Remaining features and code maintenance before calling it a major release.

* integrate citymapper API for local subway stations
* refactor source files from initial launch
* find owners to adopt data sourcing projects that require more than passive API calls (see sections below)
* squish and push fork to upstream

=== Upgrades ===

Once built, streamline and rewrite as a truly beautiful application.

* migrate from bricolage to less power-hungry hardware
* combined community slack calendar to wiki page (requires privacy policy under brite license)
* reimplement bricolage to run as embedded system under elixir/scenic/nerves</onlyinclude>
* import python directly using beamparticle

</td><td width="1%" style="border-right:solid 1px #a7d7f9;"></td><td width="1%"></td><td valign="top" width="50%">

<div style="float:right; padding-left: 20px; padding-bottom: 10px">__TOC__</div>

== Sub-Projects Needing Owners ==

The projects below require an investment of time—such as active coordination with an API's owners—to be implemented, but would provide meaningful improvements to the overall feature-set of Bricodash if completed.

At some point the description for each will be fleshed out to provide a full functional specification, together with an exploration of the requirements to move forward. For now, capsule bullet points serve as place holders. For more information, touch base with [[User:Beadsland]].

=== 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 [https://developer.twitter.com/en/developer-terms/display-requirements.html Display Requirements]

=== Slack Calendar Response Bot ===

* interactive bot response to "What's happening?"

=== 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

</td></tr></table>