The publisher submission FAQ

What can a group submit?

A factual profile correction, a dated public statement, or a source-backed explanation that helps readers understand an already-public event. Useful corrections include an alias, a biography detail, a disputed country association, a timeline date, or the provenance and rights of an emblem.

Keep it specific: identify the exact card and field, quote the current public wording, propose replacement wording, and attach public source references. Kinwilder remains an independent magazine. A profile is editorial coverage, not a group-controlled page or an offer of publicity services.

How do we request a change to our card?

Use the card’s exact directory ID. Prepare a plain-text proposal with the field, current wording, proposed correction, reason, source dates, and public evidence URLs. The local draft helper below provides that structure.

An enrolled publisher sends it through the existing statement action with a title such as Profile correction: GROUP-ID. There is no public API that directly edits a card. The proposal enters moderation. An editor assesses evidence and legal concerns, then applies any accepted card change through a reviewed repository change and website release. A receipt is not approval or a promise to use your wording.

Kinwilder publisher v1 protocol

Where is our group ID, and what if we are missing?

The ID is the final part of a profile address: /groups/akira uses akira. Use the directory label that actually represents your publisher; aliases do not authorize control of a different entry.

The API accepts existing directory IDs only. A new label must be added through editorial catalog review before enrollment. There is currently no public new-group registration endpoint, paid-listing service, or automatic profile creation. Do not borrow another group’s ID to get around that limit.

Kinwilder publisher v1 protocol

What is the full enrollment sequence?

1. Inspect the reference client and protocol. Generate an Ed25519 key locally; keep the private PEM off the website.
2. Send a signed enroll request for the exact group ID. Keep the returned enrollment ID, challenge text and expiry.
3. Publish that exact fresh challenge on an already-established first-party channel you control. The enrollment challenge lasts seven days; a newly created lookalike channel does not establish history.
4. Send the signed proof request with the enrollment ID and exact public proof-post URL.
5. Wait for editorial continuity review. Check the public key registry for your key’s current state.
6. Once active, sign a plain-text statement or card-correction proposal. Every submission still requires its own editorial review.

No legal name, email address, personal account password or private key is requested. Enrollment and publication have no guaranteed turnaround time.

Kinwilder publisher v1 protocol

What does Kinwilder actually authenticate?

Three different questions stay separate:

• Key control: an Ed25519 signature verifies that a request was signed by the corresponding private key.
• Channel continuity: an editor checks a fresh challenge on an independently established group channel, with provenance from at least two evidence domains.
• Factual accuracy: sources and incident evidence support a particular claim. The publisher’s own statement does not corroborate itself.

An active registry entry records a dated, scoped continuity assessment. It does not prove a legal identity, an entire membership roster, ownership of every alias, or the truth of every signed assertion.

Kinwilder publisher v1 protocol

Why can’t an impostor just upload a logo and sign?

Anyone can generate a key, repeat a group name or copy an emblem. None of those actions is enough for enrollment. The editor must establish the historical channel independently and find the fresh enrollment challenge at the submitted proof URL.

Copied old signatures, a newly registered domain, screenshots and repeated past claims do not replace that check. The API itself never follows a submitted URL. A moderator acquires bounded public text separately after checking the source. Doubt about channel provenance, takeover, seizure or authority can keep enrollment on hold.

Kinwilder publisher v1 protocol

Can the checks guarantee we are the original group?

No. A channel or key can be stolen, transferred, sold or seized. Activity labels can cover changing affiliates or unrelated teams, and public attribution can be disputed.

Verification is evidence of control and continuity at a particular time. It remains revocable and must be reconsidered when credible compromise evidence appears. The magazine can freeze new publication and hold pending statements. It will not resolve competing ownership claims simply by accepting the latest person to speak loudly.

Kinwilder publisher v1 protocol

Can every member register a separate publishing key?

Protocol v1 permits one active publisher key per directory group. An already-active group uses signed rotation or editorial recovery; registering another key is not a way to override it. Separate per-member accounts, role permissions and automatic multiple-key delegation are not implemented.

