etesync.com Paid content

An end-to-end encrypted backend is a server plus client SDK that stores and syncs application data in encrypted form, where the encryption keys stay on the user's device. The server handles accounts, storage, and sync but cannot read the data it holds. Etebase is one example: an open-source SDK and backend that its documentation describes as "Firebase but encrypted in a way that only end-users can access their data." You should consider this model when your users' data is sensitive enough that a server-side breach should not expose it, and you can accept the constraints that come with client-side encryption.

How it differs from a standard backend like Firebase

A conventional backend (Firebase and similar) stores data in a form the server can read. That makes server-side features easy: full-text search, server-side validation, analytics, admin dashboards, and migrations that rewrite data. It also means anyone who compromises the server, or who is compelled to hand over data, can read everything.

An end-to-end encrypted backend inverts that. The client encrypts before upload and decrypts after download. The server sees ciphertext, account metadata, and sync operations, not plaintext. Etebase's own framing is that it "takes care of the encryption and its related challenges" so you don't build the crypto layer yourself.

What the server can and cannot see

The zero-knowledge model is the core of the design, and it's worth being precise about it:

Etebase states that only end-users can access their data, and that encrypted data "isn't even considered a data-breach under GDPR and HIPAA." Treat that as a design goal to verify for your own threat model, not an absolute guarantee: metadata, access patterns, and client-side compromise remain real considerations.

Developer benefits

• Breach protection. A stolen database yields ciphertext rather than user content.
• Easier compliance. Etebase argues end-to-end encryption makes compliance with GDPR, HIPAA, CCPA, and FERPA easier, partly because encrypted data may fall outside breach-notification definitions.
• Built-in sharing and collaboration. Etebase lists sharing, access control, and collaborative editing support, plus a full revision history of your data and integrity protections.
• Battle-tested cryptography. It uses libsodium behind the scenes and is based on the code powering EteSync, so you're not rolling your own primitives.
• Open source, clients and server. You can inspect what the server actually does.
• Cross-platform. Client libraries are available for desktop, mobile, and web, and it's used by apps such as Tasks.org.

The API is deliberately small. From the documentation, a minimal flow looks like this:

// Setup encryption and login to server
const etebase = await Etebase.Account.login("username", "password");
const collectionManager = etebase.getCollectionManager();

// Create, encrypt and upload a new collection
const collection = await collectionManager.create(
  "collection.type",
  { name: "My data" },
  "My private data!"
);
await collectionManager.upload(collection);

The input is your credentials and plaintext; the action is client-side encryption plus upload; the expected result is that the server stores only ciphertext.

Typical use cases

• Sync apps for notes, tasks, calendars, or contacts where users expect privacy.
• Collaborative editing where multiple users share data but the operator shouldn't read it.
• Privacy-focused products where "we can't read your data" is a selling point.
• Regulated contexts (health, education, finance-adjacent) where reducing the blast radius of a breach matters.

Trade-offs to weigh before adopting

• No server-side plaintext features. Search, analytics, and server-side validation over content must move to the client or be dropped.
• Key management is on you and your users. Lost keys can mean lost data; recovery design is a real decision.
• Metadata still leaks. Sizes, timing, and access patterns are visible to the server.
• Crypto is easy to get wrong. Even with a vetted library, your integration and key handling can introduce flaws.
• Ecosystem and pricing. Etebase lists a pricing page and a beta integrated-billing feature; check current terms directly rather than assuming a free tier.

If your app needs rich server-side processing of user content, a standard backend is the simpler fit. If the priority is that only users can read their data, an end-to-end encrypted backend like Etebase is built for exactly that.

Browser-based video chat is secure when the call is end-to-end encrypted and media travels peer-to-peer instead of through a server. Briefing (brie.fi) works this way: audio, video, and chat are end-to-end encrypted and exchanged directly between peers over WebRTC, with no account, no install, and no tracking. You start a private call by opening the page, sharing the room link with the people you want to talk to, and connecting. This applies to anyone who wants a quick private conversation without installing an app or registering — though it depends on your browser supporting WebRTC and on how carefully you share the room link.

What "secure" actually means here

Security in a browser call rests on two separate mechanisms, and it helps to keep them apart.

End-to-end encryption

Audio, video, and chat are encrypted on the wire, so the content is readable only by the participants. The service states that media is end-to-end encrypted; the server does not hold the keys to your conversation.

