Our team has received multiple inquiries about our service’s compliance with GDPR. We answer these individually, but here’s a short-form of the types of questions that we answer.
Deprecation of TLS version 1.0
For most people, it’s been looming about pretty silently over the past few years, but TLS v1.0, the oldest and earliest version of Transport Layer Security is considered deprecated. The Payment Card Industry (PCI) data security standard (DSS) version 3.2 from April 2016 recommends full deprecation by the end of June 2018.
In compliance with these standards, while originating from the payment card industry, widely regarded to as a guiding standard for other industries, Kolab Now has disabled support for TLS v1.0.
Why? What does that mean?
Use Privacy Badger
Privacy Badger is a browser extension by the Electronic Frontier Foundation, that prevents sites from tracking your visits across the web. It’s available for Chrome (the most popular browser among our visitors and customers), Firefox (second) and Opera (nowhere to be found).
Kube on Mac OS
After a week of getting to grips with how Qt development on mac works and wrangling various build issues, I am pleased to finally report success =)
Kube on Mac OS is alive!
Kube’s gained some manpower
Around FOSDEM this year we have found some fresh manpower for Kube! Please welcome Rémi, who is doing an internship with us, and is working on Kube during that time. He was quick to land his first few patches and is now busy implementing the first few steps for CalDAV based calendaring support.
I for one am exited to see what he will come up with =)
Adding a Little Byte of Transparency
I’m considering adding a little bit of transparency to how, and perhaps how well, Kolab Now infrastructure is run, or is running.
Find your mails with fulltext search
The most recent addition to Kube is fulltext search. It’s a complex enough topic that we don’t really want to implement it in our key-value store that we use for the rest of the data, which is why we’re using Xapian to do the heavy lifting.
Kube is an offline capable client, and as such we also want search to work without an internet connection. However, we naturally can only search the data that you have available locally. Normally this means we’ll have subject and recipients indexed for all your mail, and the complete content for all mails that you have every viewed/downloaded.
In the long run we’ll want to extend that with server-side searching for when you’re connected to the server, so that you could indeed search through all your data, without having to first download it all. But that is a task for another day.
So here it goes; Fast as you type searching of your emails:
For more info about Kube, please head over to About Kube.
Bitcoin Payment Problems
In recent times, Bitcoin payments have suffered three major blows;
- Our payment provider now requires customer’s wallets to use a Bitcoin Payment Protocol, while some wallets are simply not compatible,
- Transaction confirmation times have increased, and then increased some more, both inconveniencing our users and increasing the underpay/overpay problem,
- Transaction fees have gone through the roof, making the use of Bitcoin less and less attractive, especially for smaller transactions.
Obviously, this is causing some of our customers some grief. Some of the customers that choose to want to use Bitcoin payments exclusively will actually use profanity in expressing their frustration over these changes, but our support staff does not deserve that. I, for one, will defend my staff and cause those customers to find themselves on the losing end of this “conversation”.
Using and abusing memory with LMDB in Kube
When synchronizing a larger folder in Kube, you’ll notice that the memory usage is growing at an alarming rate.
Surely something must be wrong? Let’s dig into that.
Continue Reading “Using and abusing memory with LMDB in Kube”
Testing and prototyping in Kube
To build a reliable product it is essential that we build ways for us to ensure that what we build also works as expected.
In its simplest form that means that you try what you build, the assumption being that if it works for you, it works for everyone.
- By now we all know that “works for me” is not enough, but there are also a variety of additional challenges;
- It’s not enough to only test when a feature is first implemented, the tests need to be repeated regularly to ensure nothing breaks that once worked.
- There is a balance to be struck between over- and under- testing. Tests need to be of high quality and have to be maintained with the system, otherwise they become a burden instead of an asset.
- The right things need to be tested. Test things that are too trivial and you end up with loads of tests with little value (but a maintenance cost). Test things that are too complex and your tests become fragile and don’t tell you what broke, making fixing it harder.
- The testenvironment needs to be realistic enough so we test the right things (e.g. we don’t want to test the internet connection typically), yet also removes the bits that we don’t have under our control, so we test our system only. That ensure that the test remain reliable and are fast to run (so they are run regularly).