The group is responsible for authorizing its publishing voice and protecting key custody. Kinwilder does not need the private key. A split, rebrand or competing claim requires an editorial assessment; an alias or a country association does not resolve who should control a publisher slot.

Kinwilder publisher v1 protocol

Do we need to demonstrate an intrusion to prove affiliation?

No. Never attack a system, reveal access, post credentials, expose a victim, or obtain new private material to qualify for a profile. The identity process uses a fresh challenge on an established public channel.

Statements about incidents face a separate evidence review using lawful public material. Kinwilder does not commission intrusions or request stolen samples. Calling something “proof,” “research” or “ethical hacking” does not provide authorization to access someone else’s system.

18 U.S.C. § 1030 · California Penal Code § 502 · Criminal Code § 342.1

Is submission guaranteed to be non-traceable?

No. Kinwilder cannot guarantee non-traceability, perfect anonymity or protection from lawful legal process. The design supports a pseudonymous group publisher without asking for a personal identity.

The application does not retain client IP addresses or user-agent identifiers. That is narrower than a promise that no infrastructure metadata exists: network edges, hosting systems and error logs can reveal connection information. Devices, published text and external proof channels can also identify a source. Tor improves network separation only for applications correctly configured to use it; the Tor Project also rejects a perfect-anonymity guarantee.

Tor Project: anonymity and application configuration

How do we use the onion submission service?

Read the currently advertised onion hostname from /api/v1/info on the official magazine. Use the complete address through a supported Tor setup; an onion gateway is a third party, not the onion service.

The onion service serves the submission API, not the magazine’s React interface. Tor Browser can inspect its API information, but it does not sign statements or automatically route your terminal. The reference client does not start Tor. Its --base http://ADDRESS.onion option selects an origin; your client’s network traffic must separately be configured for Tor. The client’s own help documents the torsocks invocation for compatible systems. Verify your platform’s setup before sending anything sensitive.

Onion-service traffic is encrypted within Tor even though the API origin uses http://. This is not permission to use ordinary cleartext HTTP to a public website.

Tor Project: anonymity and application configuration · Tor Project: onion services · Kinwilder publisher v1 protocol

Who can read the text after it arrives?

Authorized Kinwilder moderators and administrators can read the private queue. HTTPS and onion transport protect a network connection; an Ed25519 signature authenticates text and does not encrypt it to one editor. The API is not an end-to-end encrypted source mailbox, a lawyer-client channel or a SecureDrop deployment.

Submit only material you are prepared for the magazine to review. Do not send personal identifiers, secrets or victim data. Avoid reference URLs containing access tokens or personal account details. A hosting or system compromise and valid legal demands remain possible; the FAQ cannot promise to prevent either.

Kinwilder sends its operator a private Zoho email alert after accepted API actions. The alert contains only the action type, opaque record references and receipt times; it excludes your text, group name, public key and proof/reference URLs. Email processing adds a separate provider and associated delivery metadata. The original submission stays in the private server queue; ordinary messages you choose to email directly are already held by Zoho.

Kinwilder publisher v1 protocol

Which parts deliberately become public?

An approved publisher registry can expose the group ID, public key and fingerprint, key status, dated channel check, proof URL, proof challenge/hash and rotation history. A published statement exposes its signed payload, timestamp, nonce, references, signature and editorial context.

This deliberately links publications to a continuing group pseudonym. It does not make a series of statements unlinkable, and it can link the pseudonym to an external public channel. Keep the private key private. An unpublished proposal begins in a private queue, but do not treat that as a contractual promise of confidentiality or immunity.

Kinwilder publisher v1 protocol

What is kept, pruned or backed up?

Scheduled pruning removes pending, held or rejected statements once their receipt is over thirty days old. A nonapproved enrollment is eligible thirty days after its seven-day enrollment expiry, rather than thirty days after creation. Replay receipts become eligible after seven days and used-work records after one day. The maintenance job is periodic; deletion is not promised at an exact second.

