If you are seriously considering SpiceDB and our approach to telemetry bothers you, please do us a favor and open a GitHub issue (or find an existing one if someone beats you to it) and include your perspective. We want to be respectful while also maintaining a feedback loop to be able to improve what people use. We do a lot more than I've seen others do to communicate when/when/how/why we collect and how to re-configure (off or collect it yourself) so those who wish to opt-out can immediately. If this is not the right balance or our solution is just entirely wrong, it's important for us to understand why and improve rather than alienating folks.
Make telemetry strictly opt-in then, that's really the only respectful way to do it.
Everything else is sophistry.
Not singling you out either, too many projects do it by default, yours at least makes it obvious here that you do and how to turn it off https://authzed.com/docs/spicedb/ops/observability#telemetry so kudos for not hiding it in the basement behind a "Beware of the Leopard" sign.
For open source projects I just find it more offensive, I'd expect closed source projects to do it by default (but I expect less of them to start with) but for open source it rankles much more.
With opt-in on an open-source project I get to choose to help contributing something back (telemetry data) to help the project.
Opt-out telemetry is not compatible with respect. It also adds an obstacle when I try to advocate the software to friends and coworkers. I have to warn them about it in advance, which is often where it ends because we’ve been burned in the past with other software adding extra things to their telemetry that weren’t there before, or changing the name of the environment variable that disables telemetry, or someone on the team does something that accidentally causes data to be transmitted unintentionally.
I wrote a tutorial about how you can import Strudel without embedding it. They publish JS modules so you can just import them and build an app around them: https://good.vibes.diy/blog/you-can-just-make-music
I ended up quitting Kagi over that and built my own search engine for my own use. But if the comments here are correct that Kagi are trying to build their own index that replaces all the others, that would be great news. It seems lots of people still like Kagi regardless of that too.
For anyone trying to build their own, turns out SQLite can take you much further than it seems you should ever be able to. A metasearch layer fills in for everything else.
I am trying this. I noticed I only browse a subset of sites a lot. Also HN works wonders for finding links. But how do you get around all those bot measures/cloudflare nowadays? It seems only google IPs get a special pass.
Yep, discovering that you only need a subset of sites is the key. In my case, I still had my entire Firefox browsing history in its SQLite cache, so I tried to index every page I'd ever visited, and had a list of the domains I actually visit. It's the same insight Brave Search had - they used to be a metasearch engine, but they built their own index until they could serve 99% of queries directly, even though their index was vastly smaller than Google or Bing.
I struggle with indexing too. I don't do any crawling, just indexing from sitemap.xml files or URLs I add to the queue manually. Also I'm indexing from my own residential PC, not a hosted VPS. Something that helped me was Cloudflare's new crawler API. For all the sites where Cloudflare blocks you, just use their API instead:
Also for a quick index bootstrap, the Curlie database can be useful. It's the old DMOZ directory, the open Yahoo competitor, with 1.4 Million websites. A lot of the links are now very outdated, but it can be useful, and it's less than 500MB when converted to an SQLite database.
Unfortunately, that's nearly identical to the text from September 2024, with the only change being an increase in the number of external search sources:
I'm aware of their Teclis index, I used to be a paying API customer. Teclis is very small. It's primarily an index of indie blog websites (smallweb) mostly crawled via RSS feeds. That itself is a very cool idea, and a great supplemental index to have! But it isn't the kind of index that could ever replace their Brave / Yandex / SerpAPI dependencies. The Teclis API is even supplemented with results from Marginalia Search, a much larger index created by one person with less funding.
There's some technical info here on how Teclis is indexed, eg Readability.js for content extraction & Elasticsearch for the full-text indexing:
Kagi's short infoline about index distribution sounds new to me though. I would love to see a blog post from Kagi about that & where they're at with query coverage.
I’ve seen that a few times. Had to disable the TUI mode because clicks to focus the terminal window were being interpreted as an approval even though the click was nowhere near the question being asked. I’ve also never chosen to enable auto mode but somehow it is on and approving shell commands I didn’t want approved. Scary since I’ve caught it adding things like auto approve flags to terraform apply commands.
I’d really suggest to run Claude Code in a sandbox! Anthropic can’t be trusted.
I run it on Mac with sandbox-exec. No access to AWS, database, pretty much just files in the current folder. Even if it goes rogue, it can’t do much harm.
In addition to privacy I’d like to be able to burn as many tokens as the hardware will let me 24/7 without getting a surprise bill at the end of the month. I don’t care if it is slower that the cloud, I’m not in a hurry.
The best kind of correct.
reply