Dropnook 2.4.0

Dropnook 2.4.0 — record the live room.

• Record: a new button in the room saves the room as you see and hear it — every picture in a grid with names, every voice mixed — as a file in the shared files (.webm; in Safari .mp4). The file grows while you record: it is uploaded piece by piece, so it is nearly complete the moment you stop.
  • Everyone in the room sees a red REC mark with your name; the others get a short note when a recording starts.
  • Leaving the room or closing the page ends the recording; what was uploaded by then stays. A browser that vanishes without a word has its recording closed by Drop after five minutes.
  • Picture and sound still go straight from device to device. Drop never sees them — the recording happens in your browser, only the finished pieces are stored.
• Uploads without a known size: the server now accepts uploads that grow, which the recording uses. Everything else about uploads is unchanged.
• Texts and help in all 17 languages.

Nothing to change on your side: Check for Updates → Update (with DROPNOOK_VERSION=2, Compose Up); open pages reload themselves. The Community Apps edition gets the update too.

Full Changelog: v2.3.2...v2.4.0

Dropnook 2.3.2

Dropnook 2.3.2 — see who is live, and pages that keep themselves current.

• Preview in the tile: outside the live room, the tile above the text fields shows a small picture of it right away — the first member with a camera on, without sound, at 240p. One click on Video or Voice and you are in.
  • The room sees how many watch: the eye at the top (👁 2). Camera off means no picture; a locked room shows none.
  • Only while the page is visible; a tab in the background costs nobody anything.
• Pages update themselves: after an update, every open Drop page loads itself again — not in the middle of the live room or of an upload, then right after. Pages opened before 2.3.2 need one last reload by hand.
• Texts and help in all 17 languages.

Nothing to change on your side: Check for Updates → Update (with DROPNOOK_VERSION=2, Compose Up), then reload Drop once on every device. The Community Apps edition gets the update too.

What's Changed

• Live room preview in the tile, self-reloading pages (2.3.2) by @dropnook in #15

Full Changelog: v2.3.1...v2.3.2

Dropnook 2.3.1

Dropnook 2.3.1 — no forgotten live room.

• Still there? Alone in the live room for 5 minutes, Drop asks — with a short sound and a countdown. Stay keeps the room for another 5 minutes; without an answer the page leaves 2 minutes later, and the room ends with it. Someone coming in ends the question at once.
• Your own name no longer covers the hint at the top while you are alone in the room.
• Texts in all 17 languages.

Nothing to change on your side: Check for Updates → Update (with DROPNOOK_VERSION=2, Compose Up). The Community Apps edition gets the update too.

What's Changed

• Live room: "Still there?" (2.3.1) by @dropnook in #14

Full Changelog: v2.3.0...v2.3.1

Dropnook 2.3.0

Dropnook 2.3.0 — the live room: video and voice for up to 10 people in your network, instead of 1:1 calls.

• Go live: the camera button at the top → Video or Voice. Everyone with Drop open sees a live tile above the text fields — who is there, how many — and joins with one click. No ringing, no answering.
  • Up to 10 people (LIVE_MAX, 2–50). Every member is connected to every other one; the more people, the smaller each picture is sent (480p from 5, 360p from 7), so phones keep up.
  • In the room: mute, camera off, front and back camera, Photo into the shared files, and Invite: nudges someone who has Drop open — it rings briefly there, with a button to join.
  • Whoever opened the room can lock it; when they leave, the next one takes over. The room ends when the last one leaves.
  • Smaller puts the room into a corner; texts and files stay usable below it. Tap a picture to make it large. Whoever speaks gets a green frame.
  • Picture and sound go straight from device to device (WebRTC). Drop only passes on the messages that set the connections up; nothing leaves your network, and drop-share has none of it.
  • HTTPS only — browsers give camera and microphone to nothing else. Over plain HTTP the tile still shows who is live and explains why joining needs HTTPS. With users, the room belongs to the shared area.
• Texts and help in all 17 languages.

Nothing to change on your side: Check for Updates → Update (with DROPNOOK_VERSION=2 in the .env, Compose Up). To change the limit of 10, take the new compose.yaml and set LIVE_MAX in the .env. The Community Apps edition gets the update too, with Live room: most people among the advanced settings.

What's Changed

• compose.yaml: plain and grouped, without comments by @dropnook in #11
• READMEs: LAN-only from Community Apps by @dropnook in #3
• compose.yaml: image version from the .env by @dropnook in #12
• Live room instead of 1:1 calls (2.3.0) by @dropnook in #13

Full Changelog: v2.2.1...v2.3.0

Dropnook 2.2.1

Dropnook 2.2.1 — Cert Warden's address as you copy it.

• CERTWARDEN_ENDPOINT_URL now takes any of Cert Warden's addresses: the server itself (https://certwarden.example.org:4050), the page you have open in the browser (…/certwarden/app/) or the API. With the app page, 2.2.0 asked the wrong address and got no certificate.
• Half set up? If some Cert Warden settings are there but not all, the log of drop now says which are missing — for example when an older compose.yaml does not pass them on.

Nothing to change on your side: Check for Updates → Update.

What's Changed

• 2.2.1: any Cert Warden address; say which settings are missing by @dropnook in #10

Full Changelog: v2.2.0...v2.2.1

Dropnook 2.2.0

Dropnook 2.2.0 — certificates straight from Cert Warden.