Peer-to-peer WebRTC

The connection itself is peer-to-peer over WebRTC. Media is exchanged directly between participants, and the server never sees the media content. That is a stronger position than a relay-based call, where a server passes streams along and could in principle access them.

What the signaling server still does

A signaling server is still needed, but its role is narrow: it only helps peers find each other. It never relays or stores media. In other words, the server helps the call set up, not the call itself.

How to start a private call

1. Open the page. Go to brie.fi in a browser that supports WebRTC. No account or registration is required.
2. Share the room link. Send the room link to the people you want to talk to, through a channel you trust.
3. Connect. Once they open the link, the signaling server helps the peers find each other and the call connects. Audio, video, and chat then flow directly between participants.
4. Grant browser permissions. Your browser will ask for microphone and camera access; the call cannot start until you allow them.
5. Optional: install as a PWA. Briefing runs in the browser and can optionally be installed as a progressive web app if you want quicker access.

The expected result after step 3 is a live call in which media moves peer-to-peer and is end-to-end encrypted on the wire.

Privacy trade-offs to weigh

The no-account, no-install, no-tracking model removes a lot of the usual exposure — there is no profile to leak, no app to keep updated, and no telemetry reported by the service. But it also shifts responsibility to you:

• The room link is the access control. Anyone who has the link can likely join. Share it only with the intended people, and prefer a private channel over a public post.
• Metadata is not the same as content. Encryption protects what you say; it does not by itself hide that a connection happened or who connected.
• Browser permissions matter. Camera and microphone access is granted per site, so check what you have allowed.
• Self-hosting is an option. Because the project is open source and self-hostable, you can run your own instance if you want more control over the signaling layer.

When this fits and when it doesn't

Choose a browser-based, peer-to-peer, end-to-end encrypted call when you want a private conversation with a small group and no accounts or installs. Be more cautious when you cannot control who receives the room link, when you need features the page does not describe, or when your browser or network blocks WebRTC. For those cases, verify the specific capability you need before relying on it.

End-to-end encryption (E2EE) means data is encrypted on the user's device before it ever leaves, and only the end user holds the keys needed to decrypt it. The server stores and syncs ciphertext it cannot read. This differs from encryption in transit (TLS), which protects data only while moving between client and server, and encryption at rest, which protects stored data from someone who steals the disk but still leaves the operator able to read it. Choose E2EE when you want a backend that cannot access user data even if it wanted to — for example, a notes, tasks, or health app where the operator should never see plaintext.

How E2EE differs from other encryption models

With TLS or at-rest encryption, the server holds the keys, so a breach, a subpoena, or a rogue employee can expose plaintext. With E2EE, the keys stay on user devices, so the server only ever handles ciphertext.

The zero-knowledge backend

A zero-knowledge backend stores and syncs encrypted data without being able to decrypt it. Etebase describes itself as "Firebase but encrypted in a way that only end-users can access their data" — a set of client libraries plus a server for building end-to-end encrypted applications. The server handles sync, storage, and sharing logic, but the encryption and key management happen client-side.

The practical consequence: the backend can be breached, misconfigured, or operated by someone you don't fully trust, and user data stays confidential because the decryption keys were never sent to it.

Why this matters for breaches and compliance

Etebase's own framing of the benefit is direct:

• Data breach protection — encrypted data is safe in the case of a breach, and per Etebase "isn't even considered a data-breach under GDPR and HIPAA."
• Easier compliance — E2EE makes it easier to comply with privacy regulation such as GDPR, HIPAA, CCPA, and FERPA.

The reasoning is that if the operator never holds readable data, there is less sensitive data to protect, report, or govern. Treat the compliance claim as a design property to verify with your own counsel for your specific jurisdiction and data type, not as a blanket guarantee.

The hard part: getting cryptography right

Etebase states the problem plainly: cryptography "is easy to get wrong, hard to get right, and even harder to know if you got it right." This is the main pitfall when building E2EE yourself — key generation, key exchange, nonce handling, and integrity checks all have subtle failure modes that pass casual testing but break real security.

The mitigation is to build on audited, widely used primitives rather than rolling your own. Etebase uses libsodium behind the scenes and is based on the code that powers EteSync, which it describes as "battle tested." If you are evaluating any E2EE backend, ask what cryptographic library it depends on and whether that library has been independently audited.

