My wife and I tried to use Monica for many months in the past but had to give up because of the incredibly buggy CardDAV implementation when using iOS. Now that this has come out it seems the issue (https://github.com/monicahq/monica/issues/6175) was ignored likely because of all this work.
Have improvements been made with this in the new version?
Safari seems to have been getting more developer attention this last year. This is good but also has resulted in a number of bugs and regressions as they move fast. Same is happening on Chromium.
I likewise have been involved in a similar bizarre bug. We wrote up a very detailed report with a reduced test case but sadly it has not received much attention. https://bugs.webkit.org/show_bug.cgi?id=247020
Happy to see this announcement. I do a lot of reporting in the Noto repo's and it has been a mess with so many scripts fighting for attention, this new structure will surely help surface bugs and fixes in smaller scripts.
Google has not always given the Noto team enough resources the last few years but they have been working hard to keep up with things and hopefully this investment in the structure of the project will give it more chance of staying alive for years to come!
Just a dirty move to shove aside all of us paying Android users. Was going to look at going back to Apple for my next phone but this just brought my opinion of Apple business practices back down to the garbage heap.
I am disappointed in the founders for letting that be a part of the acquisition.
Got an invite recently, got it setup, but have had endless networking issues. Can't join any of the chat groups they advertise in the documentation.
The sheer amount of jargon you have to learn to do literally anything is insane. Nothing is intuitive, especially for someone used to a unix command line. I get upset every time I try and learn about it. All the videos about in on YouTube are 3+ years old.
Yes, I use its git feature for certain projects, and have used it for chat for a while. I have found if I come across a developer who has a profile its the easiest way to get in touch with them.
Good post, some nice lessons there for someone entirely new to this.
Perhaps a missed opportunity was not advertising the domain name during the entire video. Often a user may not have the volume up and so perhaps providing a textual call to action in the first half continuously would help with conversions?
Reading is entirely different for the deaf and is far inferior when compared to seeing something signed. Take a look at https://www.jw.org/ase for an example of how a website can be tailored for the sign language community.
Very nice, love the simplicity. Full syncing is going to be key though.
The biggest "complaint" I have after 5 mins is having a quick way to jump to a new line at the bottom. You wouldn't want to override the default of the omnibar having focus, but a simple keyboard shortcut would be nice. Currently it seems I need to tab down into the page, but then that still leaves my cursor at the beginning of the document.
It was more difficult than I had hoped to develop for. One of the biggest issues in my opinion right now is the lack of proper mobile support. The stores need to be responsive. With that said, I was able to have a discussion with their community manager and it sounds like they are working to make things better, no doubt this round will help greatly!
I am the lead developer for Treesaver (http://treesaver.net) and we have recently been working with a great team in Milan, Italy to try and offer a solution to this problem. http://savory.io
It's not perfect yet but we have a great roadmap and hope to have all the major features publishers need in the near future.