What changed, and when
Newest first. Dates are the day the change went out. Anything that affects what the app promises about privacy is called out rather than buried in a list of fixes.
1. v1.12.0 — 2026-09-27
The host is in charge. Tap someone in the room to make them the host or to remove them. Someone removed is out at once, and from then on everybody new knocks and you decide — so they cannot simply walk back in. A new door button locks the room (nobody new, not even by knocking) or lets you let people in by hand; everyone sees which it is.
Notes the host can lock. “Only you write” keeps the notes the host’s alone until opened again — and it holds against a modified app too, without any two copies ever ending up different. Undo and redo (Ctrl+Z, Ctrl+Shift+Z) take back only your own typing, even while others write. Everyone’s caret shows in colour with their name, and the notes download as plain text or Markdown.
Reply, pin, poll. Click a message to reply to it: the quote is always the message as you received it, so nobody can put words in someone else’s mouth. The host can pin one message at the top for everyone, newcomers included. And a poll asks the room a question: one vote each, changes of mind allowed, closed by whoever asked.
2. v1.11.0 — 2026-09-27
Notes, grown up. Write, Preview and Authors: the preview reads headings, lists, bold, italics, code and quotes, and its checkboxes are real — tick one and it is ticked for everyone. Authors colours each person’s words, so you can see who wrote what. A toolbar for headings, lists and checklists, Ctrl+B for bold, lists that carry on when you press Enter, a text size of your own, a live word count, and who is writing right now.
Smoother with ten people. Tested with ten browsers writing into the same notes at once, and nine guests handing files to one host at the same moment. In long notes each keystroke costs about a third of what it did, other people’s edits redraw only what changed, and translation now works only on the messages you can see.
Privacy. The notes no longer let the browser’s spellchecker read them — some browsers send what it checks to an online service. On phones the tabs you are not on are now icons, so every language fits.
3. v1.10.1 — 2026-09-27
Hardened after a stress test. In a Receive files room, a guest’s file now stays strictly between that guest and the host — the host’s browser never offers it to anyone else. Notes and translation stand up to a hostile participant: whatever they send, nobody’s tab freezes and the notes stay the same for everyone.
4. v1.10.0 — 2026-09-27
Read everyone in your language. Turn on Translate above the message box and other people’s messages appear in your language, translated by your browser on your device — the words never leave it. The original is one tap away. Chrome on a computer does this today; elsewhere the button is not shown, and the first time a language is needed the browser may download it.
Notes. A new tab: one text everyone in the room writes in at once, live. It sorts out on its own who typed what where, even when two people type at the same spot, and it goes with the room like everything else. Copy it or download it before you leave.
Receive files. A room made only to collect files: guests see only you, send only to you, and never see each other — the server does not even tell them the others exist. Good for a client sending documents, or a class handing in work.
5. v1.9.0 — 2026-09-27
Română and 日本語. Obleevo now speaks Romanian and Japanese too — the whole app and every page of this site, seven languages in all.
A language menu worth opening. The plain list became a menu that names each language in itself and in yours, works from the keyboard, and changes the address so a reload keeps your choice.
The logo goes home. Obleevo in the corner of the front page and of every page of this site takes you back to the front door, in your language.
Every screen size. On a phone the room’s header takes two lines instead of three or four, the message box gets the full width, tabs no longer push the page sideways in languages with longer words, and the page no longer jumps to the form or puts the keyboard up on its own. On large monitors everything grows with the screen.
6. v1.8.0 — 2026-09-27
Obleevo speaks Spanish, German and Portuguese. The whole app — every button, every warning, every file-scan finding — and every page of this site now read in Español, Deutsch and Português, alongside English and French. Pick one from the language menu at the top; your browser’s language is used when it is one of the five.
A front door per language. obleevo.com/fr/, /es/, /de/ and /pt/ open the app in that language, and a search in your language finds a page in it.
The legal pages, translated. The terms, the privacy notice and the cookie and accessibility pages have courtesy translations. The English and French versions remain the ones that apply, and each translated page says so.
Summaries that match. The short version atop the terms now mentions the encrypted relay used when no direct path exists, and the one atop the privacy notice the daily activity counts, as the full text below them always did.
obleevo.ca now leads to obleevo.com.
7. v1.7.2 — 2026-09-27
GhostDrop is now Obleevo. Same app, same promises, a name of its own: “GhostDrop” was already used by other services, some of them doing the same thing. Obleevo comes from oblivion - which is where a room goes when its host leaves.
A new mark. An O coming apart into squares that drift away: the room, and everything in it, going. It is the icon on your home screen, the tab’s favicon and the badge in the corner.
Nothing to redo. Safety codes, room passwords and downloads set aside to resume work exactly as before, and match people still on the old version.
A voice warning at the right moment. Someone joining a call a few seconds after someone else could be flagged as unverified before their proof had time to arrive. Everyone now gets their own few seconds first.
8. v1.6.1 — 2026-09-25
The relay, with a hard limit. The relay that hides your address (Cloudflare’s TURN) is now switched on, and it can never go past its free monthly allowance. The server reads the relay’s own usage figures, counts over any 31 days rather than the calendar month, stops before the limit - allowing for how fast it is being used - and cancels credentials already handed out. The nearer the limit, the shorter a credential lives; if the usage cannot be read, the relay is off rather than unmetered. When it is paused, Hide my IP says so, connections are direct, and the status page shows how much of the allowance is left.
A backup relay. A second relay, run on a server of our own, can stand behind Cloudflare’s: the moment Cloudflare’s allowance is used up or cannot be read, new connections go through it instead, with its own expiring credentials. Under the limit, Cloudflare’s is always used first.
A wider safety margin. Cloudflare’s relay now stops at 900 GB of its 1,000 free, so even a burst faster than its usage figures can show stays inside the free allowance. Its credentials last an hour at most, usage is read every minute, and every credential still out is cancelled when the server stops.
9. v1.6.0 — 2026-09-25
Post-quantum encryption. Everything is now encrypted a second time, on top of WebRTC’s own encryption, with keys a future quantum computer cannot recover: a hybrid of X25519 and ML-KEM-768, mixed with the room’s secret when there is one. Traffic somebody records today to open in ten years gives them nothing. Messages and files always get it; calls and screens get it where both browsers can seal video and audio frames. The connection panel says which, person by person, and a lock beside a name means that link is post-quantum.
Keys that keep changing. Each channel moves to a new key at least every minute and throws the old one away, and a completely fresh exchange runs every half hour - so a key stolen later opens neither what came before nor, for long, what comes after.
A room that no longer needs the server once you are in. After two people connect, everything else about their connection - starting a screen share, joining a call, repairing the link - is negotiated inside their encrypted channel. A room keeps working through a server restart, and the server sees nothing after the first hello.
Is that really their voice? A voice can now be imitated convincingly. In a call, each person carries a shield if their key was proved, or a warning if it was not; the app says so when somebody unverified joins, and the safety words are one press away.
Check each other in person. The safety number is also a QR code: side by side, scan each other’s instead of reading five words aloud.
Photos without the place they were taken. JPEG, PNG and WebP pictures you send leave without GPS position, camera details or anything hidden after the image, and the send dialog says what was removed. Formats that cannot be cleaned safely - HEIC, video - are flagged instead.
Pictures you receive, defused. A received picture is shown only as a copy redrawn from its pixels in a throw-away part of the browser, so an image built to attack it never reaches the page.
Links that show where they really go. Following a link from a room first shows the real site, large, with look-alike letters, imitated brands (banks, PayPal, Interac, Canada Post…) and hidden destinations spelled out. Names that could be mistaken for one another in a room are flagged too.
Rooms your size. Choose 2, 3, 4, 5 or any number of people; the server refuses anyone past it. And choose what a room can do: turn off files, screen sharing, voice or the board, and every browser in the room refuses them, even from a modified app.
Panic. Press Escape three times within a second: the page goes blank, you leave (as the host, the room burns), this browser forgets Obleevo, and the tab ends on an empty page.
Hardening. Trusted Types and cross-origin isolation shut whole families of injection and memory-reading attacks. Every change is now tested in real browsers - 44 end-to-end scenarios in Chromium - and fuzzed with hundreds of thousands of hostile messages before it can go out.
10. v1.5.1 — 2026-09-25
Privacy: a strict room no longer lets in anyone who only has the code, even for a moment. Somebody with the bare room code received the chat, the files on offer, the board, the screen and the call for the ten to fifteen seconds before the check threw them out — and could rejoin to start again. Now nothing but the handshake crosses until they have proved they hold the invite key.
Privacy: Hide my IP now means relay or nothing. If the relay could not be reached for a moment, the next connection was made directly and showed your address while the switch still said hidden. Now that connection waits, and the app says why.
Security: nobody can pretend to be the host. Who the host is now comes from the server, not from what a member says about themselves — a member claiming it could wipe everyone’s board and rule on everyone’s files. The knock label is sealed with a key tied to the room, a private file’s delivery receipt goes to its sender only, a shared screen starts silent, and one peer can no longer fill your tab’s memory with the board, voice messages or file announcements.
Connections that recover by themselves. Starting a screen share while the other person joined the call sent the link into an endless reconnect. A change offered while the other side was briefly away was never offered again. Both ends reconnecting at once could lose the greeting, the proof and the messages waiting for that moment — and in a strict room, the person. A proof made a moment too early raised a false “FAILED verification”. Each was found and checked in a real Chrome.
Transfers that resume. A file interrupted by a reconnect now carries on instead of stalling for good, and a paused download stays whole — accepting a different file with the same name no longer mixes the two. And “Resume this even if the tab closes” now survives the tab closing — it used to be erased with it.
Voice messages. Cancelling while the microphone was still opening no longer records anyway and sends it two minutes later, and a redraw of the room no longer hides a recording in progress.
Fewer surprises. Dropping or pasting several files asks once and respects a private chat. One dialog no longer silently closes another — a host’s file review could jam the rest of the room. A second invite link keeps its key. The end-of-room card shows again. The join page keeps what you typed, and creating or joining a room no longer waits for ever when the connection drops at that very moment. Dialogs take the keyboard, and more of the app speaks French.
Server. One machine can no longer invalidate everybody’s join puzzle. The daily counts are published once a day is over, so they cannot say when anything happened in it, and two servers running during an update no longer overwrite each other’s counts. The privacy notice now says plainly that relay credentials are shared, not made per person.
11. v1.5.0 — 2026-09-24
People stuck on “connecting”. Everyone could see everyone in the room, and nobody could send anything. The cause is outside the app: since Chrome 146, browsers refuse connections to addresses inside a local network unless a site is given permission, and without a relay two networks that refuse direct connections — mobile data, most home routers asked to reach themselves — never meet. The app used to sit on “connecting” for ever while that happened. It now gives it twenty seconds, then says plainly that a direct connection is refused and there is no relay, marks the person “no direct link”, and keeps trying. With a relay configured, the same people connect.
Fixed: four ways a connection could hang for good on a perfectly good network, found by testing in a real Chrome rather than a stand-in. When both ends tried to connect at once — somebody coming back after stepping away, both pressing Reconnect — the step that resolves the collision left the browser refusing every description after it. Both ends could each close the channel the other was using, so the link read “connected” with nothing to send on. A collision could leave only local addresses to connect through, useless across two networks. And a link that never failed outright was never repaired. The server also dropped the last connection candidates of somebody joining a full room — the relay ones — and refused a second screen share outright.
Test my network. On the join screen and in the connection panel: a few seconds, nothing sent to anybody, and an answer to whether your network lets UDP out, whether its NAT is strict, and whether the relay can be reached — which is exactly what decides whether a connection will work.
Who will get it, before you send. The send dialog lists everyone the file is going to: connected directly, through the relay, or not connected — and so not getting it.
The copied diagnostic now says why a link is not open: the state of the connection, which kinds of address each side offered, and how the attempts went — kinds and counts only, never an address.
A count on the front page. How many times somebody joined a room, and how many rooms were opened, since the server started counting — drawn as a running total in one-bit dither. Counted per day, never per person. Where the operator sets it up, the counts are kept in a Cloudflare KV store so an update no longer resets them.
Verify what you run. The verification page now compares every file your browser received with the list published for this version, says which ones differ if any do, and gives one fingerprint you can compare with somebody else’s. In French too.
Only things that are true. “No size limit” is now “no size limit in Chrome and Edge” (other browsers hold up to 512 MB in memory); “nothing written down” now says the server keeps a count of rooms per day; and Burn wipes the room from every browser in it rather than claiming to erase files people chose to save.
12. v1.4.0 — 2026-09-23
Scan a room’s QR code to join. On the join screen, the camera button reads the code off another screen — no typing. It appears only in browsers that can read QR codes themselves (Chrome on Android, among others); everywhere else your phone’s own camera app opens the link just as well. The camera is opened without the microphone, read on your device, and released the moment the code is found. Only a link to this site is accepted.
Pause and resume a transfer. Every transfer has a pause button beside the stop button. Pausing a download sets it aside without losing anything and tells the sender to wait; resuming picks up exactly where it was. Pausing a send holds your upload while the room keeps trading what it already has.
See the photos and videos you receive, where they arrive. Once a picture or a video has landed and your browser has checked it, it shows in the conversation — press a picture to see it full size. It is read from your own copy, judged by its real contents rather than its name, never shown if the check flagged it, and gone when you leave the room.
13. v1.3.1 — 2026-09-23
Fixed: somebody let in, or in with the password, could end up never able to talk. If the host stepped away for a moment as they arrived — switching apps on a phone to send the link or the password is enough — the newcomer’s connection request was lost, and when the host came back the two sides each waited for the other for good: the newcomer saw the host, and their messages went nowhere. Whoever is left waiting now asks again.
Fixed: a Wi-Fi blip after ten minutes in a room sent you back through the door as a stranger. The pass that seats you again after a drop expired ten minutes after you joined, however long you had been there — a host lost the room, and in a room set to burn, the room burned for everyone. It now lasts as long as your seat does.
Knocking. Knocking twice no longer gives one person two seats. A knock is withdrawn from the host’s screen when the person knocking leaves. If the connection drops while you wait, it knocks again by itself when it is back. A host who takes over from one who left is shown who is still waiting.
When two people cannot connect at all, it says so. Some networks — mobile data, a lot of office Wi-Fi — refuse to be reached directly, and without a relay two of them never connect. That used to be “connecting” for ever; it is now said plainly, with what to try.
A message sent while someone is still connecting reaches them the moment they are, instead of never.
Disappearing messages. They go at the same moment for everyone, whatever tab anyone is on — a message that arrived while you were on the Board or in a call used to stay until you came back to the chat. Nothing is left on screen afterwards: not a frozen image of it if the window was in the background, not the “delivered to 1 of 2” line under it, not an open reaction menu. The seconds left count down where you can see them, and a voice message that disappears can be heard to the end first.
Time left, measured on what has arrived. The sender’s bar counted what was queued to go out, so it could say “landed” while most of the file was still on its way; the receiver’s speed only moved every 4 MB and swung wildly; a resumed file claimed impossible speeds. All three now count bytes that actually arrived, and the flight board’s schedule starts when the bytes do.
Accepting files. A file sent privately to one person can no longer be taken by anyone else in the room. A file stopped while your save dialog was open is not downloaded anyway, and a card whose sender has left no longer offers Accept. Empty files arrive. A strict room’s blocked file is declined properly on both sides.
Fixed: in v1.3.0 nobody was shown joining a call — voice messages had taken over the call’s own signal.
14. v1.3.0 — 2026-09-23
Voice messages, and dictation. The microphone beside the message box turns the box into a live waveform while you talk. Send it as a voice message — recorded in your browser and sent to the room over the same encrypted channel as a chat message, never through the server — or keep only the words, written out as you speak and dropped into the box to read over. Dictation is your browser’s speech service: where it can run on the device it does; where it cannot, your voice goes to the browser’s maker, and you are told so and asked first. “Voice messages only” is a full answer.
Mentions. Type @ and pick a name. The person named sees the message marked for them, and gets a notification if they asked for notifications — one that says someone named them, and nothing about what was said.
A message that disappears now really does. It comes apart into noise, then into dust that blows off the screen. And it goes from everywhere this page kept it: the room log, the screen reader’s announcement, its reactions, its sound if it was a voice message — and it is left out of the saved transcript, even inside its thirty seconds. It never passed through the server in the first place.
Flight details. Press the time left on a transfer and it opens as an arrivals board: departure, scheduled and estimated arrival, on time, delayed or early against the first estimate, speed, and whether the route is direct or stops at the relay.
The download, as a heat map. Each finished square is coloured by how fast its blocks arrived, with who they came from when you point at it — so a slow stretch from one person is something you can see.
How hard the server has worked. Press “Operational” on the status page for a calendar of the last six months: one square a day, by work or by stress. The server keeps one line of numbers per day for it — how busy it was, never who made it busy — and the privacy notice now says exactly that.
15. v1.2.1 — 2026-09-23
A transfer can be stopped once it has started. Declining only ever worked before the first byte; after it, a file sent to the wrong person could only be stopped by leaving the room. The sender can now stop it for everyone and a receiver for themselves, and what has arrived is thrown away — nothing half-written is left on disk looking like the real file. Only the person who sent a file can withdraw it.
Time left, beside every transfer, in your language, and "estimating…" rather than nothing while it works it out.
You can see when you are still sharing a file. After a file arrives, your browser keeps handing it to the room for five minutes after the last request — the best source there is for someone who joined late. That used to happen with nothing on screen. It now has its own row: how much has gone out and to how many people, when it stops, and a button to stop it now.
A screen for having no network. The installed app opens without one, and the join form used to look normal and do nothing. It now says you are offline, that nothing is lost by waiting, and comes back by itself — with whatever you had typed still there. In a room, the line at the top says whether it is the server or the whole network that has gone, because only one of them leaves your transfers running.
Fixed: a join that could not reach the server said nothing. The button reset after eight seconds without a word; it now says the server is not answering and what to do about it.
Fixed: joining could freeze the page after the tab had been in the background, or on a phone that switched apps mid-join. A watchdog re-ran the whole join puzzle on the page itself when the background worker was slow to answer — and a frozen tab always is. The puzzle now only ever runs in the worker, or in small slices that hand the page back.
Fixed: a downloaded file could ask to be accepted again. A repeated offer, or a refused second press of Accept, turned a finished transfer back into a question.
16. v1.2.0 — 2026-09-22
The room is a planet now. The globe was a lattice of rings, which reads as a flat wireframe; it is rebuilt on the same point-cloud engine as the thinking orbs elsewhere in the app — a real sphere, turning, with arcs that go over the top and behind it, and packets riding them in the direction the bytes are actually going.
The score is back where the decision is. The arc filling and the number counting to 95 now appear in the send dialog and in the panel the receiver reads before accepting, instead of only after a file had arrived.
React by clicking the message — not by pressing R on it, which nobody discovers. Any emoji can be used, not four: pick one of the eight offered or type your own. It still cannot be words, which was the reason the four existed.
Messages that do not stay. Turn on the ghost beside the message box and what you send dissolves from both screens thirty seconds after it lands, character by character. It is a courtesy rather than a guarantee, and the interface says so — anything on a screen can be photographed.
Fixed: the host could not let anyone in from a phone. Knocks lived in the room’s sidebar, which is hidden on narrow screens, so the request was invisible and the person outside waited the full ninety seconds. They are shown at the top of the room now, at every width.
Fixed: the server’s refusals spoke English in a French interface — a wrong password, a full room, a host who declined. And the create-room dialog still described its own options in English.
Fixed: the password box vanished while it was working. Joining starts with a proof of work that takes seconds; the dialog used to close first and leave nothing on screen. It now stays, says what it is doing, and writes a refusal under the field instead of opening a second dialog.
Fixed: a declined file left the sender measuring for ever. When everybody said no, the transfer was never closed and its row sat in the panel with nothing to show.
The landing page lost the argument cards and the comparison table, which now have a page of their own, and the globe beside the heading is smaller.
17. v1.1.0 — 2026-09-22
The whole interface is now in French as well as English, detected from the browser and switchable with the FR/EN button. The legal pages were already bilingual; everything else is now too.
You see what you are sending before it goes. Every file is examined and the report is shown to the sender — not only the ones that look hostile — and that report, plus the first bytes of the file, now travels with the offer so the person receiving sees the verdict and the real file type before accepting rather than after.
Accept all, into one folder. Fifty photos used to be fifty dialogs. Pick a folder once and everything accepted afterwards lands in it, one click per file.
Send to one person. Click somebody in the room to send them a file or a private message over their connection alone.
Install it. The app can be added to a home screen, and on Android it appears in the system share sheet — the shared files are handed to the page by the offline worker and never uploaded.
Connections repair themselves. The server is retried for as long as the tab is open and your seat is kept for you, so a Wi-Fi blip no longer ends a transfer or a call. Broken connections restart in place, network changes are followed, and a heartbeat notices a silent peer in fifteen seconds instead of thirty.
Calls. Joining the call takes you to it and leaving brings you back; microphone and speaker can be chosen and follow a headset being plugged in; there is a live meter for your own microphone and a green, amber or red dot per person measured from packet loss and jitter. Opus is told it is carrying a voice (DTX and in-band FEC).
Speed. Files that compress are compressed on the wire, and only when a sample proves it helps; block verification moved off the page’s thread to the platform’s SHA-256, which lifts the ceiling a fast local network used to hit.
Reactions on messages, an "is typing" line, keyboard shortcuts with ? for the list, a full-screen button on a shared screen, a delivery receipt card, a globe of the room with the traffic drawn on it, and a summary when the room ends.
18. v1.0.0 — 2026-09-21
First release: temporary rooms, end-to-end encrypted files of any size, chat, a shared whiteboard, screen sharing and voice — all peer to peer, with a signalling server that never sees content.
Automatic verification from the invite link, safety words for everything else, proof-of-work on every join so the server can rate-limit without knowing who anybody is, a burn button that erases the room everywhere, and bilingual legal pages.
Last reviewed:
About · Why this · FAQ · Terms · Privacy · Accessibility · Cookies
Obleevo is developed by The House of Brendrof. Proprietary software, free to use.