Everything it does.
Without the wall of text.

BUILT ON A HISTORY WORTH PRESERVING

Architecture that refuses the usual answer

SNAPSMACK did not appear from nowhere. It follows a trail broken by earlier photoblogging projects and the people who sustained them, often with too little help or recognition. Preserving that history means acknowledging their work, learning from what they endured, and carrying the best of their ideas forward.

Noah Grey comes first. He inspired me as a photographer, a creator, and a person. He is senpai. I am kohai. SnapSmack is the kohai’s offering. His photographs and his work on Greymatter showed me that publishing software could be personal, independent, generous, strange, and unmistakably human.

No arbitrary plugins. In SnapSmack, a skin manifest is not executable code. It is a validated, declarative shopping list describing the skin and naming the approved layouts, controls, fonts, and effects it wants. The CMS then supplies those capabilities from its own shared, reviewed library. A skin can ask for the masonry engine or a film effect; it cannot arrive carrying an unknown script and run it.

This keeps design separate from machinery. The same library engine can serve many radically different skins, and a security or compatibility repair made there reaches every skin that declared it. Removing a skin removes its presentation without leaving an abandoned plugin behind. The idea owes a debt to b2evolution's resistance to plugin hell; SNAPSMACK takes the boundary further.

Support without a public forum surface. The support forum lives inside authenticated SNAPSMACK administration. Operators can ask for help from the software itself, while the usual public registration, login, and posting endpoints are not left outside for bots and drive-by spammers.

This decision owes something to Jay Williams' candid account of the attempted Pixelpost rewrite. Jay deserves enormous credit: he wrote most of the code that moved Pixelpost from version 1.5 to 1.6, contributed substantially to the rewrite, and spent countless hours helping its users. He deserves far more recognition for that work than he received. SNAPSMACK stands in the shadow of that work.

As Pixelpost's last active developer and moderator, Jay described automatic spam across the forum and blog as nearly impossible for one person to clean up. He was equally clear that the rewrite was put on hold for broader reasons: too few developers, too little available time, and the difficulty of maintaining the site and finishing the software without the collaboration the project needed. That was not a failure of effort. SNAPSMACK's internal forum applies one practical lesson from his experience: public support infrastructure should not be allowed to consume the limited time available to maintain the software itself.

A deliberately layered security system. Authentication, authorization, abuse prevention, signed distribution, integrity monitoring, breach containment, recovery, fleet intelligence, and public audit closure reinforce one another rather than operating as isolated features. GOBSMACKED adds local stylometric ban-evasion detection to the privacy-preserving federated troll-reputation system.

None of those ingredients is being claimed as an invention. What is unusual is the approach: putting all the fixings on the burger and bringing the coordinated architecture and security depth of paid software to freeware built for a small community.

See the eight-layer security stack →   Read the closed security audits →