E2EE does not have to block collaboration

A common assumption is that if the server can't read the data, features like sharing and collaborative editing become impossible. Etebase's design targets the opposite: it supports sharing data, access control, and "everything you need for collaborative editing," plus a full revision history of your data, strong integrity protections, and integrated billing (in beta).

The mechanism is that sharing is done by re-encrypting keys for the people you share with, not by handing the server plaintext. So the server still coordinates who gets access, but it never sees the content.

What using it looks like

Etebase's example shows the shape of the API — setup, login, then create/encrypt/upload:

// Setup encryption and login to server
const etebase = await Etebase.Account.login("username", "password");
const collectionManager = etebase.getCollectionManager();

// Create, encrypt and upload a new collection
const collection = await collectionManager.create(
  "collection.type",
  { name: "My data" },
  "My private data!"
);
await collectionManager.upload(collection);

The encryption happens inside these client calls; the server receives ciphertext. Etebase is open source (clients and server), available on all major platforms, and used by applications on desktop, mobile, and the web — its site cites Tasks.org as a user.

How to decide

Use E2EE when the sensitivity of the data justifies giving up server-side readability — you cannot run server-side search, analytics, or content moderation on plaintext, and key recovery for lost user keys becomes a design problem you must solve. Skip it when the operator legitimately needs to read data, or when the threat model doesn't include the server itself.

If you do adopt it, prefer a backend built on audited cryptography over a custom implementation, and confirm the specific compliance and pricing terms for your use case directly, since those depend on your deployment and obligations.

The Old Farmer's Almanac Calendar is a free, daily-updated section of almanac.com that combines a running day counter, moon phase, holidays, weather lore, and a "Best Days" guide into one page. It suits anyone who wants a quick daily reference for sky events, seasonal dates, or traditional timing advice — not a printable planner or a scheduling tool. The page is organized around "Today's Almanac," which the site describes as "your daily dose of holidays, words, weather & wisdom — updated every morning."

What the Calendar page actually contains

The Calendar section is a hub rather than a single grid. Its main blocks are:

• Today's Almanac — a dated entry with a day-of-year counter (for example, "265 / 365" for Tuesday, September 22, 2026), plus rotating daily features.
• Today's Moon Phase — the current lunar phase, tied to the site's broader moon and astronomy coverage.
• Upcoming Holidays — a short forward-looking list (the example entry shows Johnny Appleseed Day and the Full Harvest Moon, both on Sep 26).
• Best Days — a traditional guide to favorable dates for specific tasks.
• Seasonal and weather content — links to equinox/solstice explainers and regional long-range forecasts.

Because the daily entry refreshes each morning, the specific word, question, and puzzle you see will differ from one visit to the next.

Reading the daily almanac entry

Each day's block bundles several small features. In the sample entry, these were:

The pattern is consistent: read the date and counter first, then work down through the tip, word, puzzle, and Best Days line. Anything you want to keep, you copy manually — the page is a reference, not an export tool.

Moon phases, holidays, and seasonal dates

The Calendar page links out to dedicated explainers rather than showing a full ephemeris. The sample content points to an autumnal equinox article ("When is the First Day of Fall? Autumnal Equinox 2026"), which covers the date plus folklore and fun facts. Moon content is surfaced through "Today's Moon Phase" and holiday listings such as the Full Harvest Moon.

If you need precise sunrise/sunset times or a full moon calendar, treat the Calendar page as the entry point and follow its moon and astronomy links — the site's stated scope includes "moon phases, full moon dates and times, sunrise and sunset times." The Calendar page itself gives you the current phase and upcoming dated events, not a year-long table.

Using the Best Days feature

"Best Days" is traditional timing advice — the kind of folklore the Almanac is known for. The page shows one task per day under "Today Is the Best Day To…," with a "Know more" link for context. In the sample, that task was castrating animals.

Two practical notes:

• The advice is folk tradition, not veterinary or medical guidance. For anything involving animals or health, treat it as cultural interest and consult a qualified professional for the actual decision.
• The featured task changes daily, so if you're tracking a specific activity (planting, pruning, cutting hair), you'll need to check back or use the linked guide rather than expecting a full schedule on the Calendar page.

Getting daily updates by email

