thewisenerd

6 ms·

31.
by thewisenerd 1y ago
i see the complaints around URL length limits and i raise you.. storing the entire state in the hash component of the URL http://example.com/foo#abc since this is entirely client-side, you can pretty much bypass all of the
32.
by thewisenerd 1y ago
they recently had an incident with front door reachability, wonder if it's back. QNBQ-5W8
33.
by thewisenerd 1y ago
i guess that depends on what you mean by url-safe uuidv7 (-) and nanoid (_-) have special characters which urlencode to themselves. none are small enough that you want someone reading them over the phone; but from a character legibility, ul
34.
by thewisenerd 1y ago
mirroring all the comments about this _needing_ to be an extension.. in theory, one should be able to extract the "rule" definitions [1] and have it run with a conn str; instead of this _needing_ to be an extension. in practice th
35.
by thewisenerd 1y ago
can't wait for solutions of a similar nature around 2038-01-19 a free 68 more years! (hopefully nobody optimized for the 1 signed bit when allocating memory tho)
36.
by thewisenerd 1y ago
> Kotlin’s suspend modifier may now be applied to test and lifecycle methods. thank you!
37.
by thewisenerd 1y ago
relevant: Litestream: Revamped (99 comments) https://fly.io/blog/litestream-revamped/ https://news.ycombinator.com/item?id=44045292
38.
by thewisenerd 1y ago
and then you write `.chunked(list)` so you can write `.map { query(list) }` instead of `.map { query(it) }` :) i wish there was an unused lambda parameter warning..
39.
by thewisenerd 1y ago
> kube-proxy supports only basic algorithms like round-robin or random selection this is "partially" true. if you're using ipvs, you can configure the scheduler to just about anything ipvs supports (including wrr). they re
40.
by thewisenerd 1y ago
we have the same issue with HTTP as well, due to HTTP keepalive, which many clients have out-of-the box. the "impact" can be reduced by configuring an overall connection-ttl, so it takes some time when new pods come up but it work
41.
by thewisenerd 1y ago
not easily compressible, i guess?
42.
by thewisenerd 1y ago
if you paste contents which contain a very particular string ("intends to sue the human race for stealing our honey"), the contents are replaced with the phrase "the bee movie script? really? how original"
43.
by thewisenerd 1y ago
you mention traces but the documentation only specifies metrics and logs https://docs.claude.com/en/docs/claude-code/monitoring-usage am i missing something here? or is this a case where they were lazy to do
44.
by thewisenerd 1y ago
> To be clear, I would expect a moderately intelligent teenager to be able to find two lists and compare them. If an intern gave me the same attention to detail as above, we'd be having a cosy little chat about their attitude to wor
45.
by thewisenerd 1y ago
i think “$proj - implements the redis protocol” are going to be as ubiquitous as the things which claim to be “S3 compatible” idk if redis labs (the organization aka big bad) are going to patent the “protocol” to disallow clones (or they’d
46.
by thewisenerd 1y ago
sidenote: Azure's PostgreSQL doesn't provide you with superuser, and afaict, you cannot assign pg_read_all_data / pg_write_all_data without it.
47.
by thewisenerd 1y ago
recently pulled the trigger on a migration out of jdk8 we decided to bite the bullet and do 21 instead of 17; one of the reasons being 25 being just around the corner. as far as i can tell, the biggest hurdle is 8 to 11 (with the new module
48.
by thewisenerd 1y ago
that said, it's _really_ easy to have executables against random sdist with `uv run --with`. here's something that i was writing just yesterday: #!/usr/bin/env bash PYSTABLE="3.13" SERVER=&qu
49.
by thewisenerd 1y ago
specifically for python packages, while it's lightweight, shipping the kitchen sink (uv) is a no-go so, it's a venv, with the pinned dependencies installed [0], a random example of how this looks like, here [1] (specifically for u
50.
by thewisenerd 1y ago
sidenote: when do you think they're going to coax GitHub to transfer the `x` username? https://github.com/x/
51.
by thewisenerd 1y ago
this is so future 'git diff's when adding new parameters don't look bad i wonder how many default formatting decisions are made this way (including go fmt, etc)
52.
by thewisenerd 1y ago
i've been using jj for the past few weeks on a feature heavy project. my entire "workflow" is no more than these 4 commands, rinse and repeat: jj new main@github jj describe jj git push -c {prefix} jj git fe
53.
by thewisenerd 1y ago
ah; understood. assuming PEM leakage aside the scope of the exchanged token is the scope of the installation (org / repo); thereby limiting exposure already to further reduce the scope of exposure, the jwt would've needed to be ex
54.
by thewisenerd 1y ago
even if they did not have the PEM file left in the environment, the token is still widely scoped and has the same scope as the PEM what i'm clearly mis-remembering is being able to exchange the token for a smaller scope e.g., hey~ sign
55.
by thewisenerd 1y ago
global scoped installations or keys always scare me for this reason i believe the answer here was to exchange the token for something scoped to the specific repo coderabbit is running in, but alas, that doesn't remove the "RCE&quo
56.
by thewisenerd 1y ago
i can see this in the settings page for a profile under the section "Bypass Age Verification" https://my.nextdns.io/$id/settings
57.
by thewisenerd 1y ago
love litestar.. working on migrating a couple of internal consoles to it from fastAPI. the docs could use some love though. i feel most of it is references [1], the "how to"s could be better. inb4, "where pull request",
58.
by thewisenerd 1y ago
this reminds me of public repos of pass [1] i've seen in the wild same issue of intimacy, the paths aren't encrypted. [1] https://www.passwordstore.org/
59.
by thewisenerd 1y ago
isn't upgrading node going to ba bigger challenge? (if you're on a node version that's no longer receiving maintenance)
60.
by thewisenerd 1y ago
t1: select for update where status=pending, set status=processing t2: update, set status=completed|error these are two independent, very short transactions? or am i misunderstanding something here? -- edit: i think i'm not seeing w

More ›