I chose Tuta five years ago as a first step to de-google (not relying on Google services). Tuta also provides a free email, and the apps can be downloaded on F-Droid
chose tuta because of the convenience, the availability of official apps on all desktop platforms even with free subscription. And because of Proton's tendance to mégaloma ( Big tech tendance) they want to be on all aspects of tech that sounds too creepy for me! Do one thing and do it well! Don't try to do everything.
I switched from a t.online adress I had for ages to tuta and upgraded to paid version a few month ago, and there is nothing to regret. Works beautifully and the app is even on FDroid available. No spam anymore, love it!
encrypted mailbox and good pricing. Also use other services that offer a mailbox in addition to other things, and thought it’d be good not to have all eggs in one basket so to speak
I chose Tuta for stable native Linux mail client (and Mac/win/iOS/android), but most of all because of your great communications work with blog and social media pro European and/or independent software and digital services.
I was looking for a private email provider. I tried Proton, but between the owner's political statements and the inclusion of an AI chat project, I went looking elsewhere. That's when I found Tuta.
I chose Tuta because you truly prioritize privacy, no empty marketing promises. Your transparency, active community engagement, and EU roots make you stand out. Big respect for your team and the values you uphold!!
The bottle look so cute ^^! I chose Tuta because... Well, because what would I choose otherwise? I value myself and my data, so after a quick research I found out that Proton didn't suit me at all, but Tuta is a lovely platform that I am pleased to use everyday!
We have two accounts. One is free and the other is a paid Revolutionary plan. We have eliminated Apple and Google from our digital lives. We have always avoided Microsoft like the plague. We chose Tuta because it is simple, clear and, above all, it works. Unlike others, Tuta truly guarantees privacy and security. Bravi ! !
Been using Tutanota for well over 5 years at this point, mostly because of the privacy and overall security aspect. I've stuck around because of the company ethos, features, and awesome pricing!
My tuta address is only known by a limited number of trusted people, so unlike in my other non-gmail box no spam. De-google my family calendar is "work in progress" ... 😉
That's an easy one: I just wanted a good mail provider that didn't break the bank or pull me into its oversized ecosystem. No overly fancy gimmicks, tries their best, and continues to help privacy and Open Source alike.
because tuta has the best encryption amongs other email providers and because of their zero knowladge policy (for example tuta encrypta the header of the email, witch others don't)
porque la política está convirtiendo la tecnología en un sistema de control y explotación de las personas, al que deberíamos intentar no someternos voluntariamente.
I chose Tuta because I really believe that post-quantum encryption is important for all the digital services we use today and I really like the Tuta community ❤️
Stelle gerade genervt und enttäuscht fest dass Podigee die Kapitelmarken verfälscht wenn man automatisch ein Intro einfügen lässt. Auphonic selbst erkennt das und verschiebt die Zeitmarken. Kann doch nicht der einzige mit dem Problem sein.
Nope bist Du nicht, unter anderem deshalb bin ich auch von Podigee zu LetsCast.fm gewechselt und mache das in Auphonic alles wieder selber und vor allem richtig. Außerdem ist es deutlich günstiger, für die Größe, die ich habe und das, was ich brauche. Ich lasse das Podigee jetzt auslaufen und verlängere es nicht.
I’m getting a ton of spam on Mastodon. On the Jabber/XMPP side of things, we are doing a lot behind the scenes to combat it that regular users might not even notice.
I hope the people behind the scenes of Mastodon are working on similar things.
An open source instant messaging client. Easy to use, reliable, battery friendly. With built-in support for e2e encryption, group chats and media transfer.
I also received Spam in the Fediverse. From multiple servers, large and small. The topic is important as the Fediverse will scale and complicated because of the implied decentralized nature of it. Hence, I expected a thoughtful discussion and comparison of existing work, work in progress, current research questions and transferrable work between the two protocols.
What did I get: Absolutely thought free, cheap instances of tu quoque and demonstrations of incompetence about the subject being discussed. Do better.
Which brings us to one the most important tools to combat spam in the Fediverse at the moment: The block function.
Ich bin Fan vom Känguru und „VIEWS“ ist auch wirklich sehr gut.
Ich frage mich, ob Marc-Uwe Kling (@marcuwekling ) der Sache nicht mehr geholfen hätte, wenn er angekündigt hätte, ab morgen ausschließlich im #Fediverse zu posten.
Die meisten Nutzer folgen dem Content und nicht komplizierten moralischen Appellen.
In die aktuelle Situation sind wir aber auch gekommen, weil man sich als Nutzer keine Gedanken drum gemacht hat. Alles andere wäre wieder Bevormundung des Nutzers - der wiederum wäre verärgert wenn er es nicht versteht.
Gebe aber auch zu dass ich ein viel zu rational denkender Mensch bin und gefühlt viel zu viel Verständnis habe
Aus eigener Erfahrung würde ich sagen, dass ein zu aprupter Wechsel selten von langfristigem Erfolg gekrönt ist...ich denke, wenn einige neue Nutzer hier (zeitweilig parallel) ihre Zelte aufschlagen, sollten wir ihnen einen möglichst warmen Übergang ermöglichen... * es benötigt auch etwas eigene investierte Zeit, dieses Netzwerk besser zu verstehen und diesen "Mehraufwand" können wir nur anteilig mit Usability-Attraktivität wettmachen...
I wrote Zig bindings to quickjs-ng with 96% API coverage (~240 exported C decls) with unit tests, examples, and doc strings on all functions in less than 6 total hours with AI assistance. I never want to hear that AI isn't faster ever again. github.com/mitchellh/zig-quick…
This isn't slop. I worked for those 6 hours.
I was reviewing everything it outputted, updating my AGENTS.md to course correct future work, ensuring the output was idiomatic Zig, writing my own tests on the side to verify its work (while it worked), and more. My work was split across ~40 separate Amp threads (not one mega session, which doesn't work anyways unless you're orchestrating).
I have a ton of experience writing bindings to libraries for various languages, especially Zig. I have never achieved this much coverage in so little time with such high quality (e.g. test coverage). My usual approach is to get bind just-enough of the surface area to do my actual work and move on. This time I thought I'd draw the whole owl, because it's a new world. And I'm very happy with the result.
Anyone with experience writing bindings knows that you do some small surface area, then the rest of the coverage is annoying repetition. That's why I usually stopped. Well, LLMs/agents are really, really good at annoying repetition and pattern matching. So going from 5% API coverage to 95% is... cake.
There is probably some corners that are kind of nasty still, but I've been re-reviewing every line of code manually and there is nothing major. Definitely some areas that can just use a nicer Zig interfaces over the C API, but that's about it.
I plan on writing a longer form blog showcasing my threads, but you can at least see the final AGENTS.md I produced in the linked repo.
Mastodon desde el Administratum. Tenemos la calefacción puesta como siempre y aun así se nota que hoy no es que el grajo vuele bajo, es que se ha metido bajo tierra el muy.
Jenom jeji zadek:) Tech je tu nejvic. Litaji i vrabci, ale vcera jsem je docela vyplasil jak jsem tam furt lezl. Dnes budou mit klid, tak prileti. Oni jsou docela plachy, vrabcaci jedni. Doufam, ze to vyfoti i nejake dalsi, co jsem nevidel.
Da vergüenza ajena que Pedro Sánchez sea incapaz de publicar su propio comunicado de condena a la invasión americana sin tener a un grupo de países al lado, como da vergüenza ajena que haya tenido que unirse al comunicado latinoamericano porque ningún otro país de la UE es capaz de criticar a los EE.UU. como sí hicieron con la invasión de Iraq.
🧵 We moved from Google Cloud to Hetzner and cut infrastructure costs by 80%. Here's what I learned:
Same workloads, same reliability, actually better performance for our use case. Main thing we lost: 47 GCP console screens to find a simple setting.
GCP isn't bad - it's powerful and right for many cases. But somewhere the industry decided "real" companies must use hyperscalers. That's marketing, not engineering.
@Tutanota [1/2] I was using tuta mail. It was logged into the tuta app on my phone. Whenever I open the tuta app it automatically takes me to the inbox. I was also able to access it from the web too. But from the day before yesterday I was not able to login, it shows "invalid credentials".I tried many times carefully checking my credentials but I am not able to login. Also it does not login to my app automatically anymore. It was my primary email for official communication attached with many org
Marp (also known as the Markdown Presentation Ecosystem) provides an intuitive experience for creating beautiful slide decks. You only have to focus on writing your story in a Markdown document.
Hi. I apologize in advance if my account becomes somewhat political. I am Venezuelan, and I want to talk about what is happening in my country. I will do so from my own beliefs and political position. I am open to debate and to clarifying doubts for anyone who has them.
However, I am not open to insults, disrespect of any kind, or being called a traitor to my country. I only accept respectful dialogue here, and I thank in advance anyone who chooses to engage in that spirit.
Acabadico Babel, de Kuang. Uf, me ha flipado, genuinamente, me parece una maravilla de novela. sí, tiene sus cosas, como que la narradora es demasiado obvia a veces y tiene a explicar demasiado, confiando demasiado poco en el lector.
PERO, aún así, me ha flipado toda la novela de cabo a rabo. En tema, estilo y estructura. En general no leo libros tan largos (aunque ahora van a venir varios tochos seguidos...) y me imponía bastante. Sin embargo, me lo he bebido. Lo comencé el día 1, viajando a casapadres en tren, y me lo he acabado esta tarde.
Me encanta como el conocimiento de un campo muy concreto, la traducción, puede acabar no solo siendo un sistema de magia, sino un sistema de poder y relaciones. Que el propio sistema de magia que plantea sea en sí los vacíos del lenguaje... Mira, me flipa.
También es de los pocos sistemas de magia que he visto que, de verdad, está ahí para reforzar la trama y su mensaje anticolonial.
Me gustó muchísimo también; y la forma en que se sistematiza la traducción como un recurso a utilizar y explotar es muy interesante. Personalmente, también hice una lecutra secundaria que no sé si es porque yo siempre pienso en estas cosas, o porque realmente estaba ahí; pero el tema de la centralización, de como se controlaba la traducción desde un solo centro y así había que renovar la suscripción de vez en cuando, me recordó un montón a todo el tema de la nube y el software como servicio; y el status de los traductores me hizo pensar en la posición de los estratos técnicos (ingenieros, arquitectos...), con privilegios materiales pero explotados y reproduciendo el sistema.
Ayer un señor me ayudó a subir al tren, me buscó asiento, me puso la mano en la cabeza y me dijo "que Dios te bendiga". Y Dios me bendijo. Y ahora no sé qué hacer con la bendición. ¿A alguien más le pasa? ¿Cómo se vive estando bendecido? Es que no estoy usando bien la bendición o algo, porque los problemas que tengo son los mismos y no he notado ningún cambio.
@modulux @Nahir Bueno, la bendicióhn de Dios no pesa. A mi no me molestaría. Alguna vez me lo han hecho. Otra cuestión es cuando se meten en movidas de "eres ciego porque..." Ahí ya si saco las garras. Pero por un deseo de bendición... Con suerte funciona y consigo más hitroll o SAVE VS Spells. :P
In 1980 the United States led a boycott of the Olympic games in Moscow due to the Soviet Union's invasion of Afghanistan. Sixty countries joined the boycott.
The 2026 World Cup is mostly in the United States.
🥶 Výpočetní středisko *Jih* hlásí -16 °C. Můj skoro veterán nestartuje, takže vařím ☕ a houmrofficuju. Ale stejně budu muset do korpu nějak zajet... Tak keep ☕, bando.
A new day, and a new accessible Telegram client for Windows, TAccess. TAccess is a custom Telegram client built with Python and wxPython, specifically designed to be fully accessible for screen reader users (NVDA, JAWS, Narrator) on Windows. github.com/mlapps88/t-access-a…
TAccess v1.0.0 - First Public Release
We are proud to present the first stable release of TAccess, an accessible Telegram client designed from the ground up for efficiency and ease of use with scre...
@JamminJerry LOL - maybe. But my main concern is the flurry of Python/wxPython apps that have popped up over the past few weeks, mostly vibe-coded. Vibe-coding isn’t necessarily bad, but it often doesn’t follow clean, well-established development standards. By installing such apps, we tacitly accept that we may be subject to all kinds of expected—and not so expected—issues. Now I'm not saying this particular app is vibe-coded. But these days whenever I hear Python/wxPython, I may cringe a bit.
Also, I find it weird that its on Github, but only the releases the code isn't actually there. like it kinda defeats the purpose of putting it up on GH IMO.
@serrebi Well, if anything, I'd really like to see your RSS reader succeed. It's still a bit resource-hungry here to be honest. But the idea of a fully accessible, full-text RSS reader is always enticing.
When does it use high resources. I'm not seeing it. I have 18 cores though, so maybe that's why. I care about this though. This is one of the reasons my format was a blessing, because now I have a clean slower machine to test on.
@serrebi Let me try your latest build then for a more accurate picture and report. I'm waiting for you to add the PR there about the full-text module excluding the first paragraph on some websites.
@serrebi The latest versions should be significantly more optimized in this regard. I also experienced performance issues with Blind RSS, even on powerful hardware, which is why I tried to improve it—I hope successfully. 🙂
There is a persistent misconception among sighted developers: if an application runs in a terminal, it is inherently accessible. The logic assumes that because there are no graphics, no complex DOM, and no WebGL canvases, the content is just raw ASCII text that a screen reader can easily parse.
The reality is different. Most modern Text User Interfaces (TUIs) are often more hostile to accessibility than poorly coded graphical interfaces. The very tools designed to improve the Developer Experience (DX) in the terminal—frameworks like Ink (JS/React), Bubble Tea (Go), or tcell—are actively destroying the experience for blind users.
The Architectural Flaw: Stream vs. Grid
To understand the failure, we must distinguish between two distinct concepts often conflated under “terminal apps”: the CLI (Command Line Interface) and the TUI.
The CLI (The Stream): This operates on a standard input/output model (stdin/stdout). You type a command, the system appends the result below, and the cursor moves down. This is linear and chronological. For a screen reader, specifically kernel-level readers like Speakup, this is ideal.
The TUI (The Grid): This treats the terminal window not as a stream of text, but as a 2D grid of pixels, where every character cell is a pixel. It abandons the temporal flow for a spatial layout.
Case Study: The gemini-cli Madness
Let's look at a concrete example: gemini-cli, a tool written in Node.js using the Ink framework. On the surface, it looks like a simple chat interface. But underneath, Ink is trying to reconcile a React component tree into a terminal grid.
When you use this tool with Speakup (Linux) or NVDA (Windows), the application doesn't just fail; it actively spams you.
Because the framework treats the screen as a reactive canvas, every update triggers a redraw. When the AI is “thinking,” the tool updates a timer or a spinner. To do this, it moves the hardware cursor to the timer location, writes the new time, and moves it back.
For a sighted user, this happens instantly. For a screen reader user, this is what you hear:“Responding... Time elapsed 1s... Responding... Time elapsed 2s... [Fragment of chat history]... Responding...”
It drives the screen reader mad. The cursor is teleporting all over the screen to update status indicators, spinners, and history. Speakup tries to read whatever is under the cursor at that exact millisecond. You end up hearing random bits of conversation mixed with timer updates, making it impossible to focus on what you are actually typing.
Worse, lets pretend that you've somehow managed well with speakup so far, but that you want to do some work with nvda. Maybe paste an error you're getting on windows. So you open your terminal, ssh into your linux box, attach to your screen session and paste your text.
The result is an immediate crash of the screen reader (NVDA) or massive system instability. Why? Every time you type a character or paste text, the application triggers a state change. The framework decides it needs to re-render the interface. Because the conversation history is part of that state, the application attempts to redraw or re-calculate the layout for thousands of lines of text instantly. The more messages you have in a conversation, the more this will happen. And no, you can't just avoid this by using insert+5, the key combo supposed to avoid announcing dynamic change of content.
The Lag Loop
Furthermore, frameworks like Ink running on single-threaded environments (like Node.js) suffer from massive performance degradation when the history grows. If you paste a large block of text, the system has to calculate the diff for thousands of lines.
This causes input lag. You press a key, and you wait. You can wait up to 10 seconds for a single character to echo back. The system is too busy calculating how to redraw the screen to actually process your input.
Why The “Old Guard” Works (nano, vim, menuconfig)
Sighted developers often ask: “If TUIs are bad, why do you use nano, vim, or menuconfig?”
The answer is not that these tools handle the cursor perfectly by default. The answer is that they allow you to hide the cursor entirely.
1. Hiding the Cursor (nano, vim)
In tools like nano or vim, usability depends on turning off features that track cursor position. If you run nano with options that show the cursor position (like --constantshow), or if you use vim without specific configuration, the experience is broken.
When the cursor is visible and tracking is active, Speakup prioritizes the cursor's location update over the character echo. Instead of hearing the letter “a” when you type it, you hear “Column 2”. You type “b”, and you hear “Column 3”.
These older tools succeed because they allow you to disable this noise. You can configure them to suppress the visual cursor or status bar updates, forcing the screen reader to rely on the character input stream rather than the noisy coordinate updates. Modern frameworks rarely offer a “no-cursor” or “headless” mode; they assume the visual cursor is essential.
2. Single Column Focus (menuconfig)
Tools like the Linux kernel's menuconfig work because they enforce a strict, single-column focus. Even though there are borders and titles, the active area is a vertical list. The cursor stays pinned to that list. It doesn't jump to the bottom right to update a clock, then to the top left to update a title. The spatial complexity is kept low enough that the screen reader never gets “lost.”
3. The Lost Art of Scrolling Regions (Irssi)
Irssi is the gold standard for accessible chat, but not because of luck. Irssi was built over 20 years with a custom rendering engine that utilizes VT100 Scrolling Regions.
When a new message arrives in Irssi: 1. It tells the terminal driver: “Define a scrolling region from line 1 to 23.”2. It sends a command: “Scroll up.” The terminal moves the bits up. 3. It draws the new text at the bottom of that region.
Crucially, it handles this in a way that minimizes interference with the input line. It relies on the terminal's hardware capabilities rather than rewriting every character on the screen manually. Modern frameworks ignore these hardware features in favor of “diffing” the screen state and rewriting characters, which is computationally heavier and hostile to accessibility.
The “Stale Bot” excuse: A Case Study in Neglect
Google and the maintainers of gemini-cli pretend to care about accessibility. “Pretend” is the operative word here. If you look at the repository, critical accessibility regressions like Issue #3435 and Issue #11305 have been left to rot. There is no discussion, no roadmap, and no fix. Even worse is the fate of Issue #1553, which was supposed to track these accessibility failures. It didn't get solved; it got silenced. It was closed automatically by a bot with this generic dismissal: > Hello! As part of our effort to keep our backlog manageable and focus on the most active issues, we are tidying up older reports. It looks like this > issue hasn't been active for a while, so we are closing it for now.”
This is unacceptable. Closing an accessibility report because the maintainers haven't touched it in months is not “tidying up”; it is hiding evidence. It effectively says that if a bug is ignored long enough, it ceases to exist. It boosts the project's “Closed Issues” metric while leaving the actual software unusable for blind users.
Conclusion
If you are building for the terminal and care about accessibility, stop using declarative UI frameworks that treat the terminal like a canvas.
The “modern” TUI stack has optimized for the developer's ability to write React-like code at the expense of the machine's ability to render text efficiently.
If you cannot guarantee that your application allows the user to hide the cursor, or if you rely on aggressive redrawing to show spinners and timers, you are building an inaccessible tool.
For the blind user, a dumb, linear CLI stream is infinitely superior to a “smart” TUI that lags, spams, and scatters the cursor across the screen.
I unfortunately have not found any myself. The second your ssh connection lags even a tiny little bit, things kind of fall apart.
And cursor tracking seems hardcore in wsl for some reason? It's very weird. Or it's probably nvda not liking the windows terminal all that much... Let's be honest there too, nvda rather sucks for the terminal, as unfortunate as it is.
I use JAWS, so for me it's far easier: it doesn't crash, JAWS cursor works like a charm, I can virtualize and copy. The only thing is this cursor tracking in editors.
It is now my mother's birth minute. She's had 72 of those now. Minus 1 for the actual year, because your first birth minute happens at age zero, of course.
I am typically at least one or two decades behind on the latest memes so the fact I only heard of "six seven" about six months after it started is a personal record for me.
@archos "Vazeny pa chrchly chrchly pane! Helejte, skyt, sem se vozvozral. A skyt! naboural skyt auto! Vam auto naboural. Ja. Skyt. Sorry. Robin Bedrunka. "
@zoufalec Tak já jsem taky jednou odřel cizi auto, za stěrač jsem dal telefoni číslo. Majitel mi večer volal a vše jsme vyřídili. Pořád lepší než tohle.
@archos @zoufalec To závidím. Mně odřeli auto dvakrát, nikdy se vzkazem. Poprvé jsem to auto měl funglovku starou asi 14 dnů. V garážích v shopping parku, ale bohužel až pozdě mě napadlo, že to tam asi bylo pod kamerami…
@rholas Přesně moje auto. Měl jsem ho 14 dní a před barákem ho někdo odřel. Hlavně tam parkují jen pár majitelů bytů, takže na 100 % věděl, čí to auto je. No svině. @zoufalec @fabia_man
Fuck online dating. Some YMCA people swipe for a friend for hours now and it is not only boring but also kinda racist the way they just constantly judge on the appearance of the suggested people. These days we no longer meet to htalk, we meet to that kind of bullshit.
That's what I ask you. Something random about online dating and then friends meeting to swipe to look at peoples looks and being racists? That sounds a bit weird to me or I'm clearly missing context
@McOi Basically any online dating app these days is a feed with suggested profiles, you swipe left and right to like/unlike, very generally. So that's where the swiping comes from. And well, as you can imagine 90% of that decision whether to like/not comes from looking at the images people put on their profile there. And then of course if you're a group or random bored young adults you can make a bunch of random weird/stupid and also racist comments about said pictures.
Ah kayyyy I see. Idk where racism comes from though, thought germany is a typical lean left sosioity and any youth would call you racist rather than being one themself. But ofc things can change after 4 years, how would I know.
It still needs a lot of work, but I just used NVDARC on iOS to control my Mac using NVDARC's Be Controlled mode, to connect a bluetooth keyboard to my Mac. All on the touch screen.
Wow, processing images with M4 Pro makes quite a big difference as compared to, say, M2 pro. I just replaced ChatGPT and Gemini for VOCR with Gemma3:27B and the latency is quite quite impressive. It’s tiny bit slower, but still bearable. I am impressed so far!
I've been thinking about these things too. If people are actually using it I'll spend a little time improving it. I've also been thinking about changing it so we prep a zfs filesystem with the base and just clone it for the deployment. It's faster this way and will also be saving disk space with bclones.
Jessie Kirk • 🏳️⚧️
in reply to Tuta • • •<undef>
in reply to Tuta • • •FranzHohler
in reply to Tuta • • •Radgryd
in reply to Tuta • • •Adrian
in reply to Tuta • • •【Ｚｅ i Ｍａ】🔞
in reply to Tuta • • •Thiry Maximilien
in reply to Tuta • • •ThaMichele
in reply to Tuta • • •Jakob🇪🇺
in reply to Tuta • • •Hiki
in reply to Tuta • • •Tuta
in reply to Hiki • • •Zou
in reply to Tuta • • •qwertzalotl
in reply to Tuta • • •Micha P. Sexbeat
in reply to Tuta • • •Vojaganto
in reply to Tuta • • •Leander Lindahl
in reply to Tuta • • •I chose Tuta for stable native Linux mail client (and Mac/win/iOS/android), but most of all because of your great communications work with blog and social media pro European and/or independent software and digital services.
Looking forward to your drive (cloud) solution.
Arnaud Pz
in reply to Tuta • • •Meldriade
in reply to Tuta • • •axel.
in reply to Tuta • • •Tuta
in reply to axel. • • •Jeff
in reply to Tuta • • •Clicky Buttons
in reply to Tuta • • •Nexl
in reply to Tuta • • •L3N0X
in reply to Tuta • • •Tuta
in reply to L3N0X • • •freaeaz_
in reply to Tuta • • •Marcos Rodrigues
in reply to Tuta • • •Superboom
in reply to Tuta • • •I chose Tuta because... Well, because what would I choose otherwise? I value myself and my data, so after a quick research I found out that Proton didn't suit me at all, but Tuta is a lovely platform that I am pleased to use everyday!
Robert Rapacki
in reply to Tuta • • •Due Pazzi In Caravan
in reply to Tuta • • •nico o. s.
in reply to Tuta • • •Marcos D. Alves
in reply to Tuta • • •bookworm
in reply to Tuta • • •Sir David Nielsen
in reply to Tuta • • •Ryan Emmett
in reply to Tuta • • •Tuta
in reply to Ryan Emmett • • •🅱️eisbolCards
in reply to Tuta • • •Souljah06
in reply to Tuta • • •Lisa
in reply to Tuta • • •Lisa
in reply to Tuta • • •FrauZimorodek
in reply to Tuta • • •TwoDpadsDown
in reply to Tuta • • •Miguel Fontoura
in reply to Tuta • • •CreamofCry
in reply to Tuta • • •steppl
in reply to Tuta • • •Gert, ZL2AW 🇳🇿
in reply to Tuta • • •Tuta is just a simply to use email and calender. No distractions !!
A clear, fast, and reliable encrypted service made in Germany !
Cheers Gert
Xeronarth
in reply to Tuta • • •That's an easy one: I just wanted a good mail provider that didn't break the bank or pull me into its oversized ecosystem. No overly fancy gimmicks, tries their best, and continues to help privacy and Open Source alike.
Tuta fit to the letter in my opinion.
Eclipse
in reply to Tuta • • •Eric
in reply to Tuta • • •tyrkysovapanda
in reply to Tuta • • •Marco
in reply to Tuta • • •Manuel García Gómez
in reply to Tuta • • •Mystden
in reply to Tuta • • •