477 karma · joined July 9, 2015
I've been thinking about using the accessibility I framework to ETL the messages into Kinesis to facilitate event driven architecture. 'archived' Messages and attachments are stored as bsob.
Hell, I've even experimented with some goofy stuff, like FaceTime to VOIP- asterisk is just so flexible
Google photos is simply refusing to let you use their app all unless you grant them access to view all of your photos.
I'm all for privacy -far beyond the average person- but this seems like one of those cases of uninstall it and move on if you don't agree with the product decision.
Fwiw: Not a fan of google. Currently on iCloud + Flickr for non-sensitive photos
There's even cuttings bits that have integral cooling (holes in the cutting surface).
Machine shops need bodies to do a few things (some of which OP mentioned) loading materials, removing materials, changing broken cutting bits, cleaning the machines (especially if you're cutting something like magnesium).
Machine shops also need bodies to build jigs to hold pieces to the machine table while the machines remove material (think 5 axis pieces, especially).
Despite all of this – there's an amazing amount of automation at play. Tool changes, coolant, temperature monitoring, the list goes on. I'm currently building some automation hardware and software so we can start to fill the gap of 'dead' time where machinists are pressing buttons, loading in blanks, and are bored out of their minds.
It's such an interesting space.
Interesting.
I catch myself thinking that I'll be in a conundrum when the TV eventually dies. It looks like new versions of LG's WebOS has ads every time you open it's 'dock'.
Yes, you can buy an AppleTV (or your preferred alternative) – but you'll always be scurrying to the TV's original remove for anything beyond on/off, or changing the volume. So you either keep two remotes around, or toss Apple's glass remote and use a universal remote.
Does it work? Sure. Is it elegant? Eh. How have you guys solved this?
I do remember one particular core that was surprising difficult. Everything was encoded in EBCDIC. You had to rotate telnet (!) connections depending on the day of the week. There was one person (a man named Earl) who could help you if you had a problem with the continuous stationary documentation (luckily it was scanned).
Oh the memories...
Homelab [hom-læb](n): a laboratory of (usually slightly outdated) awesome in the domicile
```
INNER JOIN chat_message_join ON message.ROWID = chat_message_join.message_id INNER JOIN chat ON chat.ROWID = chat_message_join.chat_id INNER JOIN chat_handle_join ON chat.ROWID = chat_handle_join.chat_id INNER JOIN handle ON handle.ROWID = chat_handle_join.handle_id LEFT JOIN message_attachment_join ON message.ROWID = message_attachment_join.message_id LEFT JOIN attachment ON attachment.ROWID = message_attachment_join.attachment_id ...
```
But it really wasn't that hard. I was able to programmatically send and receive iMessages. The problem (as the author pointed out) was that this changed, and didn't really work for the long. Although, I'm sure it could still be reveng'd – it's a pain in the ass, and (for me) not really worth it... =/
Great job'