Since well before the pandemic, I've have dual 28" 4K screens on my desk. When ordering them, I liked the fact that they had the same pixel pitch as my 14" 2K laptop screen. One monitor was like a borderless 2x2 grid of those laptop screens.
I found myself repositioning things so that one is in front of the keyboard as a primary screen and the other is further off to the side as a secondary dumping ground. I found myself neglecting the second display most of the time so it was just a blank background. Eventually, I noticed I wasn't even using the entire primary screen. I favored a sector of it and pushed some windows off to the edges.
Ironically, with work from home, I've started roaming around the house with the laptop instead of staying at my desk. So I'm mostly back to working in a 14" screen with virtual desktops, like I was 20 years ago. I am glad that laptops are starting to have 16:10 again after the long drought of HDTV-derived screens.
The popular HTTP validation method has the same drawback whether using DNS or IP certificates? Namely, if you can compromise routes to hijack traffic, you can also hijack the validation requests. Right?
1) How to secure routing information: some says RPKI, some argues that's not enough and are experimenting with something like SCION (https://docs.scion.org/en/latest/)
2) Principal-Agent problem: jabber.ru's hijack relied on (presumably) Hetzner being forced to do it by German law agents based on the powers provided under the German Telecommunications Act (TKG)
Well, not exactly in that there are cultivars and farm differences. In that way it is a little bit like grape wine, where different processing can produce very different wines from the same grapes, but there are also differences in grapes that can come through within a style.
In a way, yes; Wuyi rock oolong will be different than a high mountain Taiwanese oolong. But what most people think of as green vs black tea, they don't realize that it's the same exact plant. Camellia sinensis has only 2 cultivars, var. sinensis (the main one) and var. assamica.
This is quite incorrect. Of the top 10 planted wine varietals in the world [0], all ten are red grapes to red wine or white grapes to white wine:
Top grape varieties by planted hectares
1. Cabernet Sauvignon - red grape, red wine.
2. Merlot - red grape, red wine.
3. Tempranillo - red grape, red wine.
4. Airén - white grape, white wine.
5. Chardonnay - white grape, white wine.
6. Syrah - red grape, red wine.
7. Grenache Noir - red grape, red wine.
8. Sauvignon Blanc - white grape, white wine.
9. Pinot Noir - red grape, red wine.
10. Trebbiano Toscano / Ugni Blanc - white grape, white wine.
There are some wines which are produced with red grapes which are not left on skins so there is no impartation of red colour, but they are really not common and the result is most of the time a bit closer to a light rose than what would be considered a white wine. Perhaps the only style that would be semi-frequently encountered are some French Blanc de Noirs wines, various champagne examples being the most common of these. (And of course standard champagne itself, but I am not sure if that is really considered a white wine). Still, rare. It is also not possible to produce a red wine with a white grape, there is no colour in the skin to impart.
I feel like some of these proponents act like a poet has the goal to produce an anthology of poems and should be happy to act as publisher and editor, sifting through the outputs of some LLM stanza generator.
The entire idea using natural language for composite or atomic command units is deeply unsettling to me. I see language as an unreliable abstraction even with human partners that I know well. It takes a lot of work to communicate anything nuanced, even with vast amounts of shared context. That's the last thing I want to add between me and the machine.
What you wrote futher up resonates a lot for me, right down to the aphantasia bit. I also lack an internal monologue. Perhaps because of these, I never want to "talk" to a device as a command input. Regardless of whether it is my compiler, smartphone, navigation system, alarm clock, toaster, or light switch, issuing such commands is never going to be what I want. It means engaging an extra cognitive task to convert my cognition back into words. I'd much rather have a more machine-oriented control interface where I can be aware of a design's abstraction and directly influence its parameters and operations. I crave the determinism that lets me anticipate the composition of things and nearly "feel" transitive properties of a system. Natural language doesn't work that way.
Note, I'm not against textual interfaces. I actually prefer the shell prompt to the GUI for many recurring control tasks. But typing works for me and speaking would not. I need editing to construct and proof-read commands which may not come out of my mind and hands with the linearity it assumes in the command buffer. I prefer symbolic input languages where I can more directly map my intent into the unambiguous, structured semantics of the chosen tool. I also want conventional programming syntax, with unambiguous control flow and computed expressions for composing command flows. I do not want vagaries of natural language interfering here.
If the threat is observation and tracking, you really want to turn off all radios, right? Cellular, wifi, bluetooth, NFC. Otherwise you are hoping some anonymization/obfuscation is preventing your signal from being correlated to those captured at other locations and times.
If the threat is self-incrimination after the fact, you also don't want to carry any device that is determining and persisting its own location info. Don't track your protest as a fitness activity on your GPS sports watch...
In my western US dialect, it is abnormal to use it as a subject-verb-object (SVO) construct. I have to guess at intent.
For me, there are three idiomatic forms:
1. Using "lag behind" gives a target/reference as a prepositional relationship, not as an object of the verb "to lag".
2. Using "caused to lag" allows one to specify a causal agent, but again not as an object of the verb "to lag".
3. Using "lag" alone is a subject-verb construct, leaving an implicit target/reference from context expectations. A coach or supervisor might scold someone for lagging.
As a bit of a tangent, I actually wonder if the etymology of "to lag" is more Germanic than some people assume. The verb lagern has many uses for placing, storing, and leaving behind. It's where our English concept of a "lager" beer comes from too, referencing the way the beer is fermented in (cold) storage. If this linguistic connection remained fresh, we might think of an SVO construct of lagging as the opposite of the intent in this article. The leader would lag the follower by leaving them behind!
I think the weirdest I encountered was Apollo Domain/OS. But SPP-UX was close as a microkernel with an HP-UX compatible personality on top.
But in some sense, every high-performance platform back then was an abomination. Whether it was the variant of AIX on an SP2, the weirdly unique Irix versions that seemed to exist in each Origin system at each national lab, or the painfully slow fork/exec on a Cray T3E frontend system when compiling apps.
Right up until it becomes clear that they will only be issued to ubermenschen, who are identified by capricious processes meant to both obscure corruption and instill fear due to their apparent randomness.
A wonderful sonic experience from ritualistic handling of a vinyl disc in a paper envelope?
Little do they know, the true sonic experience comes from wetting the disc with a special felt pad and watching the stroboscopic markings on the edge of a turntable platter...
I found myself repositioning things so that one is in front of the keyboard as a primary screen and the other is further off to the side as a secondary dumping ground. I found myself neglecting the second display most of the time so it was just a blank background. Eventually, I noticed I wasn't even using the entire primary screen. I favored a sector of it and pushed some windows off to the edges.
Ironically, with work from home, I've started roaming around the house with the laptop instead of staying at my desk. So I'm mostly back to working in a 14" screen with virtual desktops, like I was 20 years ago. I am glad that laptops are starting to have 16:10 again after the long drought of HDTV-derived screens.
reply