When I was in college, someone with the surname O'Dowd decided to spell it O Dowd on the poster, because "the computer puts red lines under it". Weirdly, my computer now is doing the opposite.
Isn't export a beer? And this tariff stuff. Do I have to pay taxes on my screenshot now?
No Dave I like it the way I do it, it works for me and I kind of like the squiggly lines.
Yeah. If it isn't actually accompanied by emotions that suggest a cause, you really might want to see a doctor about that. If you also sleep on your side, go for the home sleep study if offered, it's worlds more convenient.
verb
move (something) into a different position with a jerk.
travel by hitch-hiking. informal
obtain (a lift) by hitch-hiking.
fasten or tether.
harness (a draught animal or team).
noun
a temporary difficulty or problem.
a knot of a particular kind, typically one used for fastening a rope to something else.
a device for attaching one thing to another, especially the tow bar of a motor vehicle.
an act of hitch-hiking. informal
a period of service. informal
Slanguagely: "There is a hitch in your get-along", implying "there is a difficulty with your system/process/activity"
I won't argue that the usage can change, and I could see how it could also be used to imply that one's posterior moves in a pleasing manner, but in my experience it has only been used to indicate an issue:
Marjorie Kimmerle & Patricia Gibby, "A Word-List from Colorado," in Publication of the American Dialect Society (April 1949) has this entry for the term hitch:
hitch: n. A crick ; a limp. Used only in the expression "He's got a hitch in his git-along." Said of horses and people. OED, A limp, a hobble, an interference in a horse's pace.
Which experience would this be? That is a Stack Overflow link you posted. But I would expect such a footless prescriptivist to behave in just so ill informed a manner; excuse my short patience, I understand this actually is your best that you're showing.
Imagine an AI recipe building app that helps you create a recipe with certain ingredients, then generates an image of what the final product might look like.
Debian code won't converted into Java bytecode, though, so it won't run on the JVM. If it's the ARM version, it'll probably just run directly on the CPU.
Can you point me at what you mean? I'm not immediately finding something that indicates that it is not fit for this use case. The fact that bad actors use it to resist those who want to shut them down is, if anything, an endorsement of its durability. There's a bit of overlap between resisting the AI scrapers and resisting the FBI. You can either have a single point of control and a single point of failure, or you can have neither. If you're after something that's both reliable and reliably censorable--I don't think that's in the cards.
That's not to say that it is a ready replacement for the web as we know it. If you have hash-linked everything then you wind up with problems trying to link things together, for instance. Once two pages exist, you can't after-the-fact create a link between them because if you update them to contain that link then their hashes change so now you have to propagate the new hash to people. This makes it difficult to do things like have a comments section at the bottom of a blog post. So you've got to handle metadata like that in some kind of extra layer--a layer which isn't hash linked and which might be susceptible to all the same problems that our current web is--and then the browser can build the page from immutable pieces, but the assembly itself ends up being dynamic (and likely sensitive to the users preference, e.g. dark mode as a browser thing not a page thing).
But I still think you could move maybe 95% of the data into an immutable hash-linked world (think of these as nodes in a graph), the remaining 5% just being tuples of hashes and pubic keys indicating which pages are trusted by which users, which ought to be linked to which others, which are known to be the inputs and output of various functions, and you know... structure stuff (these are our graph's edges).
The edges, being smaller, might be subject to different constraints than the web as we know it. I wouldn't propose that we go all the way to a blockchain where every device caches every edge, but it might be feasible for my devices to store all of the edges for the 5% of the web I care about, and your devices to store the edges for the 5% that you care about... the nodes only being summoned when we actually want to view them. The edges can be updated when our devices contact other devices (based on trust, like you know that device's owner personally) and ask "hey, what's new?"
I've sort of been freestyling on this idea in isolation, probably there's already some projects that scratch this itch. A while back I made a note to check out https://ceramic.network/ in this capacity, but I haven't gotten down to trying it out yet.
