{"id":5910,"date":"2016-12-29T20:20:52","date_gmt":"2016-12-30T03:20:52","guid":{"rendered":"http:\/\/www.graphics-muse.org\/wp\/?p=5910"},"modified":"2017-10-03T08:56:24","modified_gmt":"2017-10-03T15:56:24","slug":"what-to-do-in-2017","status":"publish","type":"post","link":"https:\/\/www.graphics-muse.org\/wp\/?p=5910","title":{"rendered":"What to do in 2017"},"content":{"rendered":"

\"\"<\/a>Over on my wiki<\/a> I have an area called Project Cody<\/em>.  The code name is for my youngest dog and a play on the word “code”.   It’s a private area where I keep project plans I’m not ready to talk about or share with the public.  Only a few choice compatriots have access (until the Russians get wind of it, I assume).<\/p>\n

I keep a page in Project Cody with ideas for future projects.  This past year I collected a bunch of ideas I want to work on, most of which are related to extending PiBox<\/a> in one manner or another.  Some are related to protecting my web sites and servers. This doesn’t include continued work on PiBox issues<\/a> nor does it include my plans for adding IoT support for managing devices via wifi.  The IoT projects are part of my IronMan<\/a> project – the idea that I can build Iron Man’s house using existing technologies.  It’s not really much of a stretch.  The real issue is getting glass that will act as a display, either directly or by electrically opaquing the substrate. <\/p>\n

I’ve been working on ideas for Iron Man for some time.  I already have the Jarvis<\/a> project for accepting voice commands and evaluating them for basic control of the house by simply passing audio files to Google’s voice to text translator<\/a> (though that may not be the one I have implemented in Jarvis now) and then passing the text through a natural language processor <\/a>to interpret the command.  There really isn’t much to that project now except a proof of concept.  And it doesn’t have Jarvis’ voice<\/a>.  Generating a realistic voice is a fairly time-consuming activity and I’ve so many other things that take precedent.  But the basic structure is there.  Extending it to do something useful won’t happen till I have some devices to control.<\/p>\n

Which leads me to some of the technology plans I have for PiBox in 2017.  Take these with a huge grain of salt.  I fully expect my aging pups to occupy much of my time in 2017.<\/p>\n

Custom smartphone based on Raspberry Pi<\/h3>\n

\"\"<\/a>I’m so frustrated with the bloat on my Android Phone.  It worked fine when I bought it but automatic updates have pushed it to its limits, making most apps fail to start or crash after they do.  It’s not like I have many apps on the thing.  I don’t use the phone for anything other than the occasional text with my wife.  You can blame the bloat on Android or the provider (Virgin Mobile) if you want.  But the truth is that it makes sense for phone vendors to bloat the OS to force you into the next model.  It’s a trick they learned from the PC world.  And it’s crap.  We should be able to build our own phones.<\/p>\n

Fortunately, it’s possible to build<\/a> your own<\/a> phone.  What’s important about this project is that<\/p>\n