Difference between revisions of "WeirdlyAutomated"

From Noisebridge
Jump to: navigation, search
(Perhaps-vague Project Category Ideas)
Line 13: Line 13:
 
1. Emergency Slack bot command => Triggers Mary speaking that message into Noisebridge (e.g., "I left my purse next to the soldering iron")
 
1. Emergency Slack bot command => Triggers Mary speaking that message into Noisebridge (e.g., "I left my purse next to the soldering iron")
  
2. Flaschen Taschen API (send it text or pictures over TCP, HTTP, or WebSockets => displays them)
+
2. Flaschen Taschen API (send it text or pictures over TCP, HTTP, or WebSockets => displays them) [EDIT: I now see that [some of this is already possible https://github.com/hzeller/flaschen-taschen/blob/master/doc/protocols.md#send-images-right-from-the-command-line]]
  
 
3. Service directory/service discovery service of things on the LAN
 
3. Service directory/service discovery service of things on the LAN

Revision as of 11:01, 29 June 2017

We just have one question:

Why isn't Noisebridge weirdly automated???

"Why, whatever do you mean weirdly automated?"

Automated and integrated and aliiiiiive! with projects like this:


Project Ideas

1. Emergency Slack bot command => Triggers Mary speaking that message into Noisebridge (e.g., "I left my purse next to the soldering iron")

2. Flaschen Taschen API (send it text or pictures over TCP, HTTP, or WebSockets => displays them) [EDIT: I now see that [some of this is already possible https://github.com/hzeller/flaschen-taschen/blob/master/doc/protocols.md#send-images-right-from-the-command-line]]

3. Service directory/service discovery service of things on the LAN


Perhaps-vague Project Category Ideas

1. Voice to text => Mary => Triggers an action of hers

2. "The Noisebridge API"; Noisebridge itself should feel like a programmable machine