Discover workflows, ask questions, and share with confidence
Start by reading public ideas, questions, and workflows. When you want to join, create a profile protected only on your device; private notes and one-to-one sessions stay out of the way until you need them.
How to prepare a reproducible post
A useful tool question lets somebody else reproduce the same result. ByteQuant prepared the examples below; they are not user posts or evidence of live community activity. Reading them and trying the tools requires no relay connection.
Investigate a misplaced CSV column
State that the direction is CSV → JSON and that you expect two columns and one record. Quotes preserve the comma inside note; id stays a string. If you see three columns, compare the header, delimiter, and quotes. Share this two-line fixture instead of an entire customer file.
- Minimal input
id,note 007,"A,B"- Result to check
[{"id":"007","note":"A,B"}]
Demonstrate an encoding issue with a round trip
Encode first, then decode that exact output. Include the browser name, operation, and affected character in your post. A changed Ç or symbol points to a text encoding issue that an ASCII-only sample might miss. Base64 does not hide or encrypt secrets; keep passwords out of the sample.
- Minimal input
Çay ☕- Result to check
w4dheSDimJU= → Çay ☕
Replace “it does not work” with these details
- Tool name, selected operation, and browser.
- The smallest input without personal data, plus steps to reproduce.
- Expected output versus the actual output or error message.
- Whether the built-in example also fails; remove personal fields before sharing a screenshot.
Who can see each area?
- Global feed
- Connecting sends network requests to the independent relays you choose. Published content can be public and copied; a deletion request does not retract every copy.
- Device archive
- The local board is not automatically sent to the global feed. Consider access on a shared device; an exported pack is another copy wherever you save it.
- Direct session
- Share a P2P invitation only with the intended person. The recipient can copy the conversation; a direct connection does not guarantee later control over its content.
◇Advanced / private community toolsManage drafts that stay on this device, or start a temporary one-to-one session with a specific person.+
▣Private board on this deviceManage drafts, private groups, and portable packs that you do not want to send to a relay.+
Text is reviewed only in this tab. Create a link, download a file, or use your device share sheet without creating an account.
Private posts are excluded from share links and public board packs.This pre-check looks for explicit abuse, common personal-data shapes, secrets, and external links. It is not a moderation guarantee. GitHub is optional for persistent public publishing.▤Open the saved local boardShows posts, comments, groups, and export options stored on this device.+
◉One-time P2P sessionUse an invitation code to talk synchronously with one specific person. This is independent from the global feed.+
Talk to one person without a content server
Exchange invite and answer codes through a separate trusted channel. Messages travel only between the open browsers over an encrypted WebRTC DataChannel; ByteQuant stores no message history or member directory.
Waiting for connection
?Join the community in 3 stepsReading is free and profileless; network access and publishing always begin with your explicit action.+
- 1Approve the feed connectionRead that selected relay operators can see your IP address, then connect the global feed with one action.
- 2Create your portable profileYour private key is encrypted with AES-GCM using the device passphrase and is never sent to ByteQuant.
- 3Post and interact safelySign a locally screened post, then publish replies, reactions, revisions, and deletion requests through Nostr.
ByteQuant operates no relay or shared account database. The global feed comes from independent Nostr relays, and counts cover only loaded, signature-verified events. Delete publishes a signed request; no client can guarantee every relay removes an older copy.