Search Results for "web-browser"

...On top of this platform, we have built two apps so far: Ente Photos (an alternative to Apple and Google Photos) and Ente Auth (a 2FA alternative to the deprecated Authy). This monorepo contains all our source code - the client apps (iOS / Android / F-Droid / Web / Linux / macOS / Windows) for both the products (and more planned future ones!), and the server that powers them.

The In-Browser File Encrypter is a simple web application that enables you to securely encrypt your files directly in your browser using the AES-256 encryption algorithm in CBC mode. Check it out at: https://codepen.io/Northstrix/pen/xxvXvJL and https://northstrix.github.io/In-Browser-File-Encrypter/V1.0/web-app.html GitHub page: https://github.com/Northstrix/In-Browser-File-Encrypter The download shortcut: https://sourceforge.net/projects/in-browser-file-encrypter/files/V1.0%20%28Improved%20UI%29/V1.0%20%28Improved%20UI%29.zip/download Successfully tested in Google Chrome on Windows 11 and Fedora 40.

Emojis of Death is a down and dirty browser app, written in HTML. It's HTML, so it will work on anything a web browser can run on. It's purpose is to hide text strings in emojis, which you can then text or email. An encoded emoji can hold quite a bit of text. The receiver will need Emojis of Death as well, to decode the emoji. The file's small size makes it perfect for your phone.

An experimental cloud storage service built with Next.js, featuring client-side file encryption, a dedicated password vault, advanced integrity verification functionality, and a convenient UI. Lakhash is also equipped with the password vault. Check it out at https://lakhash.netlify.app GitHub repository: https://github.com/Northstrix/Lakhash Codeberg repository: https://codeberg.org/Northstrix/Lakhash/ The related Medium article can be found at...

VaultKeepR is a decentralized, open-source password manager where everything is encrypted client-side using XChaCha20-Poly1305 and Argon2id before leaving your device. Unlike most alternatives, it encrypts metadata too -- device names, sync data, and beneficiary info never exist in plaintext on any server. Vault data is stored on IPFS (content-addressed, no central database). Cross-device sync uses encrypted CRDTs (Automerge) with no server involved in the merge. Vault recovery is handled...