Openvibe

Open social media fixed the lock-in problem and created a fragmentation problem. The people worth following are now spread across Mastodon, Bluesky, Nostr and Threads, each with its own app, its own culture and its own notification badge. Openvibe, from Czech developer Tweetoshi s.r.o., bets that most people don’t want to pick a side. They want one place to read and one box to write in.

The company’s history explains the pitch. Openvibe grew out of Plebstr, Tweetoshi’s earlier Nostr client, and widened from a single protocol to the whole open-social map. It signs into existing Mastodon, Bluesky, Nostr and Threads accounts, adds Tumblr and RSS/Atom feeds, and merges the lot into one chronological timeline. There is no Openvibe account to create. That keeps onboarding friction low, and it means the app holds no social graph of its own: your followers stay on the networks where you earned them.

The business framing is just as deliberate. Openvibe is free and carries no ads. Tweetoshi has promised never to sell user data and plans a subscription that it says will be reasonably priced. Investors include Automattic, the company behind WordPress.com and Tumblr. That gives the project a backer with an obvious stake in open publishing, and it makes Tumblr’s place on the supported list unsurprising.

Reception follows a familiar pattern for ambitious aggregators. The app holds a 3.8 out of 5 on the US App Store from 165 ratings. Daring Fireball and 9to5Google praised its multi-network approach and its frequent updates, including the image crossposting added in version 1.10. User reviews, meanwhile, keep returning to the same set of complaints about the timeline and composer. People admire the concept and keep finding problems in how it’s carried out.

Openvibe calls itself a bridge to open social media, and that word fits better than “client.” It connects networks without replacing any of them. Like any bridge, it depends on the ground at each end, and on Threads that ground currently supports traffic in one direction only.

• Unified chronological timeline: Posts from Mastodon, Bluesky, Nostr, Tumblr and RSS/Atom feeds share a single stream, ordered by time instead of by an engagement algorithm.
• Crossposting with images: One composer publishes to several networks at once, Threads included. Image support arrived in version 1.10.
• No separate account: Sign in with existing network accounts. Openvibe adds no identity layer of its own.
• Multiple profiles: Separate profiles keep identities apart, for example a work presence and a personal one.
• Direct messages: Available on the networks that support them.
• Notifications: Supported, though mostly limited to Bluesky and Mastodon.
• Write-only Threads support: Openvibe can post to Threads but can’t display Threads posts, because Threads doesn’t offer a full third-party API.
• No ads, no data sales: A stated commitment from the developer, with a paid subscription planned.

Crossposting Is the Product

Take away the aggregation and the composer is the feature with the strongest case. Keeping up a presence on three or four networks usually means copying text between apps, re-attaching images and hoping you didn’t skip one. Openvibe turns that into a single post sent everywhere at once. Image crossposting in version 1.10 removed the most obvious reason to go back to the native apps. For anyone whose audience is split between Mastodon and Bluesky, this is the feature that justifies the install.

The catch is that these networks aren’t interchangeable. Each has its own length limits, link handling, mention syntax and etiquette, and a post written for one rarely fits all of them cleanly. User reviews report that crossposts can look messy, which is the expected cost of a composer that works to the lowest common denominator. The obvious next step is per-network preview and editing: show how the post will appear on each destination and let the author adjust it before sending. Until that exists, crossposting rewards short, plain posts and penalizes anything that depends on one network’s conventions.

The Timeline: Chronology Has Requirements

A single chronological feed is a principled choice. It rejects engagement ranking and treats every network as an equal source. Chronology also makes one firm demand: the app has to remember where you stopped reading. User reports that the timeline loses its place after reloading or navigating back undercut that directly. In an algorithmic feed, losing your position is an annoyance. In a time-ordered feed that merges several busy networks, it leaves two options: scroll back through everything, or give up on posts you never saw.

Merging also creates a volume problem. A follow list on an active Mastodon server can post at a very different rate from a few Nostr accounts or an RSS feed that updates weekly. In one stream, the busiest source sets the pace and the quiet ones get buried. Discovery has a similar weakness. Users have asked for trending topics, better search and bios in following lists, which points to an app built for people who already know whom they follow. It does less for people trying to find new accounts.

