that's not entirely true: if you look at the manifest on the github repo you can see that it only requires the `tab` permission, which, when installed, will make the extension seem quite safe, since it should not have access to the content of your pages
they say:
`This also means that, unfortunately, the bug will not work on stable builds of Google Chrome since the release channel is set to the proper value there`
So it's only working on Chromium, a way smaller attack surface than the whole Chrome users
Heroku has been around for almost 20 years, Vercel was Zeit ~10 years ago, and they both have always been widespread solutions, I wouldn't say that that there is hype only now
I cannot vouch for laravel cloud or void, since I've never used them, nor I will comment on Deno/Bun since they are far more recent
On dot matrix and impact (like daisywheel) printers, there were sprockets along the side edges of the paper so that the tractor part of the printer could advance the paper after a linefeed.
It's sometimes called 'listing paper', as it was commonly used to print out listings of your code :
Also known as "Continuous Stationery" (one of my Father's customers companies was even called that) because each page was joined via a perforated line or "fanfold" as it was folded into the box with alternating left-right folds along the perforation just as a paper fan is folded.
Often the holes for the tractor feed were also separated from the main part of the page by a perforation so that one could tear it off to leave a more-or-less pristine letter (or A4 over here) page of content.
Fiddling with the left-over narrow strips of hole-punched edging paper was one of those universal habits that you don't even notice until long after it's gone.
(Edit: _a_ I just realised I replied to the wrong parent post and _b_ now I'm wondering if you're somebody I know!)
That's hilarious! When I mentioned the joy of messing with those strips of holes from the paper I was thinking of a specific occasion in a very dull lecture (business studies?) when I built a small paper boat out of them and you and Phil (I think) sitting in the row behind me said it was the only interesting part...
As Pratchett said, "We've all passed a lot of water since those days..." :D
Epson LX300 was on my wish list for a long time. I didn't have the money at the time, then inkjet happened and the matrix printers became extremely expensive here.
you're completely right. but most italians will never admit it, shunning all of the alternatives.
the strange thing is, we are used to different grapes varieties that are used to produce different wines, and everyone knows which tomato goes in a sandwich, which ones are better in a caprese, which for tomato sauce. but we are all fine with not knowing which kind of coffee we drink, and not knowing how it was treated...
that's why in Italy it's really rare to find someone that drinks coffee as it is, usually we add either sugar (or honey) or milk in order to mask the fact that coffee here tastes too burnt and bitter.
only in the past few years specialty coffee is starting to appear in the bigger cities, and I'm finally getting used to drink coffee after a whole life of tea with milk and the occasional macchiato caldo (espresso with a dash of hot milk), unless when abroad
i tried to acquire the taste coffee and honey. never succeeded. though it should be noted that I used acacia honey which is quite acid itself. so yeah, it was a dumb exercise. now I got no time to explore coffee anymore. as long as the coffee tastes bitter and a bit sweet AND goes well with cig, then I'm fine with it.
you can remove the `prima` from the italian version: it's implied by the use of past tense and it sounds really bad in italian.
if you want to emphasize the `before`, you can use: `ha già detto addio troppe volte` instead
They do host some data, but they delegate a lot of connections as well. One of their biggest products is bot mitigation, where they'll inspect incoming connections/traffic and pass them through if they don't seem to be bots.
But i think they terminate the SSL connection, and then re-establish a new one right? It's not like your backend server didnt know it's been MITM'ed. I suppose they should've named MITM as Surprise-MITM.
