After the experimental endeavour to create a next-generation Piggydb which became Oinker.me, we decided to re-create it from scratch as open source.
The project is called “Cotoami”. It is still in an early stage of development and we are looking for some comments and feedback from people who are interested in Piggydb-like applications.
- Cotoami – https://cotoa.me
- Twitter – https://twitter.com/cotoami
- Cotoami GitHub repositories – https://github.com/cotoami
- Cotoami Roadmap – https://github.com/cotoami/cotoami/issues/2
It’s long time no see… actually, it’s almost two years since the last version (V6.18) was released.
After the long pause, Piggydb’s new version is finally here.
It doesn’t contain big changes except that the page header has been redesigned. Now it looks cooler than before (hopefully), and the title displayed in the header (“Piggydb Documents” in the screenshot) is the “Database Title” which you can change in the System Info page.
It also fixes a bug that it won’t work offline because of the reference to the hosted Mathjax library.
- Mathjax load from cdn makes Piggydb unusable without internet connetction · Issue #9 · marubinotto/Piggydb
Lastly, Piggydb V7.0 requires Java 8. If you use one of the previous versions of Java, you need to upgrade it.
From time to time I received requests for MindMap or ConceptMap like graph visualization (nodes and edges style) in Piggydb or Oinker. But I thought there were things to consider in order to implement it since the models in both applications were document-oriented as I explained in an Oinker Blog entry.
- Graph Style (Nodes and Edges) or Document Oriented Style? | Oinker Blog
Recently I came up with an idea and implemented it in Oinker as below:
The problem of displaying document-oriented data in a graph view is that a document tends to contain many large nodes which are not suitable for bird’s eye overview. So we should deal with these nodes somehow to avoid the verbosity of being precise. The idea I came up with is a way to select nodes for a graph. I call these selected nodes “topic nodes“.
Currently a topic node is:
- a node whose content has only one word or sentence.
- a node whose content length is shorter than or equal to 30.
- a node whose content is not Markdown
- a node whose content is not a URL
- a node whose content is not a file
You can check out an example of how topic nodes work in Oinker’s graph view at:
This feature is still experimental and waiting for your feedback.
Oinker – https://oinker.me/
It’s been a while. These days I’m working on a web service “Oinker” off and on, squeezing time from busy days.
Recently, I’ve started pulling well-proven features from Piggydb and adding them to Oinker. One of them is a content publishing capability which is implemented as “Anonymous Access” in Piggydb (sample site).
Oinker’s publishing feature is more sophisticated than Piggydb. You can publish your content on a room basis. A room is like a chatroom in Oinker and it has a chat timeline and a board on which you create content with your roommates.
You can make a board open to public so that anonymous visitors can view the content, and additionally allow logged-in users who are non-members of the room to view the timeline and post messages to it. So you can not only publish your content, but also collect feedback from audience.
What kind of content can you create in Oinker? Just check out the sample content: Unknown Tokyo
You can sign up for free at: https://oinker.me
I’m looking forward to your feedback 😉
Happy new year 2015 from Japan! I hope you have a wonderful year, especially in terms of knowledge work 🙂
As this year begins, the newborn service Oinker starts accepting invitation requests.
As you saw in the movie, Oinker is extremely simple. You just chat alone or with your friends and connect the comments (oinks) by dragging and dropping.
That’s all, but its potential is enormous.
I’ve been using it in real business projects with my colleagues for about a year, mainly for ideation, task and knowledge management, and it’s been just amazing. I’ll write the details of these use cases at the Oinker blog.
The best way to feel the potential is to experience it yourself, so if you are interested in trying it out, please email to email@example.com