zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,560 documents

Filters
  1. Step 2: Feature Description – GPG agent leak

    Debug mode: enabled (project default via .railspikedebugon)

    docs/plans/gpg_agent_leak/gpg_agent_leak_step2_feature_description.md Plans Plans and history

  2. Step 3: Development Plan – GPG agent leak

    docs/plans/gpg_agent_leak/gpg_agent_leak_step3_development_plan.md Plans Plans and history

  3. Step 4: Implementation Summary – GPG agent leak

    docs/plans/gpg_agent_leak/gpg_agent_leak_step4_implementation_summary.md Plans Plans and history

  4. Future Feature Note: Guest Keypair + Proof-of-Work Voting

    Not scheduled yet.

    docs/plans/guest_identity_proof_of_work_voting.md Plans Plans and history

  5. guided_php_setup_fallback_step1_solution_assessment.md

    Please write Step 1 of docs/fdp/FEATUREDEVELOPMENTPROCESS.md for the more comprehensive no-PHP fallback we discussed before.

    docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step1_solution_assessment.md Plans Plans and history

  6. guided_php_setup_fallback_step2_feature_description.md

    The existing missing-PHP fallback points to general setup documentation, leaving users to find instructions for their environment.

    docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step2_feature_description.md Plans Plans and history

  7. guided_php_setup_fallback_step3_development_plan.md

    docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step3_development_plan.md Plans Plans and history

  8. guided_php_setup_fallback_step4_implementation_summary.md

    docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step4_implementation_summary.md Plans Plans and history

  9. Hide Messages new-message form — Railspike debug log

    docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_debug_log.md Plans Plans and history

  10. hide_messages_new_message_form_step1_solution_assessment.md

    A user found the "New message" form on the /messages/ page confusing, thinking it is a registration form.

    docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step1_solution_assessment.md Plans Plans and history

  11. hide_messages_new_message_form_step2_feature_description.md

    The “New message” recipient form on /messages/ can be mistaken for registration.

    docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step2_feature_description.md Plans Plans and history

  12. hide_messages_new_message_form_step3_development_plan.md

    docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step3_development_plan.md Plans Plans and history

  13. hide_messages_new_message_form_step4_implementation_summary.md

    docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step4_implementation_summary.md Plans Plans and history

  14. High-traffic absent retractions — Railspike debug log

    No supported findings.

    docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_debug_log.md Plans Plans and history

  15. high_traffic_absent_retractions_step1_solution_assessment.md

    Effort study: railspike-effort, cycle v3/hightrafficabsentretractions; host ledger, standing enrollment R1/P2.

    docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_step1_solution_assessment.md Plans Plans and history

  16. high_traffic_absent_retractions_step2_feature_description.md

    Effort study: railspike-effort, cycle v3/hightrafficabsentretractions; host ledger, R1/P2.

    docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_step2_feature_description.md Plans Plans and history

  17. high_traffic_absent_retractions_step3_development_plan.md

    Effort study: railspike-effort, cycle v3/hightrafficabsentretractions; host ledger, R1/P2.

    docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_step3_development_plan.md Plans Plans and history

  18. high_traffic_absent_retractions_step4_implementation_summary.md

    Effort study: railspike-effort, cycle v3/hightrafficabsentretractions; ledger, R1/P2.

    docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_step4_implementation_summary.md Plans Plans and history

  19. high_traffic_diagnostic_explanation.txt

    docs/plans/high_traffic_diagnostic_explanation.txt Plans Plans and history

  20. High-traffic mode — Railspike debug log

    No supported findings.

    docs/plans/high_traffic_mode/high_traffic_mode_debug_log.md Plans Plans and history

  21. high_traffic_mode_step1_solution_assessment.md

    I want to design high-traffic mode which uses the following structure:

    docs/plans/high_traffic_mode/high_traffic_mode_step1_solution_assessment.md Plans Plans and history

  22. high_traffic_mode_step2_feature_description.md

    Repeated public-page requests consume PHP capacity even when slightly stale shared HTML would suffice.

    docs/plans/high_traffic_mode/high_traffic_mode_step2_feature_description.md Plans Plans and history

  23. high_traffic_mode_step3_development_plan.md

    Deliver operator UI/CLI enable → bounded first generation → session-bearing Apache warm hit → atomic popularity-driven cron refresh → disable/recovery.

    docs/plans/high_traffic_mode/high_traffic_mode_step3_development_plan.md Plans Plans and history

  24. high_traffic_mode_step4_implementation_summary.md

    Branch: feature/high-traffic-mode.

    docs/plans/high_traffic_mode/high_traffic_mode_step4_implementation_summary.md Plans Plans and history

  25. high_traffic_toggle Railspike debug log

    docs/plans/high_traffic_toggle/high_traffic_toggle_debug_log.md Plans Plans and history

  26. high_traffic_toggle_step1_solution_assessment.md

    Effort study: railspike-effort / v3/hightraffictoggle; ledger.

    docs/plans/high_traffic_toggle/high_traffic_toggle_step1_solution_assessment.md Plans Plans and history

  27. high_traffic_toggle_step2_feature_description.md

    Effort study: railspike-effort / v3/hightraffictoggle; ledger.

    docs/plans/high_traffic_toggle/high_traffic_toggle_step2_feature_description.md Plans Plans and history

  28. high_traffic_toggle_step3_development_plan.md

    Effort study: railspike-effort / v3/hightraffictoggle; ledger.

    docs/plans/high_traffic_toggle/high_traffic_toggle_step3_development_plan.md Plans Plans and history

  29. high_traffic_toggle_step4_implementation_summary.md

    Effort study: railspike-effort / v3/hightraffictoggle; ledger.

    docs/plans/high_traffic_toggle/high_traffic_toggle_step4_implementation_summary.md Plans Plans and history

  30. History purge — Railspike debug log

    docs/plans/history_purge/history_purge_debug_log.md Plans Plans and history

  31. history_purge_step1_solution_assessment.md

    Effort study: railspike-effort / v3/historypurge; ledger, standing P2 enrollment.

    docs/plans/history_purge/history_purge_step1_solution_assessment.md Plans Plans and history

  32. history_purge_step2_feature_description.md

    Effort study: railspike-effort / v3/historypurge; ledger, standing P2 enrollment.

    docs/plans/history_purge/history_purge_step2_feature_description.md Plans Plans and history

  33. history_purge_step3_development_plan.md

    Effort study: railspike-effort / v3/historypurge; ledger, standing P2 enrollment.

    docs/plans/history_purge/history_purge_step3_development_plan.md Plans Plans and history

  34. history_purge_step4_implementation_summary.md

    Effort study: railspike-effort / v3/historypurge; ledger, standing P2 enrollment.

    docs/plans/history_purge/history_purge_step4_implementation_summary.md Plans Plans and history

  35. Home Compact Thread Compose Plan

    As a user, I want to be able to start a new thread from the home page, using a compact compose field above the feed, similar to the x.com homepage.

    docs/plans/home_compact_thread_compose_plan_v1.md Plans Plans and history

  36. HTTP OpenPGP.js Failure Fix Plan

    When the live site is opened over plain http://, browser-side identity setup can show:

    docs/plans/http_openpgp_failure_fix_plan_v1.md Plans Plans and history

  37. Human-readable format audit

    Policy: CONTRIBUTING.

    docs/plans/human_readable_formats_checklist.md Plans Plans and history

  38. Identity Bootstrap GnuPG Import-Gap Remediation Plan

    The reported failure is an unusable-import problem, not evidence of a bad browser signature.

    docs/plans/identity_bootstrap_signature_verification/identity_bootstrap_signature_verification_import_gap_remediation_plan_v1.md Plans Plans and history

  39. Identity Bootstrap Signature Verification Investigation

    While creating a post without an existing browser identity, the first automatic identity-bootstrap attempt can fail with:

    docs/plans/identity_bootstrap_signature_verification/identity_bootstrap_signature_verification_investigation.md Plans Plans and history

  40. identity_bootstrap_signature_verification_step1_solution_assessment.md

    Please review docs/plans/identitybootstrapsignatureverification/identitybootstrapsignatureverificationinvestigation.md and write Step 1 of docs/fdp/FEATUREDEVE…

    docs/plans/identity_bootstrap_signature_verification/identity_bootstrap_signature_verification_step1_solution_assessment.md Plans Plans and history