The page promotes a free email newsletter twice — once at the top ("For daily wit & wisdom, get the Almanac newsletter") and again at the bottom under "Get Almanac's Daily Updates." Signing up requires entering an email address in the provided field. The site does not state a price for the newsletter, and no pricing or payment details appear on the page, so treat cost and any account requirements as unconfirmed rather than assuming it's free of conditions.

If you'd rather not subscribe, the same daily content is available by visiting the Calendar page directly each morning.

When this Calendar is the right tool — and when it isn't

Use it if you want a lightweight daily ritual: a word, a tip, a riddle, the current moon phase, and a heads-up on holidays and seasonal turning points. It's also a reasonable starting point for equinox, solstice, and full moon dates before you dig into a dedicated astronomy source.

Look elsewhere if you need a schedulable calendar, printable planner, timezone-accurate sunrise/sunset tables, or a complete year of Best Days in one view. The Almanac Calendar is a daily reading page with links outward — not a planning system.

Media relations contacts are the specific people or offices a newsroom, journalist, or member of the public is directed to when they need an official comment, interview, statement, or public record from an organization. They are not general customer service lines. At Illinois State University, for example, the Media Relations and Strategic Communications office is the front door for news media, and its site separates media inquiries from FOIA requests and other university reporting. Use a media contact when you are on a deadline and need an authoritative answer; use a general contact when you are a student, parent, or community member asking about routine services.

Media contacts vs. general contacts

The distinction matters because it determines how fast you get a reply and whether you get one at all.

A media relations team exists to protect accuracy and timing: it finds the person who can actually speak for the institution and gets them to you before your deadline. That is different from a help desk, which answers you when it reaches your ticket.

Types of contacts typically listed

Media relations pages usually publish several distinct entry points, and mixing them up is the most common reason for a slow response.

• General media inquiries — a main phone number and email for journalists. This is the default starting point.
• Named staff contacts — a director or communications specialist, sometimes with a beat or topic area attached.
• FOIA / public records contacts — a separate officer or form, because records requests are legally distinct from press inquiries.
• After-hours or on-call press line — for breaking news outside business hours, when listed.
• Subject-matter experts — faculty or staff available for interviews, often organized by topic.
• Social media or newsroom accounts — useful for monitoring announcements, not for filing a request.

On the Illinois State Media Relations site, these functions sit alongside news, FOIA requests, and the University Report, which signals that each has its own path.

How to choose the right contact

Match the contact to the request, not to whoever is easiest to find.

1. Identify your request type. A quote, an interview, a document, or a factual confirmation each maps to a different channel.
2. Check for a topic or beat. If the page lists staff by area, pick the one covering your subject.
3. Prefer the published media channel over a personal address for first contact, unless a named reporter relationship already exists.
4. Use the FOIA channel for records. Asking a media officer for documents can add a step and delay you.
5. Use the after-hours line only for genuine after-hours news. Routine requests sent there may wait until morning.

If you are unsure, the general media inquiry address is the safe default — it is designed to be triaged.

What to include in a media inquiry

A complete first message is the single biggest factor in response speed. Include:

• Your name, outlet, and role
• Your deadline, with time zone
• The specific question or a short list of questions
• The format you need — phone, email, or on-camera interview
• Background and links so the team can prepare
• Your direct contact details for a fast reply

Vague requests ("Can someone comment on the university?") force a back-and-forth that costs you the deadline. Specific ones can be routed immediately.

Why a media contact may not respond, and how to follow up

Non-response usually has a structural cause rather than disinterest:

• The request went to a general inbox that is not monitored continuously.
• It arrived outside business hours with no after-hours expectation set.
• It was a records request sent to a press contact.
• The question was too broad to route.
• The spokesperson was already committed to other deadlines.

Follow up by replying in the same thread, restating your deadline and narrowing the question. If the first channel was a personal address, try the published media line. If you still get nothing and the request is for records, switch to the FOIA process. Keep the follow-up short and specific; a second vague email rarely helps.

Quick checklist

• Confirm whether you need a comment, an interview, or a document.
• Pick the matching contact: media, FOIA, or after-hours.
• Send one complete message with a clear deadline.
• Follow up in-thread before trying a new channel.
• Escalate to FOIA only for records, not for quotes.

The goal is simple: get your question to the person authorized to answer it, with enough context that they can answer before your deadline.