• Cert Warden: with CERTWARDEN_ENDPOINT_URL and CERT_INT_NAME, CERT_INT_CERT_API, CERT_INT_KEY_API in the .env, drop fetches its certificate itself — no folder of certificates needed. It checks that key and certificate belong together before using them, and fetches a new one CERT_CHECK_DAY days (preset 30) before the current one expires; the log says what was fetched, never the keys.
• HTTPS for drop-share too: with CERT_PUB_… — or, without, when drop's certificate is a wildcard that covers drop-share — drop hands drop-share its certificate, and drop-share serves HTTPS on port 443 as well. A wildcard is fetched only once. Only drop talks to Cert Warden; port 80 keeps working for your reverse proxy.
• The .env template is tidier: one short comment per setting. Your own .env keeps working as it is.

Nothing to change on your side: Check for Updates → Update. To use Cert Warden, add its settings to the .env (template: compose-projects-drop/.env.example) and take the current compose.yaml; Community Apps: the new fields are under Show more settings.

What's Changed

• 2.2.0: certificates from Cert Warden, HTTPS for drop-share by @dropnook in #9

Full Changelog: v2.1.0...v2.2.0

Dropnook 2.1.0

Dropnook 2.1.0 — video and voice calls between two devices in your network.

• Calls: the camera button at the top lists the devices that have Drop open right now. Video or Voice — the other one rings and answers with or without its camera.
  • During the call: mute, camera off, front and back camera, swap the pictures, and Photo: a picture of the large video, saved to the shared files.
  • Smaller puts the call into a corner window; texts and files stay usable below it.
  • Picture and sound go straight from device to device (WebRTC). Drop only passes on the messages that set the call up; no server outside your network is asked for anything, and drop-share has none of it.
  • Calls need HTTPS — browsers give camera and microphone to nothing else. Over plain HTTP the button explains that. With users, calls belong to the shared area. Always two at a time.
• Texts and help in all 17 languages.

Nothing to change on your side: Check for Updates → Update. The Community Apps edition (LAN only, plain HTTP) gets the update too; there the camera button only shows the HTTPS note.

What's Changed

• Video and voice calls in the home network by @dropnook in #7

Full Changelog: v2.0.2...v2.1.0

Dropnook 2.0.2

Dropnook 2.0.2 — the new donation link, and the guides brought up to date.

• Donating: the link in Drop's help, in all 17 languages, now goes to paypal.me/dropnook.
• Guides: the READMEs and dropnook.app now match 2.0.1:
  • when a renewed certificate is picked up;
  • what happens to uploads nobody continues, and to one that does not fit;
  • how long a text field can be;
  • how to move from 1.x straight to the .env.

Nothing to change on your side: Check for Updates → Update.

Full Changelog: v2.0.1...v2.0.2

Dropnook 2.0.1

Dropnook 2.0.1 — fixes from a full code review and pen test.

• Drop answers only to its own names. It now answers to IP addresses, local names (tower.local, ….lan, ….fritz.box), the names of its certificates and WEBUI from the .env, and nothing else. This closes a DNS-rebinding hole: on a Drop without PIN and without HTTPS, a web site opened in your network could have read and changed it.
  If you open Drop under a domain without HTTPS: put that name into WEBUI in the .env (on Unraid: Edit Stack → .env) and take the new compose.yaml, which passes WEBUI on. Opened with HTTPS, by IP address or under a local name, nothing changes.
• Security headers on Drop's own page: no other site may frame it or embed its files.
• Certificate renewals were not picked up while an interrupted upload was left over, so the certificate could expire. Now an upload without progress for 10 minutes no longer holds a renewal back, and is given up after 7 days.
• Limits against crashes: an upload has to fit the free space, a text field holds up to 2 million characters, and requests are read only up to a size.
• Resuming an upload now also compares when the file was last changed. A changed file of the same name and size starts over instead of being mixed with the old one.
• File names made over SMB (from a Mac, with a backslash, or not in UTF-8) no longer break downloads or the file list. Two uploads with the same name that finish at the same moment no longer overwrite each other.
• A new share could, rarely, be tidied away while it was being created.
• PIN guessing is counted per PIN: signing in with your own PIN no longer resets the count for someone else's. SHARING=off no longer switches off the guard against requests through a proxy, and more proxy headers are recognised.
• Smaller fixes:
  • Tabs open for different users load the right pictures and downloads.
  • The connection dot turns grey when live updates stop.
  • Share passwords are hashed with 600 000 rounds; older links keep working.
  • Malformed requests get 400 instead of 500.

Updating: Check for Updates → Update. If you open Drop under a domain without HTTPS, see the first point.

What's Changed

• 2.0.1: fixes from the code review and pen test by @dropnook in #2

Full Changelog: v2.0.0...v2.0.1

Dropnook 2.0.0

Dropnook 2.0 — five colours, and a place of your own.

• Five colours, light and dark. Teal, gold, blue, violet or coral — the round button at the top picks one for this browser, ☀ and ☾ still choose light or dark.
• Users, if you want. Up to five people, one per colour, each with a name and a PIN — in compose.yaml at drop:

      USER_TEAL: "Anna:2468"
      USER_GOLD: "Tom:1357"

  Drop then asks "Who's there?" once per device. At the top everyone switches between their own area — text fields and files only they see — and the shared area; a dot shows news in the other one. The page is in their colour. Links shared from an own area are listed only for that user. Without a PIN of their own ("Mia"), PIN is theirs if set — otherwise the name alone signs in. Details: README, "Users".
• Without users, Drop works exactly as before — your files, texts, links and PIN stay as they are.

Updating from 1.x: in compose.yaml, change the image line from ghcr.io/dropnook/dropnook:1 to ghcr.io/dropnook/dropnook:2, then Compose Up. Please switch: :1 gets no further updates, also no weekly security rebuilds.

What's Changed

• Dropnook 2.0: users with an area of their own, five colour layouts by @dropnook in #1

New Contributors

• @dropnook made their first contribution in #1

Full Changelog: v1.2.0...v2.0.0