1,185 karma · joined March 9, 2012
Socials: - x.com/enthdegree - enthdegree.at.hn ---
q3q.net
As someone who has only touched one once, heat guns kind of scare me mostly because the airflow is invisible. I have destroyed things with it and almost burned myself. It's hard for me to gauge if you have too much or too little heat on something. Too far away it's doing nothing and too close you're frying a piece, and there is no indication where on that range you are without some learned intuition.
I got an SL108 I'm really happy using with my 67W Anker brick (far more convenient than the FX 951 station I had to store + set up every time). I think I could do some precision work with my SL108 but if it became regular or a new project involved it I'd get something smaller, like the TS101 or similar, I guess.
closed tab.
I am going through this right now... I really wanted an 85mm 1.4G but according to reviews it will put focus completely behind the subject from f/1.8-f/5.6 when closer than head+torso distance. In headshots if you target the eyes it will focus somewhere on the temples. I have no idea if it really matters in real life. So I am stuck with the 1.8 G.
Edit: A focus screen with some kind of prism mechanism would let you manually focus, at least, by holding down DOF preview. Richard Haw describes cutting down and shimming off-body focus screens so it's possible. Actually now that I look it up, whoa, an off-the-shelf one exists on aliexpress ("Dual 45 degree Split Image Focus Focusing Screen for Nikon D1 D1H D1X F100 PR129")
- https://pbs.twimg.com/media/HFaPCStWYAAOj6f?format=jpg&name=...
- https://pbs.twimg.com/media/HFaPCO8WIAASMEn?format=jpg&name=...
- https://pbs.twimg.com/media/HFaPCPEXgAE3O4z?format=jpg&name=...
Just because this is how things are does not it's how they should be. I'm very tired.
- Getting the device's BL1/BROM into download mode (where it waits for an upload of a Preloader/BL2 from outside), for these devices itself does not involve exploits. Kamakiri is an exploit in the upload process that gives an execution point at that stage.
- The BROM on Kobos (at least the old ones, P365's) don't have security enabled as far as I know. (Unless somehow they are lying to us when we ask, which there is no evidence of). They only do some integrity checks (header magic #s, checksums).
- Security on Kobos happens down the chain, starting at the Little Kernel apparently jumped to from the Preloader. I am still learning about the Clara BW's boot process.
Kobo devices have root exposed but don't let users boot their own kernels (and the kernel they ship was not compiled with kexec either).
I really don't know the reason so many devices these days don't have an unlock method. It seems predatory. Who knows where in the chain this happens... maybe it's Kobo, or maybe MediaTek won't sell you their SoCs for mass-market devices unless you lock them.
This schmaltzy student-teacher roleplay immersion-journalism feels false and infantilizing to me. It makes me mistrustful of the text and I avoid reading essays written like it. The facts are embedded in an artificial adventure narrative as one feeds a dog a pill by hiding it in peanut butter. Why? Would the non-sensationalized, plainly framed information content be too un-stimulating for readers? Are false narratives hidden inside?
>Obama chuckled. "You mean the Chaos Emeralds?"
The article is appalling. To me it more effectively conveys his character than his ideas. Maybe for some people it really is hard to find a balance.
It would require further compiling an X server or Wayland, the Lucid GUI toolkit, freetype and fontconfig, a bunch of image libraries and maybe more stuff I don’t know about, plus of course all their dependencies.
It would likely take some effort to get X or Wayland to refresh the screen responsively, possibly using xdamage or Wayland protocol stuff to intelligently ask fbink to do limited refreshes.
The keyboard and touchscreen might be configurable but I haven’t done it. If it turns out to not work out of the box another option besides fighting drivers would be to be translate the event devices in /dev/input into virtual devices like efbpad kbreader does.
GUI emacs seems doable and requires, in my estimation, about “this project” again more work. The issues with the terminal version should probably be resolved before continuing. I’m unsure how much less responsive it will be than the terminal one.