No, but I do think it is likely that someone might find this while looking for the kinesis keyboard, a popular product which has been on the market for 34 years.
3,638 karma · joined March 3, 2009
No, but I do think it is likely that someone might find this while looking for the kinesis keyboard, a popular product which has been on the market for 34 years.
I saw some comments from people against a proposed data center at the site of an old power plant. I pointed out that it was a mile from anything. Someone replied saying that that was still too close, and that they wouldn't want to live 50 miles from a data center.
We are 20 miles from Ashburn.
I just couldn't seem to hold a pen or pencil the right way and would always fall behind following along with the rest of the class. I was forced to spend hours at home with worksheets tracing over letters. I was led to believe that if I couldn't write properly I would be a complete failure.
It turns out being able to use a computer and type quickly was a more useful skill.
That's $159.89 in today's dollars.
It is trivial to switch between gaming mode and desktop mode. I'm not sure what point you are trying to make here.
The Zig implementation is literally still there.
You can make predictions of what might happen in the future, but hard to take the rest of the article seriously when it has the basic facts wrong.
> Without them, your system accepts arbitrary data from the public network.
Neither of these features change if you are accepting arbitrary data from the public network. They limit what an exploited process can do. It's explained properly in the 'Security' section, so I'm not sure where this came from.
I briefly looked at localstack to see how they implemented the Kenesis api and other than a `KINESIS_ERROR_PROBABILITY` option to simulate rate limiting, they did not implement any of the constraints.
Containers ran using docker are called containers, not dockers.
$ zramctl
NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 zstd 3.8G 2.3G 13.2M 17.2M 4 [SWAP]
2.3GB of 'a's that gets compressed down to 20MB.Yeah! Telling people what to do is rude!
> Anyone still using Linux on the desktop in 2026 should switch
Oh.
* They have full sized HDMI ports
* They will happily run using any random old USB charger and not overheat.> without a bulky expensive receiver box
A "receiver" has been one of the standard options for making bookshelf speakers work for more than 50 years. A receiver is also not expensive. You can get a basic used one for under $100. I paid $30 for a perfectly working 5.1 Denon receiver with HDMI.
Your problem is that you aren't even using "Modern" AV stuff. If you were, your speakers and TV would both have HDMI Arc ports. Arc has been a thing since 2009.
> That's harder than it sounds though because you have to navigate the menu blind using short and long button presses with the one button.
Or you could unplug it and plug it back in.
If they added latency to all packets then London would still have the lowest latency.
pattern_start = 1 if half_digits == 1 else 10 ** (half_digits - 1)
when 10 ** (half_digits - 1)
is fine.You were misinformed if you thought using rsync required setting up an rsync service.
# copy all files
COPY . .
# install Python with uv
RUN uv python install 3.13
# run build process
RUN uv run --no-dev sus
This adds the entire repository to the first layer, then installs python, then runs the build which I assume will only then install the dependencies. This means that changing any file in the repository invalidates the first layer, triggering uv reinstalling python and all the dependencies again. The correct Dockerfile would be something like # install Python with uv
RUN uv python install 3.13
# copy info for dependencies
COPY pyproject.toml uv.lock .
# Install dependencies
RUN uv whatever
# Copy over everything else
COPY . .
# run build process
RUN uv run --no-dev sus> What's the big deal that you need to call hard drives by an acronym that doesn't even mention that they're drives? No duh, of course the drives are on a network, and of course they store data.
See the problem?
Frigate is not "Cameras". Not all cameras are networked. Not all cameras record. Not all software that integrates with networked cameras is NVR software.
SELECT *
FROM passwords
WHERE (password LIKE '%password%') AND (password LIKE '%123456%')
ORDER BY user ASC
INTO OUTFILE '/tmp/res.txt'
Query id: 9cafdd86-2258-47b2-9ba3-2c59069d7b85
12209 rows in set. Elapsed: 2.401 sec. Processed 1.40 billion rows, 25.24 GB (583.02 million rows/s., 10.51 GB/s.)
Peak memory usage: 62.99 MiB.And this is on a Xeon W-2265 from 2020.
If you don't want to use clickhouse you could try duckdb or datafusion (which is also rust).
In general, the way I'd make your program faster is to not read the data line by line... You probably want to do something like read much bigger chunks, ensure they are still on a line boundary, then search those larger chunks for your strings. Or look into using mmap and search for your strings without even reading the files.