Following the topic of FHE for quite some time and I am always hoping that we get some breakthroughs regarding speed.
Seeing how this can be applied to CRDTs another awesome topic, is really cool, even if it still more theory than practice :-D
Loving these kind of apps :-)
I personally use WhoBird, which runs complete local on your android device, so it works also when you don't have internet and is available on fdroid (https://f-droid.org/packages/org.woheller69.whobird/).
Will give merlin a shot as well to see how it compares
yeah seems like at least for many that is the case. I wasn't aware that so many engines are using bing! under the hood. Afaik qwant uses their own thing and that startpage is using google under the hood, but that might have changed
Mhm tested in ff and chrome and it works fine in my site. Does it mean that the filters do not at all on your site? What setup are you using?
Ty for the feedback :-)
so if I want to sunset my api version X in 1 year for whatever reason and I am able to support an old schema X, which api X maps to, for that time period without any hassle (and not only during migration), this would be a much bigger feature / USP for me then everything else mentioned. I am really curious to look deeper into this :-)
So during migration both schemas are valid if I understood correctly?!
It would be awesome if "during migration" could be lifted to a point where it is possible to keep both schemas (old and new) for as long as I want and do migrations/transformation of incoming request (like queries) on the fly.
Then I could map my different api version to different schemas and these on the fly transformation would be able to take care of the rest in many scenarios :-)
For those use-cases I use entr (https://github.com/clibs/entr). In what sense does watchman differ to it? Didn't see anything related to this at first glance :-)
Nope. There are some concerns about using openssl for file encryption and it is generally good to be very specific about the encryption instead of using default parameters. I don't necessary share all the concerns, but it might be worth knowing them, e.g. https://security.stackexchange.com/a/182281
Still a thumbs up because all backup solutions I and a lot of my friends are aware don't cover most use cases and I am happy to see people are trying to fill some of those gaps
Some questions that weren't answered in the readme:
- What type of encryption is used exactly? Is it a simple encfs which leaks some meta information or is a container created or something else?
- Is it a full snapshop backup or does it work incrementally?
Very cool to see more privacy by default in Firefox.
It is still a lot of effort to have clear separations in every browsern...
I am using Firefox containers with the temporary containers plugins (with history deletion enabled) as well as cookies auto delete plugin (which supports containers).
Therefore, everything is usually isolated in a container inside a tab and only white listed cookies are kept in the named containers.
As a Berlin based software consultancy, we are focused on building state of the art scalable platforms using functional programming and DevOps paradigms. We believe writing software is an inherently creative craft which requires a nurturing, supportive and collaborative environment.
We exist and strive to empower companies who conduct their business according to our values: fairly, ethically, sustainably, humanly. We don’t do fossil fuels, defense nor surveillance. We celebrate diversity and especially encourage non-males to apply.
We are a team of skilled 1.) Scala developers which like to write pure functional and clean Scala code and 2.) Infrastructure engineers with a strong background in IaC and a DevOps-mindset
We are now looking for an infrastructure engineer with a strong background in IaC and a DevOps-mindset to help us build scalable and replicable infrastructures for our customers and our own products on AWS.
Our benefits
- We work 100% remotely
- Choice of equipment (Mac or Linux)
- Cross-Functional teams
- Paid Conference/workshop
- Paid co-working
- Regular on-sites
- Flexible working arrangements (between 20 - 38h / week)