Found one interesting org -- IndieWeb Fwd: what idno is
hupili.snsapi
The two projects mentioned in the original posts are less interesting, i.e. http://idno.co , http://elgg.org . I tried to have a quick study of them but did not get the main idea. It looks like the two are called Social Media Management System. The name sounds like a variant or improvement of previously understood Content Management System. There is no quick overview for the "social" aspects. The showcase demos all needs registration and does not support open login solutions.
In the post, I happen to see the IndieWeb org. It has done interesting things. For example,
http://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread
Laurent Eschenauer, who started the federated comment thread, is the founder of OneSocialWeb.
IndieWeb is really worth looking at. There are a lot of ad hoc open techs/ tools.
Pili
-------- Original Message --------
| Subject: | what idno is |
|---|---|
| Resent-Date: | Wed, 03 Jul 2013 08:55:07 +0000 |
| Resent-From: | public-f...@w3.org |
| Date: | Wed, 3 Jul 2013 10:54:36 +0200 |
| From: | Melvin Carvalho <melvinc...@gmail.com> |
| To: | public-rww <publi...@w3.org>, "public-f...@w3.org" <public-f...@w3.org> |
[[
This site runs on idno: an open source social publishing platform that I've been working on for the past few months in my own time.
You may know that I co-founded Elgg, the open source social networking engine, which is used by the likes of Oxfam, NASA, the World Bank and several national governments as a social intranet and learning platform. The original thinking around Elgg happened a decade ago. Given that, you shouldn't be surprised to learn that my original thought experiment was: What decisions would I make if I was building Elgg today, in 2013? What would I do the same way, and what would I do differently?
Some technical decisions
I knew that I could make a faster social networking platform, with a better templating engine, and a much smaller codebase - even while sticking to PHP as an underlying scripting language. Partially that's because PHP 5.3+ is a much better development platform than earlier versions. It's also because there are now some well-tested, intelligent back-end frameworks, like Symfony 2, and front-end frameworks, like Bootstrap.
One of the major decisions I made when we built Elgg 1.0 was that not only was it a hassle for plugin developers to write their own database schemas - it was undesirable to the point of being dangerous. We effectively faked a NoSQL schema in MySQL by creating a data model around entities (first-class objects like users and blog posts), metadata, annotations and relationships. People were taken aback, and it was row-intensive, but it worked, and it continues to work today.
Nonetheless, today we have NoSQL, so #idno is based around MongoDB. This means there are far fewer database transactions involved - and adding new data to an object is incredibly easy. Together with a plugin architecture based on lazy loading, and Symfony's excellent observer pattern support, as well as the framework code I've built, I'm able to write a new plugin in an hour or two. That's important for a system I'm building in my spare time!
Meanwhile, all of the things about #Elgg that were great - a plugin architecture, granular access permissions - are intact. And on top of that there's a faster framework, and a responsive front-end that works really well in a mobile browser. Great!
But that's not the end of the story.
The #indieweb community has existed for years as a force to advance the state of the independent web, and to promote ownership of our own spaces. IndieWebCamp is an annual event for creators to discuss their platforms, technologies and ideas.
One of the big concepts to come out of #indieweb has been #POSSE: Publish (on your) Own Site, Share Everywhere. The idea is that your friends or followers shouldn't have to join your site to engage with you; you should be able to post on your own site and be read on Twitter, Facebook, Foursquare, or wherever they happen to be. idno has built-in plugins for status updates, blog posts, images, checkins and events. Correspondingly, it also has plugins to #POSSE this content to Twitter, Facebook, Foursquare and Flickr - and writing more would be trivial.
That's just as well, because I've committed to only post on my own site and copy to third parties (where that's possible).
Reinventing the social web
This year, though, something else happened. Using Microformats 2 (a way to very simply embed meaningful markup into any web page) together with Webmention (a way for any web page to lightly ping the pages it references), the community participants created the first indieweb decentralized comments thread.
Using nothing more than the markup on their own web pages and a very simple protocol, the participants created the basics of a decentralized social community, where each comment is hosted on its owner's own site, but nonetheless forms a coherent, easily-readable narrative.
This is a very big deal.
It's a completely different model to traditional social networking, where content typically doesn't bleed outside the walls of a specific social site. It's also different to previous decentralized social networking efforts, which have been in many ways more sophisticated, but much harder to join in with. Because a simple IndieWeb-compatible social tool can be built in an afternoon, just as a simple RSS-compatible tool can be built in an afternoon, these concepts have a much greater chance of succeeding.
Needless to say, idno is now a first-class participant in the decentralized IndieWeb social community. I've implemented IndieWeb comments, and moved immediately to also implement decentralized events that anyone can RSVP to, as well as decentralized likes. It also integrates with Firefox's brand new Social API.
You can browse the web and reply to any page, on a site that you truly own.
As more sites and platforms implement the IndieWeb social standards, those interactions will become correspondingly more social. For now, though, you can go ahead and interact with the web already.
Beyond that, idno will continue to develop over time as a community platform in itself. I'm using it here on my own site as a single-person publishing platform, but it doesn't have to be that at all, and all those Elgg-style features will continue surface as time goes on. But there's a big, wide web out there, and it's important to embrace that as widely as possible.
idno's homepage is here. Meanwhile, I continue to do work I'm proud of in my actual job, working for latakoo to facilitate media storage and transfer for video professionals and the broadcast news industry. We're talking about using decentralized social networking there too - but more on that another time.
]]
Lin Huiwen
每个人将这个部署在自己系统上，然后提供给别人一个地址，插件会自动帮助获取。
是这样的吧。
2013/7/3, hupili.snsapi <hupili...@gmail.com>:
> my own time.
>
> World Bank and several national governments as a social intranet and
> learning platform. The original thinking around Elgg happened a decade
> ago. Given that, you shouldn't be surprised to learn that my original
>
> *Some technical decisions*
> I knew that I could make a faster social networking platform, with a
> better templating engine, and a much smaller codebase - even while
> sticking to PHP as an underlying scripting language. Partially that's
> because PHP 5.3+ is a much better development platform than earlier
> versions. It's also because there are now some well-tested, intelligent
> frameworks, like Bootstrap <http://twitter.github.io/bootstrap/>.
> One of the major decisions I made when we built Elgg 1.0 was that not
> only was it a hassle for plugin developers to write their own database
> schemas - it was undesirable to the point of being dangerous. We
> effectively faked a NoSQL schema in MySQL by creating a data model
> around entities (first-class objects like users and blog posts),
> metadata, annotations and relationships. People were taken aback, and it
> was row-intensive, but it worked, and it continues to work today.
>
> Nonetheless, today we have NoSQL, so #idno
> <http://www.mongodb.org/>. This means there are far fewer database
> easy. Together with a plugin architecture based on lazy loading, and
> Symfony's excellent observer pattern support, as well as the framework
> code I've built, I'm able to write a new plugin in an hour or two.
> That's important for a system I'm building in my spare time!
>
> that there's a faster framework, and a responsive front-end that works
> really well in a mobile browser. Great!
>
>
> The #indieweb <http://werd.io/search/?q=%23indieweb> community has
> web, and to promote ownership of our own spaces. IndieWebCamp
>
> One of the big concepts to come out of #indieweb
> <http://werd.io/search/?q=%23POSSE>: Publish (on your) Own Site, Share
> join your site to engage with you; you should be able to post on your
> own site and be read on Twitter, Facebook, Foursquare, or wherever they
> happen to be. idno has built-in plugins for status updates, blog posts,
> images, checkins and events. Correspondingly, it also has plugins to
>
>
> This year, though, something else happened. Using Microformats 2
> indieweb decentralized comments thread
> Using nothing more than the markup on their own web pages and a very
> simple protocol, the participants created the basics of a decentralized
> social community, where each comment is hosted on its owner's own site,
> but nonetheless forms a coherent, easily-readable narrative.
>
> This is a very big deal.
>
> It's a completely different model to traditional social networking,
> where content typically doesn't bleed outside the walls of a specific
> social site. It's also different to previous decentralized social
> networking efforts, which have been in many ways more sophisticated, but
> much harder to join in with. Because a simple IndieWeb-compatible social
> tool can be built in an afternoon, just as a simple RSS-compatible tool
> can be built in an afternoon, these concepts have a much greater chance
> of succeeding.
>
> decentralized IndieWeb social community. I've implemented IndieWeb
> comments, and moved immediately to also implement decentralized events
> that anyone can RSVP to, as well as decentralized likes. It also
> integrates with Firefox's brand new Social API
>
> *You can browse the web and reply to any page, on a site that you truly
> own.*
> As more sites and platforms implement the IndieWeb social standards,
> those interactions will become correspondingly more social. For now,
> though, you can go ahead and interact with the web already.
>
> Beyond that, idno will continue to develop over time as a community
> platform in itself. I'm using it here on my own site as a single-person
> publishing platform, but it doesn't have to be that at all, and all
> those Elgg-style features will continue surface as time goes on. But
> there's a big, wide web out there, and it's important to embrace that as
> widely as possible.
>
> decentralized social networking there too - but more on that another time.
>
> ]]
>
>
> You received this message because you are subscribed to the Google Groups
> "snsapi" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to snsapi+un...@googlegroups.com.
> To post to this group, send email to sns...@googlegroups.com.
> Visit this group at http://groups.google.com/group/snsapi.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
Pili Hu
Pili Hu
xuanqi...@gmail.com
Pili Hu
代码家
好便宜啊... 有没有打算部署个blog在新的空间？