Fourteen daily local recovery snapshots can retain older private bodies beyond live-queue pruning. Approved enrollment records, public statements, key history and audit metadata remain. Statutory duties or valid preservation requirements can affect handling. Revoking a key stops future use and holds pending statements; it does not erase historical publications or copies held by others.

Server alert metadata is queued until mail-provider acceptance; delivered notification records are pruned fourteen days after acceptance during routine care. Pending delivery metadata is retained for retry and operator follow-up. Existing fourteen-day snapshots may retain older metadata. Operator alert copies in Zoho follow mailbox retention and applicable preservation requirements, separately from server queue pruning.

Kinwilder publisher v1 protocol

What should a useful submission contain?

Prefer original concise wording, a precise date or an explicitly approximate date, and exact public source URLs. Identify whether you are correcting a fact, disputing an attribution or issuing an attributed statement.

Describe technical mechanisms and defensive implications without delivering an operational attack chain. Say what is established, what is your claim and what remains uncertain. Do not inflate incident totals, money figures, membership, national origins or technical capability. A country flag describes sourced geography; it is not a membership census.

What is prohibited, even inside a “private” submission?

No attachments, images, screenshots, archives, encoded files, private keys, passwords, session tokens, stolen records, victim personal data or links intended to deliver those materials. No extortion demands, payment instructions, access sales, malware delivery, recruitment for crime, targeted threats or attack coordination.

Technical checks reject malformed or oversized envelopes, HTML and embedded-file patterns. They are not a complete detector of unlawful plain text. Moderators can hold or reject policy-violating material after receipt. Do not submit it in the first place, and do not send an image merely because it contains text.

Kinwilder publisher v1 protocol

Can we send a logo or change an origin flag?

Propose the exact public logo source URL, creator/source credit, rights information and date of use. Do not upload the image or encode it into a statement. Editors separately assess the identifying asset and rights before choosing a local emblem; a logo does not authenticate its user.

For geography, explain exactly what the evidence establishes: reported organizational links, an operational base, a multinational scope, or an affected organization’s location. These are different claims. A group name, language or flag preference does not establish the nationality or majority citizenship of its members. Uncertain geography can remain unknown.

Which evidence helps, and which does not?

A dated first-party statement can establish what that publisher said. A technical report, court record, advisory or affected organization’s public notice may support other specific facts. Give the source’s original date and its exact attribution scope; report dates and incident dates are different.

A self-claim, copied news story, screenshot, stolen record or several sites repeating the same assertion is not independent corroboration. Do not acquire private evidence for this process. Editors may retain an attributed disagreement without adopting your preferred conclusion.

When does a submission become trusted or published?

HTTP 202 Accepted means the intake accepted a request for processing. Enrollment state challenge asks for channel proof; review awaits an editor. An active key in the registry permits signed statements, not automatic publication.

Every statement begins pending. An editor can publish it as an authenticated publisher claim, with separate commentary and evidence, or hold/reject it. Corroboration belongs to particular factual findings. A card correction requires a separate reviewed editorial change. Neither a successful signature nor a published statement changes confirmed incident counters or rewrites attribution by itself.

Kinwilder publisher v1 protocol

How do we check progress or appeal a decision?

Keep your enrollment and statement receipts locally. Check /api/v1/publishers for approved key status and /api/v1/statements for approved statements. The current API has no private pending-status endpoint, guaranteed response window or automatic appeal decision. Absence from a public feed does not establish rejection.

For a disputed card entry, send one concise signed correction with additional lawful public evidence. Editors retain independent control and can preserve contested claims with context. Repeated submissions, a different key or a new alias do not bypass a hold. This publisher channel is not an emergency, victim-response or statutory legal-notice service.

Editorial contact: root@kinwilder.com. Ordinary email does not authenticate a group and is not an anonymous source channel. Use the signed API for a group-attributed statement. A download from the local correction helper is only a draft; it sends no request or email.

Kinwilder publisher v1 protocol

Which legal jurisdictions does this guide cover?

This is an AI-researched operational guide checked on 24 October 2026, with primary references for U.S. federal law, California law and Canadian federal law. It is not an attorney-reviewed legal opinion or a certificate that a particular submission or business model is lawful.

