that .it domain is kinda worrying given their recent stance on blocking or deleting parts of the internet to support the shareholders. Well, at least it’s not Spain, but do keep an eye on that.

Do you have further details on the topic? We’d like to learn more. FYI, We have a .it  domain simply because the service was born from Italians, and we are proud of the fact we built it in Italy, but the servers are in Germany

May I recommend also Cryptpad?

We might consider offering both Cryptad and NextCloud with a shared quota. Cryptpad is something we evaluated but discarded as it had a much smaller feature set compared to NextCloud and for the average user it wouldn’t have been as helpful. Our main goal is still to show that OSS solutions are a valid alternative to proprietary ones, so we need to start with services that are comparable in terms of features.

Some comments have mentioned chat. A XMPP server,

We will keep brainstorming more on the topic of Chats. But we are only going to provide a Chat service if it has a solid support for bridging with main stream chat services (opt-in obviously, we do recognize the risk they bring), we believe that it would be perceived as an inferior service if people were not able to talk with their usual friends and thus it’s better to not offer it compared to offering something that would damage the image of OSS based solutions.

FYI, in our FAQ we currently suggest communick.com for services we don’t offer like Matrix, Lemmy and Mastodon.

**Do you offer Mastodon, Lemmy, Pixelfed and Matrix Chat services?**
   At the moment InlineStyle does not plan to offer support for social platforms that already easily available to users. 
   We think it wouldn't add any value to the community offering one more node of those services. 
   For PixelFed we suggest using pixelfed.social itself, while for Lemmy, Mastodon and Matrix you can try **Communick.com** which offers those at great prices.

Absolutely. End-to-end encryption will always be high on our roadmap.

At the same time, we believe in a world where users shouldn’t have to encrypt everything just to protect themselves from the platform they’re using. Privacy should start with ethical intent, not just technical features. We don’t scan, monetize, or analyze user data. Not because it’s difficult, but because it’s wrong.

We’ve been exploring the idea of adding a chat service. But we haven’t yet decided which protocol would provide the most value for most people.

Right now, we’re considering XMPP and Matrix — both are solid, privacy-respecting options. Our goal is to offer something that lets people communicate with their existing contacts, not start from scratch.

We’d love your input: what would you actually use? What works best in your daily setup?

What’s the encryption situation for personal side of the service ie email, docs etc?

Currently, InlineStyle uses encryption in transit (TLS) across all services. We’re working on implementing encryption at rest, to ensure data remains inaccessible even in the event of a server breach.

As for end-to-end encryption (E2EE):

• Email: Not E2EE by default, but we support GPG for users who wish to secure their messages independently.
• Docs: Currently no E2EE, and we don’t plan to add it for collaborative editing (due to the technical limitations it brings).
• We are planning to introduce a dedicated “Locker” feature, where users will be able to store files with stronger protection, albeit without collaboration features.

If strong E2EE is essential to your workflow, tools like Proton Mail and Proton Drive are great choices. Our focus with InlineStyle is more on access to fediverse content and everyday convenience: a suite that works out of the box for people looking for alternatives without giving up too much convenience.