$GAY_AS_OLD_PAREE: "Hi!"
$MICHAEL_DAVID_CRAWFORD: "Hi. I can't chat right now I'm talking with my girlfriend."
$GAY_AS_OLD_PAREE: "Do you sex?"
$MICHAEL_DAVID_CRAWFORD: "No."
$GIRLFRIEND wants me to move in with her. Where she lives housing is much less expensive than even Vantucky.
Either we will rent a house, or we will buy a vacant lot and I will build a house.
I actually know how to, because my father taught me how to use every kind of tool. I already have all the tools I would need; I even have a full-sized table saw.
I would need a helper, and I'd get someone else to do the foundation.
Maybe I'll build a geodesic dome. Bonita said she would refuse to live in such a Fullerian home, but quite likely $GIRLFRIEND would be into it.
The Hell is a homeless guy doing with a table saw? You quite reasonably ask. When my father died my mother asked what I wanted to inherit. "His tools," I replied. She paid for the storage.
I'm probably going to sell the auto body tools. Those were given to my grandfather by his best friend, because his best friend had no heirs.
Nighty-Night! Don't Let The Code Bugs Byte.
$GAY_AS_OLD_PAREE: "Hi!"
$MICHAEL_DAVID_CRAWFORD: "Hi. I can't chat right now I'm talking with my girlfriend."
$GAY_AS_OLD_PAREE: "Do you sex?"
$MICHAEL_DAVID_CRAWFORD: "No."
$GIRLFRIEND wants me to move in with her. Where she lives housing is much less expensive than even Vantucky.
Either we will rent a house, or we will buy a vacant lot and I will build a house.
I actually know how to, because my father taught me how to use every kind of tool. I already have all the tools I would need; I even have a full-sized table saw.
I would need a helper, and I'd get someone else to do the foundation.
Maybe I'll build a geodesic dome. Bonita said she would refuse to live in such a Fullerian home, but quite likely $GIRLFRIEND would be into it.
The Hell is a homeless guy doing with a table saw? You quite reasonably ask. When my father died my mother asked what I wanted to inherit. "His tools," I replied. She paid for the storage.
I'm probably going to sell the auto body tools. Those were given to my grandfather by his best friend, because his best friend had no heirs.
Nighty-Night! Don't Let The Code Bugs Byte.
Not manic. Not yet anyway.
There is a woman in my life now. She is very religious, so I have the idea that I'm going to get up in six hours.
Doubtlessly AC will find some fault with her. Perhaps he will suggest she's inflatable
She lives far away. I'm going to visit when I get paid
I had a long distance relationship once before. That works a lot better now because even video calls don't cost anything
She is very shy so I won't be tell you much about her
I would prefer to stay up all night but I promised her I wouldn't do that anymore
After nearly 6 years with a Motorola Photon Q (XT897/"Asanti") I finally decided it's time for a new phone, and spent the outrageous sum of just-under-$130-including-shipping for a Moto C Plus, screenglass, and rubber body armor.
Motorola, now a subsidiary of Lenovo, is known for most of its phones being fairly amenable to rooting and unlocking. This particular one also happens to be GSM-enabled and support dual SIMs, on the off chance I ever leave the US and want a data plan. Its specs are, by today's standards, unimpressive: quad-core MT6737M CPU (4x ARMv8 A53 @ 28nm, somewhat slower than a Snapdragon 425 for reference), 2 GB of memory, 16GB of eMMC flash, and 5" 1280x720 screen. The body is all plastic, though it's not bad plastic, and the battery is a surprising 4,000 mAh that weighs more than the phone itself does.
Now, it turns out the C Plus is *not* as easily unlockable as, say, the G4 is. In particular, the usual fastboot commands such as get_unlock_data simply fail with "unknown remote command" errors. The stock ROM is also kind of pants, though it's at least a fairly vanilla Android 7.0 rather than Madokami-forgive-us-all MIUI or TouchWiz.
However, there is a program called SP Flash Tool that is able to write directly to MediaTek devices' internal flash over a USB port. This is not for the faint of heart, as it requires carefully-crafted scatter files with the exact starting addresses and lengths corresponding to each and every piece of the stock firmware, and if you mess up by even one byte, you will very likely hard-brick your phone. For even more heart-pounding excitement, the way to get a custom ROM on here is not to use this tool, but to pop into an advanced mode and specify where to start writing (if you're curious, it's 0x2d80000 and no, that's not a typo) and with what file.
The purpose here is to flash a custom build of TeamWin recovery, known by its uncomplimentary acronym TWRP. And *this* involves dissecting the machine, removing its battery, holding VolDown, and hooking it up to a PC via USB cable, *in that order.* Somehow, Flash Tool is able to write to the device even though it's powered off and battery-less.
From here, disconnect from the PC, hold VolUp and Power, and select Recovery boot. After about 30s, TWRP will load, and you can pull up ADB in your shell, place the device in sideload mode, and "adb sideload /path/to/lineageos-14.1.zip," which goes a hell of a lot faster than you'd expect it to. But there's a catch: if you reboot now, you'll go into an endless bootloop, where the phone won't go past the Motorola logo. If you don't have a stock ROM or, preferably, a Nandroid backup, this is game over.
Turns out you *also* need to install SuperSU, and you need to do it in a special way: while in TWRP, pop a terminal, and do "echo SYSTEMLESS=true>/data/.supersu" before adb-sideloading a known-good SuperSU .zip onto the phone. The output will be quite verbose, and it will warn you that 1) on reboot, the device will likely restart at least once and 2) first boot will take "several minutes."
They're not kidding. I lost count of the exact amount of time, but I believe LineageOS sat there blowing bubbles to itself for a good 15 or 20 minutes, and I was literally seconds away from forcing a power-down and starting the entire process again with a stock ROM. It also takes well over a minute to boot; I counted 33 sets of right-to-left bubbles at the LineageOS loading screen per bootup, and that's after a good 30 seconds of the phone sitting at the Motorola logo with a nice fat warning about how the device can't be verified and might not work properly.
Yeah, that's the point: from Google's PoV, it's *not* working properly, because LineageOS seems not to have all that spying junk on it. I didn't even flash a GApps zip; instead, first thing I did was to sideload an FDroid archive, which is something like an open source version of the Play Store. Everything I need is on there and more.
So far, I am loving this thing. I've been zipping all over downtown Milwaukee looking for a new place to lease the last couple of days, and there is nothing like having a portable MP3 player for those long rides. And get this: after using it to play music for a good 3 hours, *the battery was still at 95% from a full charge this morning.* That is *nuts.* The Moto C Plus punches way, way above its weight with the proper love and attention paid to it.
So if anyone wants a good budget phone to run LineageOS, Resurrection Remix, etc on and doesn't mind doing some nailbitingly-scary stuff with direct flashing, I can heartily recommend the C Plus (NOT the C, that thing is junk). Happy flashing, everyone :)
Crazed girls flood Parkland school shooter Nikolas Cruz with fan mail
Mass murderer Nikolas Cruz is getting stacks of fan mail and love letters sent to the Broward County jail, along with hundreds of dollars in contributions to his commissary account.
Teenage girls, women and even older men are writing to the Parkland school shooter and sending photographs — some suggestive — tucked inside cute greeting cards and attached to notebook paper with offers of friendship and encouragement. Groupies also are joining Facebook communities to talk about how to help the killer.
The South Florida Sun Sentinel obtained copies of some of the letters showing that Cruz, who had few friends in the outside world, is now being showered with attention.
(Note that I'm still using iOS 10.0.1. In general I am quite hesitant to update any of my software if I'm happy with the version I've got.)
I will attach a sysdiagnose log when I get home this evening.
Summary:
This only happened to me once during the most of a year that I have owned my iPhone 7. It is likely to be quite difficult for you to reproduce.
The combination lock screen and home touch sensor were unresponsive, leading me to believe that my unit was hung.
Pressing the side button once - to turn off the video - then again - to turn the video back on - restored normal operation.
Steps to Reproduce:
Log into an iPhone 7.
Configure your device to use the six-digit combination lock.
Use some apps for a little while. Mostly I use Safari and the Music app.
Press the side button to darken the display.
Press the side button again to light up the display.
Press the home touch sensor to display the combination lock screen.
Touch all the buttons. There is no response.
Touch the home touch sensor. There is no response.
Press the side button to darken the display.
Press the side button again, to light up the display.
The combination lock screen now works normally.
Expected Results:
The buttons on the combination lock screen would respond to finger touches.
Actual Results:
None of the buttons on the combination lock screen responded to touches.
Version/Build:
iPhone 7 Model MNA62LL/A
iOS 10.0.1 (14A403)
Configuration:
256 GB Flash
Tresorit Launches Campaign To Build An End-To-End Encrypted Social Network
The new technology that aspires to #DeleteFacebook for good (Mastodon)
At the end of these charts, you can see a small spike in Diaspora users.
It might all be in the name. People/"dumb fucks" will sign up for a "Facebook", but "Prevaat"?
I have been at the C++ again. After a few years I have been slowly managing to persuade people that directly testing (using TDD) the C++ code is a good idea.
Also, I have tried to put my C smugness and arrogance away in the spirit of doing things "the right way" i.e. in C++ and the way the earnest and eternally vigilant members of the C++ Inquisition would recommend.
A couple of weekends ago I was on a fairly long train journey so for entertainment I reacquainted myself with the C++ Frequently Questioned Answers and laughed out loud a couple of times much to the bemusement of Mrs Turgid.
I had been asked to supervise a much younger and inexperienced member of the team. He had too much to do and so I was asked to pick up some work he had started. Young people today... So I extracted some of his code into independent methods and put them under test with CPPUNIT which involved hacking on some nasty ANT build scripts (don't get me started...) just to add a few .so files to the linker command line. The build scripts are so bad that it takes upwards of 45 seconds to compile, link and run the unit tests (200 lines of code).
Now to the fun, std::map. Why oh why oh why? Well, because the STL and these are "algorithms" and they've been developed by people much cleverer than you and so they won't have bugs like the ones you would write yourself and they have performance criteria and they use templates so you get type checking at compile time and blah blah blah...
Yes, well, nobody expects the C++ Inquisition. Their main weapon is type safety and code reuse. OK, their two main weapons are type safety, code reuse and generics. Hang on, that's three. I'll come in again. Nobody expects the C++ Inquisition. Amongst their weapons are type safety, code reuse, generics, multiple inheritance, virtual methods, references, the STL... You get the idea.
And what was std::map being used for? To store pairs of strings and integers (hex) read out of an ASCII configuration file. How was the file parsed? sscanf()? No, some fancy stream object with operator<<. And what were the ASCII strings? Names of parameters. And there was a third column in the file that specified a width and was summarily ignored by the parser. And what about the names of the parameters? Well, they were looked up in the map at run time, hard-coded, to pull the values out of the map and put into internal variables with all kinds of shifts and shuffles on byte order. And what if the user changed the names of any of the parameters in the file? Yes, what indeed. The user will be editing this file.
Now I do need to use some sort of dynamic data structure myself in this project. I need to map strings to integers, but with integers as the keys this time. My table needs to be populated with the names of files read from a directory and the files sorted in order. If I were doing this in a sane language like C it would be relatively straight forward. Anyway, we're in C++ land now and the C++ Inquisition are in attendance. So I thought I'd take a leaf out of their book and use std::map<uint32_t, std::string> table or something (note the code is infected with stds all over the place, another cool feature) so I decided I'd better read the documentation. I thought I might use the insert() method and check for duplicate keys in the map. Nope, template error. It seems one must use operator[] but that doesn't check for existing keys, it just overwrites them. The suggested remedy? Ah, scan the entire map from the beginning each time to make sure the key isn't already there. Doesn't it throw one of these pesky exception things? I thought they were the Modern Way(TM)?
::iterator is fun. Try to iterate over an empty map, or to an entry that isn't there. How do you detect it? Well, ::iterator is some kind of pointer (you get at the data with ->first or ->second) so you might compare with NULL (sorry, 0 nowadays) but no way because operator== is not defined. The best advice is not to try to iterate over an empty map or to dereference an iterator that doesn't point to anything.
I could have read my file names into a (sorted) linked list checking for duplicates along the way. It would have been less than 50 lines of C, and I could have written it and tested it in the time it took me to get angry about C++ all over again.
The word is chagrin. I have wasted very precious time and haven't even got any working code.
Edited 20180328 to use proper escape codes for angle brackets.