Nice, and I like the idea that the past is fixed, but ... is there a way to define the point of rollover to the next day? My "days" sometimes end at 0:50 for example and not at 23:59. So I might summarize the day a bit after midnight.
Days "roll-over" when you sleep, so it should be safe to rollover notes which haven't been edited for 6 hours. That way there is no fixed rollover time.
If needed you can easily remove colored borders first (trim subcommand with fuzz option) or sample only xy% from the image's center, or where the main subject might be.
My first thought: a rather strange copy of the en.wikipedia.org/wiki/Pillsbury_Doughboy
Google's Android robot has a much better design, IMHO. And I remember the Amazon box version of https://en.wikipedia.org/wiki/Danbo_(character) and Arielle Nadel's photo stories "365 Days of Danbo" with it. Can't imagine that with the Apple Dough boy..
And the eye's periphery, while it isn't sharp, is highly sensitive to movement. Which is "obvious" if you ponder the question where dangerous things appear first. Thus things dangling from the rear mirror in a car are a bad thing, they need (subconscious) attention.
The cone cells in the eye's center are color sensitive, but need a lot of light, while the rod cells at the edges are highly sensitive to motion, even in low light. And that might be one of the reasons why flicker is strenuous for the eyes. Funny side effect is that looking at stars in the night sky seems to work better when you look slightly besides a star, I guess that's because then the low light parts take over.
Ah, yes, After Dark, with the "Lunatic Fringe" module, which was fun (and was a time sink ;-0). And what I would like to see again is the "Stained Glass" module which produced phantastic visual effects when tuned a bit.
and many more countries. They all need a caretaker, or else they degenerate into rubbish.
In France I stumbled upon one during a holiday trip, it was located in an old phone booth. Hmm, I must have a picture somewhere in my photo collection, …
"In France I stumbled upon one during a holiday trip, it was located in an old phone booth"
Those are pretty common in (eastern) germany, they were empty for a while after the telephones went out of service and then before demolishing many got turned into little libaries. I really like the idea and exchanged many books.
We heat up unskimmed milk, add oatmeal, let them soak for at least 10 minutes. Then serve them and pour a little bit of cold milk over the cooked oatmeal. Plain, or add some fresh fruit, nuts, berries to taste.
Yes, some patterns of speech are recognizable … The "That's LLM generated" pattern is one of those. And while I can understand the motivation behind this, I find it more irritating now than LLM texts, if these contain useful information, which make me curious.
This text made me curious, I liked the approach the author has taken. And it made me think how I would do it. My first idea would be to use ImageMagick to render text and then use ImageMagick's https://imagemagick.org/script/compare.php to somehow calculate the risk of confounding glyphs.
>I agree that mandatory developer registration feels too heavy handed, but I think the community needs a better response to this problem than "nuh uh, everything's fine as it is."
OK, so instead of educating stupid (or overly naive) people, we implement "protections" to limit any and all people to do useful things with their devices? And as a "side effect" force them to use "our" app store only? Something doesn't smell that good here …
How about a less drastic measure, like imposing a serious delay for "side loading" … let's say I'd to tell my phone that I want to install F-Droid and then would have to wait for some hours before the installation is possible? While using the device as usual, of course.
The count down could be combined with optional tutorials to teach people to contact their bank by phone meanwhile. Or whatever small printed tips might appear suitable.
reply