1) the tenting leg should be in the other direction; I can cut a wedge out of the 1x2 wood, but I can't cut the entire length of the board at the angle.
2) the platforms need to be about 1/4" - 1/2" in most dimensions. The holes I drilled to receive the keyboard were too close to the edge, and even with careful drilling (not shown) there just wasn't enough material between the holes and the edge for me to feel comfortable with that. Alternatively, I could notch the edges instead of drilling them out. Worth thinking about.
3) the 3/4" thickness of the wrist rest piece is too small. I need about 1", I think.
4) I am positive I'm going to mess up the tenting legs and make them wobbly. Calculating the angles, especially when I intend to put little rubber feet on as well, will be a challenge. I should just plan on leveling it by sanding the bottom of the tenting wedge. Alternatively, I could figure out a way to make a movable, adjustable tenting wedge. This would make storage easier (since it would lay flat) and also let me experiment with actual tenting angles.
5) home depot sells crappy lumber. I'm glad this was cheap, because I messed it all up and gone (and have plenty more to experiment with before I finalize the design and build). But if I'm going to really make something pretty, I should look into buying a few pieces of nice wood. In particular I'm not happy with the "premium" 3/8" plywood. The oak 1x2 was fine, although unremarkable. I figure the size I'm working on here I can probably afford better wood.
Before I built my ergodox, I had a razer blackwidow (which is quite nice for a regular shaped keyboard, sturdy and MX blue switches). The keycaps were ABS, and they definitely got smooth feeling pretty fast. It isn't terrible, though, just a thing.
I do hear you though: a pbt desire really limits what you can use, especially if you want pbt in some weird key profile (like SA), especially-especially if you want strange keys or nonstandard caps (I'm explicitly not doing dvorak or colemak because I don't want to deal with that).
I put all that work behind a little facade pattern in angular, so I can present the google client api stuff to my webapp layer without having to mess around with globally-scoped objects and stuff. It's even testable now, with mocks and so forth. Fancy.
Give it a listen!
If Patreon had existed in 2009 when the blog began I know I probably only would have had a couple bucks in funding in the first year, but the gradual build up would have been an even better motivator to keep working and improving. It probably would have been enough to keep my online during the year where I couldn't even afford an internet connection.
Full Disclosure - whoever signs up the most mailing list recipients in the next week gets a prototype of the keyboard.
The issue is that I then take that g+ info and re-issue a local token (JWT) that takes a lot longer than an hour to expire. I don't want my users to keep hitting the login button, and I don't want to expose my api id and key on the front-end, so I manage oauth stuff on the server side.
I'm able to grab a refresh token from users the first time they authorize, and finagle getting it again if I do approval_prompt=force at login-time. The problem is that right now, I'm testing stuff out so my database gets wiped occasionally, so my tester accounts end up getting that approval_prompt=force looking login fairly regularly, so I can grab the refreshToken and send it along.
I'm worried about this line from the documentation:
Note that there are limits on the number of refresh tokens that will be issued; one limit per client/user combination, and another per user across all clients. You should save refresh tokens in long-term storage and continue to use them as long as they remain valid. If your application requests too many refresh tokens, it may run into these limits, in which case older refresh tokens will stop working.
Is this something I need to worry about at testing scale? E.g., re-requesting refresh tokens about ten times for about ten users before putting the app into production, at which point I don't think I'll have to request more than once, unless there's a bug.
So, as long as I'm storing refresh tokens in the backend, it's not too bad- I just make sure that the current one works and we're good. I won't be requesting 25, and even if I did, I only care about the most recent one.
- Michigan State University
- University of California, Berkeley
- Knowles Science Teaching FoundationProgram Officer, Educational Technology, 2013 - presentSupport the teaching fellowships at KSTF by helping fellows and teacher developers create technologically-enhanced lessons. Develop new ways to bring teachers together online. Design and deploy professional development for educational technology use in the classroom.
- University of California, BerkeleyVisiting Professor, 2010 - 2013
Using Google Apps Script to make a Sites Hashtag Index
My students are doing this really cool thing: they're using a Google Site to collect and curate interesting resources for progressive teache
Mash Paddle - 36 inch Stainless Steel (With Drilled Holes) | MoreBeer
Your Home Brewing Supplies Super Store since 1995. Thousands of hard to find Beer Making products and kits. Free shipping on orders over $5
NYPD raze the #OWS library, throw out over 5,000 books - Boing Boing
NYPD raze the #OWS library, throw out over 5000 books. By Cory Doctorow at 7:09 am Tuesday, Nov 15. Some collateral damage in the police rai
What we SHOULD have been taught in our senior year of high school - The ...
The Oatmeal. Comics. Quizzes. Blog. New! Book. Shop. Follow: Twitter. Facebook. RSS / Email. What we SHOULD have been taught in our senior y
YouTube - Mameshiba 21 - Pronunciation Bean [with English annotations]
Create AccountSign In. Home. BrowseMoviesUpload. Hey there, this is not a commercial interruption. You're using an outdated browser, whi
Let's Go (Vyranis Remix) by Vyranis in the Calvin Harris Pepsi Remix Con...
Listen and vote for Let's Go (Vyranis Remix) by Vyranis in Beatport's Calvin Harris Pepsi Remix Contest