Search Results for "ram"

Petoron P2P Messenger (P-P2P-M) Architecture: Pure P2P - no servers, no databases Key storage: Keys generated in memory, never stored, erased after use Metadata: Only IP and port exist during the session - everything else is encrypted & obfuscated Encryption: PQS v1.2 - PBKDF2-HMAC-SHA256 (200k), BLAKE2s-MAC, custom stream cipher + fake padding Authentication: BLAKE2s-MAC (16 bytes) - instant failure on any data change Packet obfuscation: --stealth mode - padding, hidden structures Connection: Direct peer-to-peer only Anonymity: No accounts, logins, or phone numbers Third-party access: Impossible without physical access to both peers during session History: No storage — all in RAM, wiped on close Message size: Limited only by RAM & MTU — no artificial limits External dependencies: None DPI/blocking resistance: Harder to detect, can be masked Autonomy: Fully offline until peers connect 26.01.26 Add pqs_chat_tor.py github.com/01alekseev/Petoron-P2P-Messenger

This app is meant for a simplified user experience, perfect for note takers. It has a good encryption system, and the best feature is that it works on the CLI, so its compatibility is great.

...Running Tezos Nodes (particularly Archive Nodes) can take massive amounts of storage when fully synced (~300 GB). 16GB of memory is recommended for running Tezos Nodes, along with the other processes alongside it. 8GB of ram should suffice, but it might not be comfortable for the containers, nor for anything else running on the machine.

Script to import maildir mail into gmail with metadata.

The most easy-use BitTorrent Client ever. It has features of little ram eating (3-5MB), detailed tray icon hint (show status of DL), history recording, Integration with TorrentSpy, firewall & CPU usage Setting, multi-language support, etc.