Thank you for letting me know, I’ll update both links asap.
nsa.tech is a domain name I acquired some years ago for fun and I’ve been meaning to use for some time now. I understand that most people know of an agency that uses the acronym but hey! We’ve been thinking “network secure access” around the office ;)
I want to build an open protocol for building p2p apps that don't rely on any central servers. For this I'm looking into BitTorrent's DHT for discovery, libp2p for connection and encryption. The idea is that you own your identity, you pick who you trust, and nothing gets stored on servers you don't control. It will work for things like messaging, photo sharing, and private networks where you want real decentralization/federation, not just a blockchain slapped on top of the same old client server model.
The infra intended here exposes TCP and/or UDP connections, it is protocol agnostic; so end-user apps can use smtp, http, activity pub, at protocol, etc.
I am going for an infra that can scale by leveraging the DHT as DNS and p2p for end user apps/apis.
I've been enjoying working with LLMs for some weeks now, and realized that as faulty as these can get, asking them to put material in place to learn some resource may be worth my time.
I am looking to learn more about Clojure, I read through it all and was happy that it ends up with examples for an actual api app. I may ask for more in depth lessons as I find more suitable apps to be built.
This looks fun! But the fact that the self hosted version lacks support for some core apps is sad, I'd love to be able to build puter apps! Any plans for an app store-like ecosystem?
We are open to suggestions :) And the very first generation of P2P Matrix was indeed built on libp2p (and Protocol Labs led Element's Series B). However, the thought experiment here is whether we can get away without a full global P2P overlay at all in the interests of keeping it simple & stupid. We might well end up back at libp2p tho!
Some years ago, I co-founded a startup that would run workflows when email messages arrived, any email from any source was parsed and it would trigger "actions" that could include notifications - this sounds like a good use case for it! You don't need the service to expose an api to listen in, since most services end up sending email as last fallback.
Sadly no, the feedback loop with users lacked consistency and we never got around finding use cases. One of the visions for it was to help people clean up inboxes, because as you put it, some sources can get pretty spammy.
I'll keep an eye out for Cozy Watch, I hope you are successful!
> Some password hashing algorithms have a maximum input size. For example, bcrypt is limited to 72 characters.
Ahh, I was not aware of this limitation, thank you for clarifying. If I sign up for a service that does not allow up to 72 chars does it mean their hashing algorithm is of lower quality?
nsa.tech is a domain name I acquired some years ago for fun and I’ve been meaning to use for some time now. I understand that most people know of an agency that uses the acronym but hey! We’ve been thinking “network secure access” around the office ;)