GM

Just published a new version of Marco with basic spam protection: You can now mark read relays as trusted in order to show any and all content from them by default. Content from untrusted relays is only shown automatically when it's your own, or from a followed pubkey; otherwise you have to explicitly reveal the photos via link in the place details. View quoted note →

Tried out Qwen 3.8 VL 14B for detecting photo contents and the results were absolutely brilliant. I think I have a viable path to automated moderation for place photos in Marco now, allowing new Nostr users to submit map content without having to have an established reputation yet. Also, I came up with a neat design for configurable relay trust, i.e. show all content from trusted (private and/or moderated) relays, but only personal and WoT content from untrusted ones. Tuning some last UI bits for that, deploying tomorrow.

GM

In Alby, when first signing a Nostr event for a new domain, it offers some beginner-friendly options for how paranoid you want to be about signing. One of them is "Let's be reasonable". Apparently, someone thought it's reasonable to allow arbitrary apps to auto-sign kind 1 events, which I find entirely unreasonable. So, if you also use that extension for Nostr, and you also don't want some vibecoded thing to auto-post to your timeline, here's your warning.

🎉 Just finished Island Bitcoin Vibe! Score: 1200/1200 ⚡ Lightning Bitcoin Expert Off-Ramp Bonus: 100/200 🏧🤝 Bitcoin Center: 1200/1200 🎓 Vibe Coding Camp: 300/1500 💻 Leaderboard Score: 2800 Taught 3 island businesses to accept bitcoin 🌴₿

Hilarious bug report: > Steps to reproduce: > 1. Burn money and the planet by wasting G/CPU cycles on make-belief stuff > 2. Try to monitor that errand using zeromq > 3. Fail to see the errors of your way because bitcoin isn't listening on zeromq

GitLab

Consider re-enabling zeromq support (#5) · Issues · Arch Linux / Packaging / Packages / bitcoin · GitLab

Description: With the