Hacker Newsnew | past | comments | ask | show | jobs | submit | berndinox's commentslogin

„Because thousands of contributors develop and access open-source code, it’s easy for vulnerabilities to open up and go unnoticed.“

And closed-source fortunately has no security holes at all. Sarcasm off!


Vaultwarden for Passwordsync and Wallabag for Bookmarks.

Con: no „real“ Firefox Sync - Pro: no „real“ Firefox Sync - it works on any device with any browser, data is self-hosted


I set up Wallabag recently for this very purpose. My initial impression is that it mainly focuses on fetching and storing the content itself, rather than giving you an easy to navigate bookmark library. So it's great for, eg, saving long-form articles and blog posts, but not so good for bookmarking interactive/dynamic content.


True, its better suited for saving „Text“. I dont have that much bookmarks tbh


https://github.com/getmeli/meli

But is searching for maintainers


Agree, Fly.io is great for such usecases. Is there any CDN/Proxy solution or guide available for fly?



Not via SMS, anymore


While i‘m an absolut cloudflare fanboy, one wording sounds wired to me:

„Zero Trust Cloudflare Tunnel“

… at least you have to trust cloudflare, fully!


And, in turn, while I loathe Cloudflare, I would say that's perfectly reasonable; "Zero Trust" means that you distrust the network and possibly the clients, but you generally still have to trust, at the very minimum, something to provide identity verification, and usually some sort of network proxy in front of the actual application. So long as every connection is securely encrypted in flight, I'm pretty sure it still counts as Zero Trust.


"Zero Trust" is about as good a name as "Serverless". Yeah, it kind of makes sense if you understand it already, but at first look it's pretty dumb.


Zero trust is a whooly term which means different things to different people, it's more of a strategya and principles than a technology. Ultimately you will have to trust something and we want to make that as small trust relationship as possible. For me, the best way is to use open source and only have trust of central key infra (the control plane/PKI) while ensuring all connections and anything that wants to attach goes through its own process of bootstrapping trust. No connections should be made to the controller or on the data plane unless endpoints have bootstrapped trust.

I work for a company that has created exactly this and we open sourced the core tech. It allows anyone to put programmable, pirvate (outbound only) connectivity based on zt principles into any app (sdk), host (tunnler) or network (edge router). It can support any use case across access, multi-cloud, IoT, and more.

Check it out - https://openziti.github.io/


Cloudfare's gonna check out all your girlfriends for you Cloudfare won't let anyone dirty get through Cloudfare's gonna wait up until you get in Cloudfare will always find out where you've been


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: