Latest feedback about some significant drawbacks

[Jeroen]

While you have carefully chosen your words they do come across a bit harsh and demanding (like @qualquertipo said be kind ), eventhough you have a few solid points of concern.

1. Blocks should be Objects
This is a thing that has been requested and Anytype responded. I don’t remember but I believe they are looking into it (no promises). Also, I disagree that this means blocks as well, but I understand why some people might think so. Or maybe hoped that would include blocks (which I would love and bring Anytype to the next level).

2. Tags should have nested hierarchy
I don’t think they should but having the options would be nice. Also there have been many suggestions about a master tag lis or better handling of tags including nested tags. Which also is something being worked on.

3. Notes should have Templates or be redesigned
I don’t really understand this, why? You can simply use an object type of your own choosing and assign templates to it. That type can be set as the default and you just not use the Notes type.
As I replied in this topic Let users change locked types - #12 by Jeroen I believe that Note is one of the default objects that has more things working in the background (like layouts) and that is why we cannot remove or edit them. This is more a design descission which you can agree with or not.

4. Sets are useless
Strongly disagree! Sets are great and useful to me as well as collections. Even in their current state! I use both a lot! Agreed that they lack some features and require some quality of life updates but both have their place in my workflow at least. Sets where the number 1 request more then a year ago before they got added.

Edit: I just red this post:

Merge collections and sets

Hi there, great discussion. Our current vision (subject to change): Search will be more powerful and basically will incorporate all abilities of current sets (filter/sorts/etc.) Sets will be basically saved search requests, maybe we even will rename them Collections will be primary way to work with many objects in more “traditional” data base way with a sprinkle of Anytype flat structure

5. Inability to change our Recovery phrase
Strongly agree! But this is already in the works see this awnser in Learning more about Security Phrases - #3 by AnyChris

@Angelo

Yes, Key (Recovery) Phrases are vastly superior to traditional passwords by margins of magnitude.

We want to add something like 2FA (Two-Factor Authentication) to improve security. It will not only protect accounts better but also give owners a way to change their Recovery Phrase if it’s lost or compromised.

I feel a lot of your points are valid but almost all of them are still being worked on or improved in some way. So my advise would be to have some more patience and don’t use Anytype as your daily driver. Stick with Evernote, Obsidian or another app that does suits your needs better. You would be supprised how fast development goes when you are not focussed on it.