Kelson Reviews Stuff - Page 7

I haven’t decided whether Dia is an AI chatbot masquerading as a web browser or the other way around.

For now it’s in closed beta (and only on M-series Macs), but they’ve released it to anyone with an Arc Browser account. Not wanting to run it on my primary OS or log into any important accounts (Dia will look through your logged-in accounts for answers), I installed it on a virtual machine.

First impression: it really wants you to personalize it. And it really wants you to interact by chatting. Once it gets past the onboarding, the main window is a 50/50 split with the web view in one column and chat in the other. And they’ve finally implemented the UI change that big tech has been trying to do for the last 15 years: Hide the URLs. I spent several seconds looking for a place to type in the name of a website before I decided to type it in the “Ask anything” box, and was relieved that it works like Arc and I could pick the actual site from a drop-down.

But Why, Though?

The problem is that I don’t want to interact with the web through an AI chat bot.

I’ve tried. I really liked Arc Search, but I never warmed to its AI features either.

I just don’t want a generated answer that won’t tell me where to find more details, and won’t cite its sources. (I asked it why it doesn’t cite its sources, and it said it will if it has to do a web search, but not if it’s just using its training data.) And I don’t want a folksy-sounding “well, I can’t find an exact answer, but I can tell you sort of where to look for it,” I want to go to that place where I can find it.

I also don’t trust the technology yet: I don’t trust its accuracy. I don’t trust the people running it. I don’t trust the way summaries will entrench a single interpretation (just like classifying AI tends to reinforce the biases in its training data). And so much of it still relies on cloud services, meaning that your questions and answers are routed through another layer of remote computers, which need more energy and provide a nice central spot for surveillance. (This is also why I’ve avoided voice assistants for so long.) If I go directly to EFF.org, that’s between me and the EFF, but if I use Dia’s AI chat to get answers from EFF, Dia’s and OpenAI’s servers need access too. And while Dia assures you that your query is deleted immediately afterward, you have to trust them on it. And trust anyone who might eventually buy them.

And that’s not even getting into AI’s rapidly expanding energy requirements coming just at the point when the world was getting a handle on renewables, or the ethics of sourcing its training data.

Bottom (Command) Line

AI integration is the whole point of Dia. Without those features, it’s just a stripped-down Chromium browser, and not a very compelling one, either. (I’d go back to Arc or Ecosia in a heartbeat, or DuckDuckGo, and those are the comparatively bland ones. And Ecosia at least tries to work for the environment.) With the AI, it’s another panopticon funnel.

Maybe it’s just not my thing, or I’m just being a digital curmudgeon. (Maybe.) Though it is kind of funny that people are interacting with computers by typing text commands to get responses again. Of course, terminal applications are (usually) more deterministic about what you get back from them!

Update (September 2025): Atlassian is buying The Browser Company, which means it’s following the typical startup-to-acquisition path. Maybe the pivot to AI was sincere, but it certainly looks like it was an attempt to raise their profile among potential buyers.

Back when I was first using Mastodon on my phone, I tried a few apps and settled on Tusky. I was impressed at how smoothly it works, especially with multiple accounts. It’s more capable than the official Mastodon app, not too cluttered, and handles just about everything mainline Mastodon servers offer. And while it doesn’t go out of its way to support other Fediverse platforms, it does work well with other software like GoToSocial and Snac.

They recently polished the app’s look, and while the differences are mostly subjective, block quotes are a lot more legible than they used to be!

These days, most apps that support multiple accounts will ask which one you want to use when sharing from another app. Tusky was one of the first I found that did. I used to get so annoyed when I started posting something to Instagram only to notice at the last stage that it was on the wrong account! Another nice feature is the option to open the post you’re viewing in another of your accounts, something that I use just often enough that I miss it every time I try another app for a week. (Update: Moshidon does this too!)

There are a couple of maintained forks that I’ve tried: Husky adds Pleroma/Akkoma features, but lags a bit behind Tusky. Pachli is a solid alternative, having split over a project disagreement, and while Tusky and Pachli have diverged, Tusky is more mature, and they’re still similar enough that I don’t see a compelling reason to switch.

Bottom line: it’s still my preferred Fediverse app, though Fedilab’s support for additional non-Mastodon features makes it a very close decision.

An actively-developed Mastodon app forked from Tusky.

Like the original, it’s capable and stable, not too simplified and not too cluttered. I’ve been trying it out for a few weeks, mainly out of curiosity, after years using Tusky. They’re still broadly similar, with mostly small differences in what’s emphasized and how. Pachli tries to release an update every month, while Tusky follows the more common “when it’s ready” release model. In some cases they’ve both added new features since the split, like hooking into server-side translations.

The biggest Pachli-specific feature I’ve found is more harassment filters that let you limit messages from unfamiliar accounts based on account age, interactions, etc. This is a cool idea, and I’d like to see something like it implemented at the server level as well.

Tusky recently polished the look of their app, and the differences are mostly subjective, but the new design displays block quotes a lot more legibly than Pachli does.

Overall, Tusky and Pachli are still similar enough that I don’t see any compelling reason to switch from one to the other. Both are more stable than Husky, more capable than the official Mastodon app, and more user-friendly than Fedilab or Subway Tooter, though neither has Fedilab’s support for additional features in non-Mastodon servers.

A full-featured app for connecting to Mastodon and other Fediverse servers. The experience is closer to Tusky’s minimalism than to Subway Tooter’s clutter, but it doesn’t run quite as smoothly as Tusky. Fedilab handles multiple accounts, drafts, lists, scheduling, all the usual features you’d expect.

More importantly, it also supports some extended capabilities of non-Mastodon servers (and Mastodon forks), including:

• Quote-boosts compatible with Akkoma.
• Local-only posts compatible with Hometown, Glitch Social, and GoToSocial (but not Akkoma!)
• Emoji reactions compatible with Akkoma.
• Full-width images on Pixelfed.
• Logging into a PeerTube account directly.

Another feature I like is that it pre-fills a summary and attaches an image when you share a URL from another app.

Visually it’s a bit…pinched?..compared to Tusky. And I can’t move both the main toolbar and the lists to the bottom of the screen (where I can reach them with my thumb). But the nested thread display with sidebar colors is quite nice.

I’ve been using both Tusky and Fedilab on my main accounts (GoToSocial and a Mastodon alt) for the last few weeks, and while I think I’m going to go back to just Tusky, it was a close decision. If I used my Akkoma alt more often, or PeerTube, that could easily have tipped the balance the other way.

A fork based on an older version of Tusky, with added support for Pleroma and Akkoma extensions. This includes things like quote boosts, emoji reactions, a toolbar for markdown formatting, and local-only posts, and it works quite well on Akkoma.

Husky runs about as smoothly as Tusky, with the exception that it currently needs to keep a background process running for push notifications. (It looks like the planned switch to Unified Push should resolve that.)

You can use it to connect to other server types like Mastodon or GoToSocial, but it doesn’t always know which extensions are supported. For example, it assumes Mastodon and GoToSocial will handle local-only posts the same way Akkoma does, and if you try, the post fails. And it hasn’t kept up with newer Mastodon features as well as Tusky has.