I downloaded a copy of Mimestream (link) to see how it performs when setup with my Google account. It have to admit, there have been some big improvements, in particular support for Google Contacts. i had a check of the Mimestream roadmap (link) and it appears that they’re considering support for not only Contact management (beyond the basic integration so far) but also support for Google Calendaring. I’ve put my 5 cents worth in and suggested they also provide support for the Google Keep API so then it can integrate with Google using the APIs provided by Google (link).
Long term I would love to see Mimestream fill that role similar to how Mail/Contacts/Calendar/Notes integrate with iCloud or how Microsoft Outlook app integrates in with Microsoft’s Outlook in the cloud. I believe that Mimestream has a good base to build on because they’ve decided to build it from the ground up using Swift because long term, in my no so humble opinion, Apple is going to eventually get Swift and Swift UI to a point of maturity that they’ll have an UI and language API that spans from workstations all the way down to watches which will eventually supersede AppKit/UI Kit in the long term with Catalyst (running iPadOS apps on macOS with minimal changes) is a stop gap measure in the mean time (in much the same way that with WinUI you can mix and match which makes migration a lot easier rather than telling programmers to throw it all out and start again).
One thing I have done recently was turning off DPI (Deep Packet Inspection) since it really was of no benefit to me other than having a cool break down in the form of nice graphics of what type of data I was transferring which came at the cost of latency, speed and I found at times it could be a big iffy (stalling) but that being said I still have my security set to its maximum setting. I’m looking forward to the next version of Unifi OS 1.11 which will include WPA3 support, improved firmware for the UDM’s wireless networking module etc. Although there are Wi-Fi 6 devices out there, I am waiting for the technology to mature and for the finalised specifications to make their way out to devices (most of the current ones are based on the draft standard which may cause problems as seen in the past with iterations). For me the interesting part will be the 6Ghz support that comes with Wi-Fi 6E in terms of potential bandwidth improvements (particularly important when one is on a gigabit fibre connection).
More leaks regarding the Pixel 6 are making their rounds with an indication that it won’t include the sort of X1 cores that are found in the Exynos 2100 and Qualcomm 888 – rumour has it that’ll include 2 x A78, 2 x A76, 4 x A55. For me, those would be good enough for the vast majority of people (aka normal people who don’t whip themselves into a frenzy over specifications) and I wouldn’t be surprised that by dropping the X1 cores it has enabled them to keep the price low – I wouldn’t be surprise if the Pixel 6 is only slightly higher than the Pixel 5 and the Pixel 6 Pro being slightly higher than that again. There is a good chance that we might see a sub $1000 phone which will mean it won’t be completing at the flag ship level but rather going for that premium mid range segment which is where all the excitement is at the moment then add to that the rumours of 5 years worth of updates, it sounds like I need to start cracking and saving up money to buy it – I’ll end up buying it through Amazon but I maybe lucky and find that Kogan offers it or even better if Google sells it directly into New Zealand like the did back in the days of the Nexus 6p.