We definitely plan to enable effortless transformation of any block into an object, for example, by adding a tag to it or simply by mentioning it in another object 'transclusion'.
We also have plans to develop a simpler local API and a local AI helper that will be able to assist you with import/export tasks in ways you might think of
Thank you for the input! If you're looking for a clean space, you can easily create a new one by clicking on your profile icon in the panel at the bottom. It will contain only a few sets. You can always delete spaces that are no longer needed.
If you need a simple notepad, there are better tools out there. Anytype is more suitable if you're looking to create something like a database or knowledge base, not just a list of notes.
The next year we are working on simplifying the user experience and introducing multiplayer+communication
Yes, we are aware that there is a steep learning curve before you reach the point where you feel it's worthwhile. It's absolutely true that if you need a tool solely for note-taking, Anytype might not be the best option. We envision Anytype as a tool for knowledge management and communication (we're launching multiplayer early next year). One of our biggest internal projects is to simplify the user experience. With each new release
Thanks for the feedback about the screenshots! We'll get that fixed.
The license is somewhat vague. Essentially, it means you can use the software as a tool for your revenue-generating business. You have the option to use it for free if you self-host. Alternatively, you can choose a paid membership in our network, which eliminates the need for you to handle maintenance. The license specifically restricts selling the software to others without ANY coop consent.
I'll try to clarify: For syncing objects (anytype native data structure), we use IPLD in conjunction with our own networking layer. For file synchronization, however, we opt for IPFS without libp2p, since a faster method is necessary to improve the user experience. This strategy ensures our file storage is compatible with the public IPFS network and incentive-based storage networks like Filecoin and Arweave. Additionally, it provides a significantly faster experience for our users now. This approach works much better for cases when you have many small files ( what often the case in pkm and communication).
I wouldn't say it's extremely slow. While benchmarks can be useful, they often don't align with real-world experiences. What exactly are you comparing? Is it just rendering time? Have you considered a user's workflow, which might involve navigating through several pages or objects? In reality, we've attracted many users because they find 'Notion' to be slow, and many appreciate the speed of Anytype. Based on this, I believe it's not fair to give Anytype the same rating as Notion in your diagram. Also, I would assign a higher rating to Bear and Craft; their desktop apps are faster since they are native.
There is significant room for improvement, and we're already steps ahead in this area with our native mobile clients that sync peer-to-peer. Try our Android app and see for yourself. I hope that within the next three years, we'll excel with native desktop applications as well.
The value proposition of Plume looks good; I've left my email.
On the p2p topic: Our protocol is p2p and it's already working well in local networks. You can experience the magic yourself: install Anytype in local mode, create a space, and fill it with some data. Open the mobile app and log in with the same phrase, and your data will be synced without any central server, immediately! Isn’t it magical? The network is needed for backups and to solve the closed laptop problem. You can always self-host a network. We believe it's important to give people the ability to be free from a service provider
On the topic of e2e encryption: All your data in Anytype is encrypted at rest; only the indexes of this data (which are created and used locally) are not encrypted. We have plans to also encrypt the indexes. Currently, we assume that the majority of users employ full disk encryption, and if your machine is compromised, it is likely that malicious software can read memory and, therefore, access the keys. Could you please elaborate on the significant vector of attack, so we can consider this case?
Regarding the license, we have covered our logic here: https://blog.anytype.io/our-open-philosophy/. We are passionate about open source, and for some projects, it’s the only viable option. That's why our AnySync protocol and data format are MIT licensed. The clients are currently under a source-available license, as we are still exploring ways to make the ANY association and contributor ecosystem sustainable. Still researching…
Thanks for your kind words towards us and congrats on your progress!
1) We don’t offer a browser version. Instead, we have an Electron-based cross-platform app that works on Windows, Linux, and macOS. We also have two native mobile apps for iOS and Android. Creating a browser version is challenging for us because our business logic and local database rely on a middleware library written in Go. Currently, the only feasible approach is running it in WebAssembly (Wasm). We hope to make a browser version available in the future.
2) No. It’s not build with anytype, as we do not have a web version:)
It's a matter of taste, and ours differs. You can establish trust by going to GitHub, checking the code, and compiling it yourself. In my humble opinion, trust and taste aren't closely connected.
By default, your account is created on the machine. You can use it without connecting to any network. We allow you to sync notes in a peer-to-peer way in local networks, or over the Anytype network (or your self-hosted network) via the internet. Currently, you can sync notes among your devices. Soon, you'll be able to collaborate with others using end-to-end encryption. I can't agree that the claim about the key is vague, as there is documentation and code on GitHub. You can check it, and we are happy to hear arguments.
We are genuinely implementing a local-first approach. Why do you have doubts? We have a clear description of the data format, which is MIT licensed. Feel free to write and read. We hope that data adaptors will soon be available with the help of the community. You have full control over your data. Compile your version, and that's it.
Most of our repositories are MIT licensed, which holds significant value. Some of our repositories are source-available. We believe we are building an open-source product, and we reserve the right to define what 'open-source' means for us. Our only prohibition is against competitors making minor modifications and then selling our product. Our position on this is clear. We recognize that our definition may not align with others' perspectives here, and we are open to understanding that. However, labeling our approach as dishonest isn't something we consider accurate. To avoid any confusion for those who uphold the traditional notion of 'open source', we will change the term 'open source' to 'open code' on our website.
> Then how can I use the app without creating first an account and space which will sync my data without even asking? You talk about trust and offline-first, but the first thing you do is uploading data and don't even talk about it.
It's not an account you create in a classical way using a server. It's locally generated data wallet ( we need it for encryption and sync). We talk via on-boarding that your wallet will be synced, and that your data is encrypted only with the key generated on your machine. It's for people who don't want to mess with self-hosting. If you want you can make your build from GitHub, disconnect sync, or just self-host yours. This way our promise works.
> BTW Don't reinvent menus. I just now realized that File->Close does not actually close the app, like in any other app. And for whatever reason, there was no information about the App still running. Kinda sus..
Because we want to provide other organizations with the opportunity to offer paid sync services, we needed to incorporate the concept of a network into the license. We crafted the license with that consideration in mind