web_publishing.md

Fuzzr Web Publishing

Analogous to a CMS (not static site), but self-hosted on-prem, using:

• CloudFlare Argo tunnel daemon
• CommonMark & YFM rendering

0.1 - Basic Content Publishing

• Publish page can both upload text and images
  • Switch between text and image upload
  • Additional metadata fields on publish screen:
    • Title
    • Description
    • Tags
    • Path
• Content list
• Warp server
  • Can respond with text and image responses
• Configure cloudflared Argo tunnel daemon
  • https://github.com/cloudflare/cloudflared
  • https://developers.cloudflare.com/argo-tunnel/

0.1.1 - FuzzrWeb Viewer

• CommonMark rendering
• Links navigate to other paths

0.2 - Web UI

• Iced web UI
• Websockets
• CBOR packets
• Static file server
• Usage and Setup Documentation for Publishers

0.2.1 - Monochrome Design

• Styles
  • Monochrome (two colors)
  • Thin lines (2px)
  • Blunt corners (2px rounded)
• Themes
  • Dark theme
  • Light theme
  • Serverside detection
  • Fallback clientside detection
  • Button for dark mode setting
  • Dark mode setting persistence
  • Fallback to default (dark theme)

0.2.2 - Multi-site Support

• Support multiple site profiles, and multiple Argo tunnel configurations per Fuzzr client

0.3 - Crypto monetization v1 - scrapped

• Miner config
  • Communicate with locally running xmrig HTTP API
• Wallet config
  • Communicate with locally running monerod JSON-RPC API
• Mining pool verification
  • reqwest to pool endpoint

0.4 - User-generated content

• Token / Cookie client authentication
• Voting (in MH)
  • (1 MH can usually be reached within 5-20 minutes of xmrig mining, dependent on hardware)
• Comments

0.5 - P2P

• P2P IPFS (for more than just local storage backend)
• Publisher notifications
• Subscriptions

Backlog / Unprioritized

• Save text in local Git site repo, similar to how static sites do.
  • This will require making a git-IPFS API. This could also allow us to host our code on here, too.

Additional tasks

• Look into CloudFlare cache for offline / maintenance operation
• Look into CloudFlare HTTP/3 to HTTP/2 and HTTP 1.1 backward compatibility

Ongoing technical decisions

• Decide on data backend: ipfs (embedded dht), sled (embedded LSM-tree k/v store), pallet (embedded searchable document store, unmaintained, design flaws, tantivy, but promising)
  • Start with existing ipfs-embed-rs, but it's currently switching to a SQLite backend to better support object GC, which may or may not be desirable, depending.
• Future HTTP/3 support: h3 -> hyper -> warp