nikisweeting

6 ms·

61.
by nikisweeting 11mo ago
ArchiveBox open source does not, but I have set it up for paying clients in the past using TLSNotary. This is actually a very hard problem and is not as simple as saving traffic hashes + original SSL certs (because HTTPS connections use a s
62.
by nikisweeting 11mo ago
I've been mulling over how to take ArchiveBox in this direction for years, but it's a really hard problem to tackle because of privacy. https://docs.sweeting.me/s/cookie-dilemma Most content is going behind l
63.
by nikisweeting 11mo ago
btop is good, I like 'glances' the best though because like 'atop' it actually highlights whatever problem is most likely to be causing lag at the moment, and it breaks out docker containers into a separate section and l
64.
by nikisweeting 11mo ago
my personal theory is that archive.is has paid subscription accounts (legit or via botnet) to most of the major news outlets and edits the html to make the sites look not logged in. I wonder if they do it by hand or by doing something like
65.
by nikisweeting 1y ago
Security and auditability is not the core problem, it's versioning and uninstalling. https://docs.sweeting.me/s/against-curl-sh
66.
by nikisweeting 1y ago
Nah ULID guarantees some extra stuff as part of its spec beyond UUIDv7, including true sub-millisecond monotonicity and a ceiling of 7ZZZZZZZZZZZZZZZZZZZZZZZZZ. You can convert to base32 to get some of the benefits but they're not exa
67.
by nikisweeting 1y ago
Heh BrowserBase and Browser-Use exist specifically because this is a harder problem than it looks. Any approach will work for the first couple actions, that hard parts are long strings of actions that depend on the results of previous actio
68.
by nikisweeting 1y ago
You need to convert it to perserve the timestamp info correctly so that a ULID library reading the base32 format would reproduce the same timestamp.
69.
by nikisweeting 1y ago
ULID is the best balance imo, it's more compact, can be double clicked to select, and case-insensitive so it can be saved on macOS filesystems without conflicts. Now someone should make a UUIDv7 -> ULID adapter lib that 1:1 translat
70.
by nikisweeting 1y ago
I must have a very different brain shape than the author. Color processing is for me subconcious, I don't get the "color overload" situation at all because my brain has hardware accelerated it long ago, there is no concious l
71.
by nikisweeting 1y ago
https://github.com/browser-use/macOS-use https://github.com/browser-use/browser-use
72.
by nikisweeting 1y ago
workflow-use is currently just an early implementation of some of the ideas for repeatable workflows, there's not much secret sauce to worry about from an IP standpoint yet. you could also use deepwiki to safely paraphrase it / ge
73.
by nikisweeting 1y ago
Nice work! You should reach out to one of the other team members on discord / X about it and make sure they see. (I am on pat leave right now and trying not to open Slack)
74.
by nikisweeting 1y ago
How does this stack up against unikernel-based VM snapshots?
75.
by nikisweeting 1y ago
https://turso.tech I think attracts a lot of the people trying add new features / improve SQLite rough edges
76.
by nikisweeting 1y ago
Deepwiki was instrumental in our refactor of a large codebase away from playwright to pure CDP @ browser-use. Huge props to the team that built it, I regularly refer to it as one of the few strictly net positive AI coding tools. The auto-ov
77.
by nikisweeting 1y ago
Oh no I would hate to have to depend on my package manager and build system
78.
by nikisweeting 1y ago
go fmt, cargo fmt, deno fmt, dart format, etc. it's hardly a new trend to ship a formatter with an all-in-one package manager for a language. It's convenient for new projects to not have to set up an additional dependency.
79.
by nikisweeting 1y ago
whoops pasted the wrong link and it's too late to edit. meant to link to the updated article section here: https://browser-use.com/posts/playwright-to-cdp#:~:text=Sele...
80.
by nikisweeting 1y ago
That's why we support Brave, Edge, Ungoogled-Chromium, and our own custom Chromium fork that we're working on. Just because we only support Chromium doesn't mean we're pro-Google-dominance. There are enough Chrome forks
81.
by nikisweeting 1y ago
That's not really true, https://github.com/daijro/camoufox is at parity with patchright on stealth, it's just that Firefox has way less market share so it's not worth the >2x maintanance effort for us
82.
by nikisweeting 1y ago
no one is proposing removing the sub-commands, only adding a shortcut that calls both
83.
by nikisweeting 1y ago
fwiw `ruff format` includes nearly all the black rules by default / supports a superset of black's options https://astral.sh/blog/the-ruff-formatter
84.
by nikisweeting 1y ago
Package managers providing a shortcut to call a standardized formatter is a very popular feature in many languages, also not hard to understand the appeal: - cargo fmt - go fmt - deno fmt - dart format
85.
by nikisweeting 1y ago
You realize this is just a shortcut for one of those "time-tested" options, right? ruff format is already widely used.
86.
by nikisweeting 1y ago
and stop removing extra leading whitespace before inline comments (#7684)
87.
by nikisweeting 1y ago
Of course we already have it automated in pre-commit checks, I'm just mildly annoyed that it's two different commands in the first place (though I'm sure there is some good historical reason). The distinction/ordering be
88.
by nikisweeting 1y ago
native messaging is a huge headache to set up reliably across all the OSs and (often headless) chrome setups in our experience, that's why we've avoided it. Just using some remote endpoint message bus service is an easier solution
89.
by nikisweeting 1y ago
As long as it does `ruff check --fix; ruff format` internally and not just one or the other, then I'm happy. Tired of running 2 commands every time.
90.
by nikisweeting 1y ago
While that is the origin story of Playwright in 2020, that's no longer really true. Puppeteer is alive and well and arguably moving faster than Playwright these days because it's updated in lockstep with https://github.

More ›