Input
Back to Architecture.
Principle
Here we gather all the way to add ideas to Seedea. We try to be up-to-date with ALL the way to connect include the last trendy ones! See the list below and if something is lacking, just tell us.
Different input modules
Meeting recording
More generally we could dedicate an entire part of the input management to meeting recording. It would share several Input module but would handle multiple simultaneous participant.
Bot for all conferences modes (telephone, skype, IRC, MSN, etc...) after each meeting automatically :
- record then post the transcript + audio
- then organize and use other existing tools
See the on-going experiment : StigmergyLive in TheLab
Voice based input
Talking to the wiki, i.e. speech recognition
- call a number
- select your wiki page with numbers
- talk
- get your speech added to that page
Easier to do the formatting only later on, on a computer as the goal isn't to replace the web interface but to provide an alternative for notes on the spot.
- Speech Recognition relying on VoIP (notes on VoIP)
- Buy 1 number per country using Gizmo (eventually rely on Gizmo5 Business) and handle it with a VoIP number (cf Asterisk settings Gizmo)
- Hook the VoIP with Asterisk
- generate user box using Asterisk API when they register
- redirect user to his box when he calls using commands with numbers (or voice based on VoiceGlue and VoiceXML scripts)
- record the call
- CMUSphinx
- convert the recorded call to text
- add the typed and prepared (formatted links, paragraph, etc) text to the user personal account
- Integrated commercial systems
- Jott (US+Canada 24/10/08)
- SpinVox (United Kingdom+Canada 24/10/08, no API)
- see also Center for Accessible Technology (exchanged email with Jennifer there)
Online social HUBs
- IM + Mail + SN + Phone + SMS + CustomURL + API
- IM + SN + CustomURL (only custom URL for receiving, not sending)
- SN
- SMS
- IM
- ?
Requirements
- able to send the message to a custom URL
- eventually rely on a proxy service using a bot (like IMified) that would fetch the message on a supported network but potential problem of
- TOS/EULA
- response time
- frequency (possibility to use the proxy as a buffer)
- account creation
- fully automated
- API to automate the subscription process
- TOS/EULA not requiring the user to go and subscribe
- manual but 1 account for the whole site
- no frequency limitation if 1 account
- possibility to use proxy like IMified
To integrate
test