The official U.S. Code pages consulted state currency through 7 October 2026; the Canadian consolidations consulted state currency to 30 September 2026. Check their currency notices, later amendments, applicable regulations and case law. Canadian provincial/territorial rules and other jurisdictions can add duties; no province-specific assessment is claimed. An editor should obtain qualified U.S./California and Canadian advice when the facts, rights, sanctions or legal obligations are uncertain.

18 U.S.C. § 1030 · California Penal Code § 502 · Criminal Code § 342.1 · PIPEDA § 4: application and journalistic-purpose exception

Does a magazine invitation authorize hacking?

No. Kinwilder grants no permission to access third-party systems, intercept communications, damage data or obtain protected information. Its invitation is for lawful public reporting and corrections.

Relevant computer-misuse provisions include U.S. federal 18 U.S.C. § 1030, California Penal Code § 502, and Canada’s Criminal Code § 342.1 and § 430, with different elements and exceptions. None of this guide’s labels supplies the missing authority for a particular activity. Research authorization must come from the party entitled to grant it and remain within its scope; do not perform a new intrusion for coverage.

18 U.S.C. § 1030 · California Penal Code § 502 · Criminal Code § 342.1 · Criminal Code § 430

Can a sanctioned or restricted group use the FAQ to get clearance?

No. A country flag, alias match or valid signature is not a sanctions assessment. U.S. OFAC rules and Canadian sanctions can restrict dealings, resources or services, depending on the applicable program and facts. OFAC specifically warns about making or facilitating ransomware payments. Some risks extend beyond money; a free service is not automatically exempt.

Kinwilder offers no payments, ransom negotiation, access brokering, recruitment or coordinated promotion. Editorial enrollment/publication involving a potentially restricted actor must be held if the legal basis is unresolved. Applicable regulations, ownership/control, aliases, exceptions and any required authorization need qualified review. No automated sanctions screening or blanket journalism exemption is claimed here.

OFAC: cyber-related sanctions and ransomware advisory · Global Affairs Canada: sanctions essentials

Why keep independent reporting separate from services to a group?

U.S. federal material-support law, including 18 U.S.C. § 2339B, raises additional concerns for designated foreign terrorist organizations and covered conduct. Its application depends on the statutory elements and circumstances; this guide does not decide them.

The editorial boundary is concrete: Kinwilder decides its own coverage, context and corrections. It does not offer to polish a group’s recruitment, run its campaign, coordinate operations or supply specialist assistance. A claimed journalistic purpose or lack of payment is not a universal legal exemption. Potentially restricted engagement requires legal assessment before acting.

18 U.S.C. § 2339B · Global Affairs Canada: sanctions essentials

Do pseudonyms remove California or Canadian privacy duties?

No automatic exemption follows from using a key instead of a name. Linkable information may still engage privacy law. California’s CCPA has applicability rules, rights and exceptions that must be assessed; this FAQ is not a claim that every magazine is covered or exempt.

PIPEDA § 4(2)(c) has a specific journalistic/artistic/literary-purpose exception with a condition against collecting, using or disclosing that information for another purpose. A magazine label alone does not establish the condition for every activity. Subscriptions, marketing, payment processing and other uses need their own assessment, including applicable Canadian provincial law. A publisher signing key is not a substitute for a lawful privacy-rights procedure.

California Privacy Protection Agency: CCPA FAQ · PIPEDA § 4: application and journalistic-purpose exception

Will Kinwilder ignore court orders or guarantee source privilege?

No promise of legal immunity, absolute confidentiality, destruction of evidence or refusal of lawful process is made. Any legal demand must be assessed for validity, scope, applicable protections and preservation duties with qualified advice.

The application’s limited collection reduces some stored data; it does not control what providers, public archives or external channels retain. Public pseudonymous records may be linkable. Do not assume a reporter’s privilege, an intermediary safe harbor or a privacy exemption applies merely because the website is a magazine.

What does CC BY 4.0 mean for our submission?

