When you send a message to Google SMS, we log an encrypted version of the incoming phone number, the wireless carrier associated with the number, and the date and time of the transaction. We use this data to analyze the message traffic in order to operate, develop and improve our services.
Google will never rent or sell your phone number to any third party, nor will we use your phone number to initiate a call or SMS message to you without your permission. Your wireless carrier and other service providers also collect data about your SMS usage, and their practices are governed by their own privacy policies.
And as for MPE being unintuitive, well, all a matter of perception. I find:HELLO,:BYE, and:LISTFILE much more intuitive than their *nix counterparts. Maybe not as efficient for typing, but hey, that's what UDCs are for.;->
Plenty of I/O options
on
Tandys Never Die
·
· Score: 2, Informative
Yes, there are plenty of ways to get data in & out - serial, parallel, audio-cassette, 300baud modem. There is a freeware MS-DOS program that allows a PC to talk to it over a serial line and emulate a disk drive so the M100 can save & retrieve files by name.
Some hams even hooked it up to packet radio devices to run it wireless.
my contribution to M100 "Open Source" community
on
Tandys Never Die
·
· Score: 1
Back in the day, one of the best places for M100 stuff was the M100SIG forum on Compu$erve (it's probably still there, but I'm not a member anymore). Lots of shareware and freeware, most with source code. We ran a disassembler on the ROM image (I probably still have a 3-inch thick hard copy) and extended the built-in utilities with our own Z80 code. Anyone remember XMDPW6.CO? It was an enhancement to the terminal emulator to add things like XModem file transfers. I added a keyboard macro facility to that with about 20 lines of assembler code.
I like the idea of hanging one on the wall as clock/conversation piece. With a serial connection to another box it could even receive live internet updates for things like/. headlines! Maybe I'll dust mine off...
I've tried low screen res w/large virtual desktop. I ended up spending too much time mousing around to keep the focus where I was working. A decent magnifier also tracks keyboard focus, so that text carets or other types of focus like active buttons are always within view.
RP and many other diseases of the retina are very good reasons to keep an eye (no pun intended) on this and similar projects. Here are a few good resources for other types of low-vision coping technology:
Three suggestions from my wife, and end-user. These are somewhat client-centric but carry some implications for the back-end as well.
1. Ability to change font and/or background color of each event.
2. Ability to delete one occurrence of repeating appointment, without disturbing future occurrences. Possibly an e-mail reminder that the event for that day was cancelled.
2. Ability to print a professional looking page for notebook or planner, in month or week view, with all days the same size.
And from myself, I want to see a good integration of to-do list management into the calendar server. To-do's should be stored with discrete attributes for both importance and urgency, not just a generic priority. Also, an optional target date and/or hard-deadline date, intelligent status-change paths with event/notification triggers (send email to specific addresses whenever a task of type q moves from status b to c or urgency d to e).
Sounds like a great project, hope you are
successful.
Slashdot Mirror
Rumor has it that the M100 firmware was the last code that Bill Gates personally did any real work on before going 'big time'.
The apache-on-M100 was an April Fool's joke though. (almost time for another round of those...)
http://www.google.com/sms/privacy.html
Information that we collect and how we use it
When you send a message to Google SMS, we log an encrypted version of the incoming phone number, the wireless carrier associated with the number, and the date and time of the transaction. We use this data to analyze the message traffic in order to operate, develop and improve our services. Google will never rent or sell your phone number to any third party, nor will we use your phone number to initiate a call or SMS message to you without your permission. Your wireless carrier and other service providers also collect data about your SMS usage, and their practices are governed by their own privacy policies.
1-800-555-TELL
It ain't google, but it gets you lots of useful info without thumb-boarding a bunch of TXT to get it.
... the new architecture is based on 31-bit integer datestamps and is expected to roll over to zero before it is released.
They're all there, try
And as for MPE being unintuitive, well, all a matter of perception. I find :HELLO, :BYE, and :LISTFILE much more intuitive than their *nix counterparts. Maybe not as efficient for typing, but hey, that's what UDCs are for. ;->
Yes, there are plenty of ways to get data in & out - serial, parallel, audio-cassette, 300baud modem. There is a freeware MS-DOS program that allows a PC to talk to it over a serial line and emulate a disk drive so the M100 can save & retrieve files by name.
Some hams even hooked it up to packet radio devices to run it wireless.
Back in the day, one of the best places for M100 stuff was the M100SIG forum on Compu$erve (it's probably still there, but I'm not a member anymore). Lots of shareware and freeware, most with source code. We ran a disassembler on the ROM image (I probably still have a 3-inch thick hard copy) and extended the built-in utilities with our own Z80 code. Anyone remember XMDPW6.CO? It was an enhancement to the terminal emulator to add things like XModem file transfers. I added a keyboard macro facility to that with about 20 lines of assembler code.
/. headlines! Maybe I'll dust mine off...
I like the idea of hanging one on the wall as clock/conversation piece. With a serial connection to another box it could even receive live internet updates for things like
I've tried low screen res w/large virtual desktop. I ended up spending too much time mousing around to keep the focus where I was working. A decent magnifier also tracks keyboard focus, so that text carets or other types of focus like active buttons are always within view.
here [javadevelopersjournal.com]
RP and many other diseases of the retina are very good reasons to keep an eye (no pun intended) on this and similar projects. Here are a few good resources for other types of low-vision coping technology:
autofocus eyewear [lowvision.org]
the Jordy [enhancedvision.com] (yes, trek-inspired!)
wire a camera to your brain [artificialvision.com]
artificial retina [mit.edu]
1. Ability to change font and/or background color of each event.
2. Ability to delete one occurrence of repeating appointment, without disturbing future occurrences. Possibly an e-mail reminder that the event for that day was cancelled.
2. Ability to print a professional looking page for notebook or planner, in month or week view, with all days the same size.
And from myself, I want to see a good integration of to-do list management into the calendar server. To-do's should be stored with discrete attributes for both importance and urgency, not just a generic priority. Also, an optional target date and/or hard-deadline date, intelligent status-change paths with event/notification triggers (send email to specific addresses whenever a task of type q moves from status b to c or urgency d to e).
Sounds like a great project, hope you are successful.
been dere, dun dat. don't have the ref handy but one of the other other artificial retina projects is doing with laser, just like you suggest.