I have seen the light! Let’s Encrypt is well poised to become the SSL key manager for those of us who don’t want to think about TLS. It’s easy to setup and configure, and generally just does the right thing.
So I’ve had the idea for a long time to write myself a little script that would configure VLC/Gstreamer/etc
to pipe a video file in to v4l2loopback to expose it as a virtual
webcam. Then I can just “play” it in Google Hangouts and have virtual movie watching parties, without silly
things like “Ok, everyone hit play on 3!”
I want you to imagine someone for me. Her name is Jessica and she is 17 years old. She lives in a two bedroom apartment with her mother and uses an old laptop she got from one of her mom’s ex boyfriends. With it, she browses the portals that serve as her connection to the community constructed…
A reminder of what it’s like to live on the other side. Because sometimes we forget just how hard technology can be.
Ok, so last time I said there would be some designs in this post. That was a complete fabrication. (Or maybe an enhancement of the truth?)
I’ve been thinking a lot about harder problems: 1: I love Web Components. 2: Polymer has all the compatibility of car components (ie it only runs on Chrome).
So I’m leaning more towards Mozilla’s X-Tags to do some of the heavy lifting of Custom Elements, use HTML Imports, and leave Shadow DOM out of the picture. The problem with this is that X-Tags does approximately nothing for you with regards to templating, data binding, or anything else you need to do.
For some reason, I also want to move away to jQuery. Vanilla JS has come a long ways since 2004, and maybe if I use less frameworks of questionable utility, the lighter the app will be. To that end, I wrote doubledollar.js, a simple wrapper around some of the pain points of DOM (web components stuff, abbreviations of common operations, AJAX things, some promise stuff, etc). I expect to develop it more as I dig more into Leatherbound.
One the data side, I had a painful reminder that I’m no longer in key-document land and that Google Cloud DataStore (aka BigTable) stores simple schemaless records. So I had to do some actual thinking as to my data store.
What I’m thinking is that an entire post is stored as (sanitized) HTML in a single value in the database. Make sure that user-facing content and searchable text are in the text content of it. We’re already making heavy use of custom tags in front-end, so why not use them in the data store, too? The software can semantically know exactly what happened, widgets can be updated, and the messy implementation details (like the code to embed a video) don’t appear in the DB. Use tags like <lb-event>, <lb-picture>, <lb-tag>, <lb-mention>, etc. The software can easily parse these out for various reports (lists of media, tag clouds, etc).
For indexing, hash-tags and at-mentions would need to be also stored, but I consider these cache columns for the benefit of querying.
My next problem is the posting and editing process. Because of uploading media, posting an entry is not a simple POST request, but several. Clean up of media of deleted posts would need to follow (unless I take the tumblr approach and store everything forever). The alternative is to upload all the media at once, but this sounds like a recipe for bad user experiences (long post time, higher chance of failure, and unusual behavior).
I’ve been using the i3 Window Manager for a little while now on my laptop. For those of you who don’t know, i3 is a tiling window manager somewhere between wmii and awesome.
I personally find it’s minimal enough to be quite nice on my 15" laptop, but still implements useful things like notifications, systray, and a normal way to log out.
My customizations are available on my github with config file an support scripts. The big things it does is set up i3lock (with a fuzzed background, thanks to Image Magick), starts a bunch of baseline stuff, and fixes the Chrome App List.
So keyboard-based window management is here to stay for me. Good luck getting me on vim or emacs, though.
I’m working on a new project which I thought I’d turn into a series. It’s nothing fancy or sophisticated. The code name is Leatherbound, and it’s a diary/journal web app. This first post I just want to lay out the premise and some of the requirements and guidelines.
Easy to use
Some of the decisions I’ve made:
Using Material design: Because why not? At least it’s not more bootstrap)
Google AppEngine: scalable and free limits
Google Cloud Storage: I think NoSQL will work better than SQL
Using Polymer (although that might not be mobile friendly? May ditch it)
Optionally include events that have occurred since the last post (from Google Calendar)
Full WYSIWYG (I’m thinking inspired by hallo.js, but probably re-implemented for material)
Embedding media, including photos
Some other random details:
First screen after login is the new entry screen, and it should load fast. I figure its the #1 thing people do when they login.
May look into Ember? The initial load time is a concern against the previous requirement and Polymer’s already slow loading.
Next time, I’ll be showing the prototype interface I’ve got going so far.