> Then keeping on top of the news for the rest of your life to see if your password manager is going down the gurgler or been hacked. Also, will my passwords be available when I travel to a country with restricted internet? Who knows. Can I export my passwords to any other password manager or a text file if I need migrate? That's part of the research needed to even get started using a password manager.
These are pretty much the exact reasons I created https://github.com/conradkleinespel/rooster. It's a simple password manager for the command line. It's offline. It's open source. It's stable. It can export passwords to plain text in different formats.
And its feature-set is intentionally limited, so I can maintain it with little work, to avoid it going down the gurgler. It's been available and maintained since 2015.
DNS history is really interesting for a variety of reasons.
I've seen it used to try and circumvent Cloudflare firewall rules. Some people don't replicate the firewall rules on the servers behind Cloudflare. If they've ever pointed their DNS to their servers directly before turning on Cloudflare proxy and you have that old IP address, then that IP address has value. White hat security firms for instance pay for that information when running audits.
I will sign up, curious to see where this project leads you.
Thanks for the API details, will discuss this with my teammates.
I'm working on https://datafragment.com with a couple colleagues, and domain monitoring is definitely one of the things we'd like to try and sell to prospects.
What are some best practices for portability of passkeys?
I've built me a little password manager (namely https://github.com/conradkleinespel/rooster) and wonder if I could make it support passkeys, at least as a backup solution to the likes of 1Password.
While I totally get the usefulness of passkeys, I feel like having a backup of some sort is needed, in case the device breaks, gets stolen, etc.
You could also register an account at https://chatgpt.com and ask it to answer specific questions you have. Although it is not always 100% accurate, it is a large portion of the time.
Deploying FLOSS software on your own infra can also be a good way to contribute something back: there are usually some things you need to do for your setup that aren't yet covered by the project itself. Eg, I just deployed an open-source RSS reader on a private k8s cluster and didn't yet have a Helm chart. So I will make that open source for whoever wants to deploy that same RSS reader on k8s without having to reinvent the wheel.
Deploying everything on k3s running on dedicated servers has also been a great way to better understand how Kubernetes works. Coming from the AWS world, it's an interesting challenge—there's so much I have to figure out now that AWS used to handle for me (PKI, load-balancing, private DNS, etc).
Learning new things is my biggest motivator. A day during which I learn something new is usually a good day.
Recently, I've been working with two former colleagues to build a search engine that indexes the entire web's HTML—a fascinating technical challenge on its own. Equally intriguing is figuring out how to attract our first customers.
I'm working on a product that may allow you to find competitors' customers through a search engine for the web's HTML. If your competitors happen to put specific HTML in their customers' websites (some HTML tag, a JS library, etc), you could get a list of prospects, which could help validating your idea for specific products.
Recently, I've been using HN RSS (https://hnrss.github.io/) to get alerts when specific keywords get mentioned on HN. Really useful tool! The underlying data comes from Algolia's HN search engine (https://hn.algolia.com), which is neat to run some searches and understand which keywords can be interesting to follow.
Thinking about following Subreddits with filters on keywords through RSS, instead of regularly checking into Reddit, to save time and cut through the noise.
If you have a niche SaaS product that somehow embeds in your customer's website, I've been working on a search engine that can help find your competitors' customers. It lets you search over the web's HTML code, basically. While this doesn't let people find you, it can help you find them.
There are a couple other companies in this space, with data focused on specific markets (US, Europe, etc). So you could find one that suits your geography.
Another thing you can do to find people interested in what you offer is following RSS feeds for keywords of your choice. HN RSS (https://hnrss.github.io) is particularly cool for HN! Tools like RSS Bridge (https://github.com/RSS-Bridge/rss-bridge) and Morss (https://github.com/pictuga/morss) can also help to get RSS feeds from websites that don't provide them and only provide a very trimmed down ones.
While I agree that for user-facing APIs, serverless can both help handling load spikes and keep costs low, how would serverless help with spidering and indexing?
Spidering and indexing are processes that would most likely run continuously for any search engine like Google or Kagi. There is always data to update and new web pages being created.
We've been building https://www.datafragment.com, a tool that can help you get prospects for your product. It lets you search the web's HTML code.
Some of our current users use it to find Wordpress websites with specific versions of Wordpress, others to find websites that use niche-market tools, ones that are not covered by incumbents such as Wappalyzer or BuiltWith. We're currently focused on the French market.
Curious to hear your thoughts, if you are looking for new ways to find prospects.
Because wireguard is UDP and only responds to valid requests, there isn't any open port from the outside. Not even ssh.