diff --git a/LOGGING.md b/LOGGING.md
index b0f4cc50..6ff4ee61 100644
--- a/LOGGING.md
+++ b/LOGGING.md
@@ -18,21 +18,23 @@ In development mode, you can control logging from the browser console:
```javascript
// Enable debug logging
-jumbleDebug.enable()
+imwaldDebug.enable()
-// Disable debug logging
-jumbleDebug.disable()
+// Disable debug logging
+imwaldDebug.disable()
// Check current status
-jumbleDebug.status()
+imwaldDebug.status()
// Use debug logging directly
-jumbleDebug.log('Debug message', data)
-jumbleDebug.warn('Warning message', data)
-jumbleDebug.error('Error message', data)
-jumbleDebug.perf('Performance message', data)
+imwaldDebug.log('Debug message', data)
+imwaldDebug.warn('Warning message', data)
+imwaldDebug.error('Error message', data)
+imwaldDebug.perf('Performance message', data)
```
+(`jumbleDebug` is still exposed as an alias for compatibility.)
+
### For Code
Use the logger instead of direct console statements:
@@ -69,7 +71,7 @@ logger.perf('Performance metric', data)
The logger automatically configures itself based on:
1. **Environment**: Debug logging is disabled in production builds
-2. **Local Storage**: `jumble-debug=true` enables debug mode
+2. **Local Storage**: `imwald-debug=true` enables debug mode (legacy: `jumble-debug=true`)
3. **Environment Variable**: `VITE_DEBUG=true` enables debug mode
## Performance Impact
@@ -103,12 +105,12 @@ To enable debug mode:
1. **In Browser Console** (development only):
```javascript
- jumbleDebug.enable()
+ imwaldDebug.enable()
```
2. **Via Local Storage**:
```javascript
- localStorage.setItem('jumble-debug', 'true')
+ localStorage.setItem('imwald-debug', 'true')
```
3. **Via Environment Variable**:
diff --git a/PROXY_SETUP.md b/PROXY_SETUP.md
index 39110f61..026d4e9c 100644
--- a/PROXY_SETUP.md
+++ b/PROXY_SETUP.md
@@ -11,7 +11,7 @@ When building and deploying on the remote server, you need to build the Docker i
**IMPORTANT:** `VITE_PROXY_SERVER` must be set during Docker BUILD (as a build argument), NOT at runtime. It gets baked into the JavaScript bundle.
-Rebuild the Jumble image with the correct proxy URL:
+Rebuild the Imwald image with the correct proxy URL:
```bash
# Build with the correct proxy URL (baked into the JS bundle)
@@ -101,7 +101,7 @@ docker-compose up -d
The client uses **`POST /api/piper-tts`** on the **same host** as the app (default build: `VITE_READ_ALOUD_TTS_URL=/api/piper-tts`) so the browser does not need cross-origin CORS to aitherboard.
-Add these **before** the catch-all `ProxyPass /` to the Jumble static container (same ordering as `/sites/`):
+Add these **before** the catch-all `ProxyPass /` to the Imwald static container (same ordering as `/sites/`):
```apache
ProxyPass /api/piper-tts http://127.0.0.1:9876/api/piper-tts
@@ -117,7 +117,7 @@ curl -sS -o /tmp/t.wav -w "%{http_code}\n" -H "Content-Type: application/json" \
Expect **200** and a WAV file. **Local dev:** `npm run dev` proxies `/api/piper-tts` → `http://127.0.0.1:9876` in `vite.config.ts`.
-Rebuild the Jumble image after changing `VITE_READ_ALOUD_TTS_URL`; `Dockerfile` passes `ARG`/`ENV` `VITE_READ_ALOUD_TTS_URL` into `npm run build`.
+Rebuild the Imwald image after changing `VITE_READ_ALOUD_TTS_URL`; `Dockerfile` passes `ARG`/`ENV` `VITE_READ_ALOUD_TTS_URL` into `npm run build`.
## Update Proxy Server's ALLOW_ORIGIN
@@ -194,7 +194,7 @@ sudo systemctl restart apache2
RequestHeader set Host "127.0.0.1:8090"
- # Reverse Proxy for the main Jumble app (needs Host header preserved)
+ # Reverse Proxy for the main Imwald app (needs Host header preserved)
ProxyPreserveHost On
ProxyPass / http://127.0.0.1:32768/
ProxyPassReverse / http://127.0.0.1:32768/
@@ -228,10 +228,10 @@ sudo systemctl reload apache2
# Test with a real URL - the code constructs /proxy/sites/{encoded-url}
curl https://jumble.imwald.eu/proxy/sites/https%3A%2F%2Fexample.com
# Should return example.com's HTML, NOT jumble.imwald.eu's HTML
-# If you see Jumble HTML, the proxy server is using the Host header instead of the URL path
+# If you see Imwald HTML, the proxy server is using the Host header instead of the URL path
```
-**If the test returns Jumble HTML instead of the requested site's HTML:**
+**If the test returns Imwald HTML instead of the requested site's HTML:**
The proxy server is using the `Host` header (`jumble.imwald.eu`) to determine what to fetch. Update your Apache config to use `ProxyPreserveHost Off` for the `/proxy/` path:
@@ -272,9 +272,9 @@ docker build \
## Troubleshooting
-### If Proxy Returns Jumble HTML Instead of Requested Site
+### If Proxy Returns Imwald HTML Instead of Requested Site
-If you've set `ProxyPreserveHost Off` but still get Jumble HTML, test the proxy server directly:
+If you've set `ProxyPreserveHost Off` but still get Imwald HTML, test the proxy server directly:
**1. Test the proxy server directly (bypassing Apache):**
```bash
diff --git a/README.md b/README.md
index e5dc4aab..c041f42b 100644
--- a/README.md
+++ b/README.md
@@ -2,20 +2,20 @@
+
logo designed by Daniel David
-# Jumble — **ImWald Edition** +# Imwald -**Maintainer: [Silberengel](https://github.com/Silberengel)** · Hard fork of [Cody Tseng’s Jumble](https://github.com/CodyTseng/jumble) +**Maintainer: [Silberengel](https://github.com/Silberengel)** · Evolved from [Cody Tseng’s Jumble](https://github.com/CodyTseng/jumble) -A Nostr web client focused on relay feeds, discovery, and spells. This repository is the **ImWald** line: same core ideas as upstream, with a substantial navigation and information-architecture rewrite (see below). +A Nostr web client focused on relay feeds, discovery, and spells. **Imwald** keeps the same core ideas as upstream, with a substantial navigation and information-architecture rewrite (see below). The public instance lives at [jumble.imwald.eu](https://jumble.imwald.eu). --- -## Major rewrite (this fork) +## Major rewrite (this line) High-level changes versus a “stock” Jumble-style layout: @@ -47,11 +47,10 @@ High-level changes versus a “stock” Jumble-style layout: ### Other - Sidebar layout tuned for **long translations** (e.g. German) so labels don’t sit on the divider. -- Branding in-app: **Im Wald**. --- -## Features (still core to Jumble) +## Features - **Relay feeds:** Browse content through relays, sets, and favorites - **Relay-friendly requests:** Efficient subscriptions where possible @@ -60,17 +59,17 @@ High-level changes versus a “stock” Jumble-style layout: ## Screenshots -
+
-
-
+
+
+
Loading Jumble…
+Loading Imwald…