Skip to main content

Seeing something I haven't seen before, building something that never existed before.

Collecting new skills and experiences like precious shinies.

Artisanal bit wrangler & @elgg expert, @withknown core contributor.

Hacker, Wanderer.

Have laptop, will travel.

Pushed a bunch of @withknown changes: translation hooks for templates, PHP 7.2 compatibility, refresh/remove option for link previews, a couple of bug fixes, and Gettext support.

Replied to a post on :

Closing this, this sort of discussion should go to the discussion group!forum/known-dev or IRC channel.

But, in short there are a number of very good reasons why Known uses a (number of different options of) database for storage.

For those who feel strongly about avoiding database for backend storage, and are prepared to accept the consequences, I encourage you to look at the DataConcierge class hierarchy. It is entirely possible to write a plugin that maps the data queries to another mechanism/flat file store (although I imagine search will suffer unless some effort is taken to provide some sort of lookup mechanism), however I doubt this'll ever be something that is built out for the core project.

Starting an exciting new project today by building out the data model.

I put together some (unofficial) IRC logging for @withknown's channel: HTH :)