Reports that Bluesky feeds sometimes stop loading without warning expose a specific weakness of aggregators. When a feed goes silent, a quiet network and a broken connection look identical. Clear per-network status signals would turn that ambiguity into information, and an app whose entire job is merging sources needs them.

Friction in the Details

Some reported problems are minor on their own and damaging together. Reply drafts disappear when the user taps outside the reply field, so one stray tap costs written work. Videos autoplay with sound, a default that suits nobody reading a feed on a train or in an office. Neither is a hard engineering problem, and both affect how much people trust the app.

Identity, Messaging and Notifications

Multiple profiles are a thoughtful addition for people who run separate personas, such as a professional account and a personal one, or a project account next to an individual one. Users still ask for more than one account per network, though, so the profile system clearly doesn’t satisfy everyone who manages, say, two Bluesky handles.

Direct messages work where the underlying network supports them. Notifications are the uneven part: they’re mostly limited to Bluesky and Mastodon. In practice, Openvibe can stand in completely for some networks and only partly for others. Given the app’s Plebstr roots, it’s ironic that Nostr users get one of the thinner experiences.

The Threads Gap

Threads support works in one direction. Openvibe can publish there but can’t show Threads posts. The limitation comes from Threads’ API, not from Openvibe, and Tweetoshi can’t fix it alone. The result for users is still awkward. Threads becomes a broadcast-only destination, and anyone who wants to read or answer the conversations their posts start still needs Meta’s own app.

The Subscription Question

Today the deal is about as good as one gets: free, no ads, and a promise never to sell user data. Some users worry that a costly subscription will eventually replace it, and the developer has only said the price will be reasonable. We think the no-ads, no-data-sales commitment is the right one for an audience that moved to open networks largely to escape that business model. Until a price is announced, though, the value score is provisional.

The hardest design problem here is structural. Openvibe has to display posts from networks with different formats (Bluesky, Mastodon, Nostr, Tumblr and plain RSS articles) in one stream without it looking like five apps stacked together. User complaints about messy crossposts suggest that normalization is still incomplete, at least on the publishing side. Autoplaying video with sound is a UI default that works against a calm, chronological reading experience, and it will use mobile data whether or not the reader wanted the clip.

On performance, an aggregator can only be as fresh and reliable as the slowest or least dependable network it pulls from. That’s a structural limit of the model, and the reports of Bluesky feeds stalling silently and the timeline losing position fit it. The tech press credits Tweetoshi with frequent updates, which suggests rough edges get attention. Still, the current complaints concern the main timeline, the screen the app depends on most.

Openvibe ships on iOS and Android with the same offer on both stores: the same networks, the same crossposting and the same free price. Both versions are touch-first and built for phones. The subscription has no announced price on either platform.

• iOS: Rated 3.8 out of 5 on the US App Store from 165 ratings. Praise from Apple-focused Daring Fireball shows the app has attention in that community.
• iPad: Users report that the share button doesn’t work on iPad. That’s a notable gap in a tool built around distributing posts, and it suggests tablet layouts trail the phone experience.
• Android: Coverage from 9to5Google indicates the Android version gets serious attention and isn’t a secondary port.

Openvibe solves the right problem. The open social web is split across protocols, and an app that lets one person write once and reach audiences on several networks has a clear, practical purpose. Crossposting is the reason to use it, and the 1.10 update that added images made it complete enough for everyday posting. The no-account design and the no-ads, no-data-sales pledge show a developer that understands why its users left the big platforms.

The reading side has further to go. A chronological timeline that reportedly forgets your position fails at the one thing chronology requires. Silent Bluesky stalls, disappearing drafts and autoplaying sound make the app harder to trust, and the Threads API keeps one of the four headline networks write-only. Notifications and discovery are both thinner than a full replacement for native apps would need.

We recommend Openvibe as a publishing tool first and a reading app second, and only to people whose posting lives span several open networks. It’s worth installing for the composer, worth watching for the timeline, and the final assessment depends on what the subscription costs once it arrives.