(Redirected from idno)
Known is an open publishing / community platform project. It aims to be a simple, beautiful way to share your story using a variety of media from any device. It adheres to the IndieWeb technologies and principles.
Goals & Model
Known is also a full-time business endeavor with the following paid products:
It is currently concentrating on higher education educators and institutions as its first customers.
Known was released in September 2014. Packages can be downloaded from withknown.com.
Known was released at withknown.com in September 2014. Both a fully-hosted version and a self-hosted version are available. Users will be able to move their content from one to the other, in order to (for example) try the software using the hosted version before configuring their own server.
Documentation is being written at docs.withknown.com.
Plugins & themes
Known has a full plugin architecture, making use of PHP lazy loading and the observer pattern. This makes it very easy to create new content types or behaviors.
Known is being developed with the rule that "indie" content - internal posts, likes, etc - are bundled as included plugins in the main source code repository. If you want to POSSE to external sites, you need to install those plugins separately (although they may also be included in a downloadable distribution of the content).
Currently, content includes:
Supported webmention annotations include:
Known also has a Webfinger endpoint that plugins can extend.
People currently using Known as their primary site:
People currently using Known as a secondary site or trying it out:
People currently using Known as a public stream for a private community
As of September 25, 2014, there were over 3,000 Known sites, spread between the Known service and self-hosted sites.
Setup Known on nginx
User:elliottucker.net has posted a full how-to here https://elliottucker.net/2014/setting-up-known-with-nginx-indieweb. Note - the source code change is no longer required and you can now also use Known with MySql.
User:rascul.io provided his nginx configuration (based on a more recent version of Known) https://gist.github.com/rascul/ad665c9df9898c6e5074
User:kylewm.com tried unsuccessfully to reproduce reported issues with callbacks from Twitter and Facebook. Here is the configuration that worked for me https://gist.github.com/kylewm/7d8cbc9a72984d67c646
The current official documentation says that no config.ini file is needed to use Mongo, but this appears not to be the case any more. Mongo is only used now if it's explicitly specified in the config.ini file, e.g.,
(of course replace /var/www/data with your chosen data directory)
Fix 404 Not Found on /begin
This usually means .htaccess is missing or more often, not allowed, based on the Apache configuration. If you manually visit /index.php/begin instead and see a landing page, it means that htaccess is not being allowed to rewrite URLs.
At least in recent versions of Ubuntu, Apache is configured by default with AllowOverride Off. To allow, create a new <Directory> configuration in /etc/apache2/apache2.conf for your Known install, with AllowOverride All, and restart Apache.
Plugins and Themes Missing
We're not sure what causes this yet, it should "just work". Some things to check:
Update: This seems to have been fixed in version 0.6.3
New content types
Known is designed to be a multi-user system (although Ben and Erin are currently using it as single-user sites). The intention, therefore, is to implement a traditional asymmetrical social networking friends / following model - with an IndieWeb spin.
In a future embodiment, each step in the webmention process could be signed on a per-user basis (I'm interested in HTTP signatures, with keys exchanged / assigned at the point of mention. This would allow content to be made privately available to individual users. Other methods of retrieving private web content should also be considered.
Because it's not enough to publish: a way to _consume_ IndieWeb content from a Known user's followed sites and users.
No HTTPS support
withknown.com doesn’t support https for browsing, during signup, or on anyone’s subdomain, meaning that authentication credentials and cookies can easily be intercepted on public wifi networks, as well as private content.
Articles written about Known, especially in the press / mainstream media (most recent first)
Videos about Known (most recent first.