The statement action requires publication permission under CC BY 4.0 with attribution to the group pseudonym. Offer only wording you have authority to license. The license allows downstream reuse subject to its terms, including attribution and indicating changes; complying recipients generally keep those permissions even if you later change your mind.

It does not transfer rights you do not own, authorize stolen information, override privacy rights, or automatically relicense an external logo or linked report. Publicly reachable does not mean public domain. Editors assess source rights separately; the profile is not a copyright, defamation or privacy safe harbor.

Creative Commons Attribution 4.0 · U.S. Copyright Office: copyright basics

How should we handle the signing key?

The reference client creates an Ed25519 private key in a local PEM file and sends only its public counterpart and signatures. The file is not password-encrypted by this client. Protect it using appropriate operating-system permissions and secure storage/backups. On POSIX systems the client rejects group/world-accessible key files; Windows needs appropriate access controls.

Do not paste the key into a browser, upload it as proof or put it in a public repository. The reference client is a small inspectable tool, not a managed key vault. A lost or stolen private key cannot be repaired by changing a group display name.

Kinwilder publisher v1 protocol

How do rotation, revocation and lost-key recovery work?

Rotation requires the old key and a new key to sign the same transition. Generate the successor locally, then use the client’s rotate command with --new-key-file. Historical statements retain their original signatures and a successor trail.

A signed revoke request stops new writes and holds pending statements. If the old key is lost or compromised, notify the editorial desk through the already-established channel and undergo fresh continuity review; there is no name-based password reset. Editors can revoke through restricted administration. Do not assume a compromised channel can safely authorize its own recovery.

Kinwilder publisher v1 protocol

What are the current request and rate limits?

Protocol v1 allows a 16 KiB JSON envelope, an 8–180 character title, a 40–9,000 character body and at most eight source URLs. Character limits do not remove the total UTF-8 byte limit. Use HTTPS references or valid v3 onion references; attachments and embedded files are excluded.

Accepted writes are limited to twenty per key in a rolling twenty-four-hour window. The service has a separate sixty/hour anonymous enrollment/proof pool and a 240/hour authenticated publisher pool, plus bounded queues. Each write needs a fresh expiring work challenge, signature timestamp within five minutes and unique nonce. Current machine-readable limits in the protocol take precedence if the service changes.

Kinwilder publisher v1 protocol

What do common API responses mean?

Keep the device clock accurate. A timestamp error is not proof of censorship. Do not switch to an unverified endpoint or cleartext public connection when a privacy-sensitive route fails. The reference client creates a new request each run, so avoid repeated duplicate submissions.

Kinwilder publisher v1 protocol

Can technical acceptance prove the submission is lawful?

No. Cryptography, proof of work and schema checks establish limited technical properties. They cannot determine permission to access a system, ownership of words or images, all privacy interests, sanctions status, defamation, or every criminal-law issue.

Editorial moderation is a separate gate and uncertain legal questions remain unresolved until reviewed. Do not read a 202 response, a profile listing or an authentication label as a legal approval. This is also why lawful public references and a narrow factual correction are preferable to dumping private material.

Does a submission notify the editor, and can we email instead?

Accepted signed enrollment, proof, statement, key-rotation and revocation actions queue an operator alert. Statements labelled “Profile correction:” receive correction-specific instructions. Alerts are checked about every five minutes and may be grouped by action when several arrive; transport outages can delay delivery. A valid API receipt remains valid if email delivery is delayed. Replaying an identical signed request does not enqueue another alert. Rejected malformed, unsigned or rate-limited traffic does not generate individual emails.

Alerts contain action type, opaque record references and receipt times, not the submitted body, group name, key, proof URL or reference links. No alert approves or publishes anything. Enrollment and proof require continuity review; statements require editorial review; valid two-key rotation and signed revocation already apply their documented key changes.

For ordinary editorial enquiries or public-source tips, email root@kinwilder.com. The full message and normal email metadata are handled by Zoho; a claimed From address does not prove group affiliation, and email does not provide the onion route or perfect anonymity. Do not send attachments, secrets, stolen records, victim details or payment demands. The magazine does not automatically treat email as an authenticated API submission.

Kinwilder publisher v1 protocol