We can say once again that our last event, RealTime WebCampLjubljana, was a great success. We didn’t run out of coffee, there was enough electricity and WiFi as well as a great mix of people and the quality of talks and discussions was astonishing.
There are a few things that we did differently this time that had effect on the ‘camp feeling:
Smaller group – instead of going with 150+ we went for 50+ crowd. More intimate and it allowed for more open discussions.
Two tracks only – moved from 3 tracks format to 2 tracks as there was less people and we also had to optimize for the available rooms. We still managed to create a nice balance of tech vs. non-tech oriented talks.
Slovenian language – despite protests from our friends in Croatia, we decided to go with Slovenian as a primary language this time. My current feeling is that this made it easier for everyone involved and we should consider sticking to Slovenian for smaller camps that are not intended for international audience.
‘Hackish venue’ – instead of going for university or conference venue, we crashed in Hekovnik this time, a new hackerspace in Ljubljana. This had a totally different feeling of more ‘ad-hoc’ and less sterile environment. It seemed like people enjoyed this more.
There is still a question – how to encourage people to prepare more sessions and how to time the event. Going for early Saturday morning as a start (8am-ish) seems to work great for now. Regarding more sessions, I’m not sure if we can expect more than 30% of attendees to run their own session, would be interested in recommendations on any literature on the topic of facilitating sessions.
Did I miss anything important that we should take into consideration for our next ‘camps?
It’s been two months after last WebCamp and it’s time for another party. Following the idea of BarCamps with story line, we’ve decided to organize RealTime Social WebCamp Ljubljana.
This time we’ve decided to focus on a single emerging technology space: Real-Time Social Web. If you’re not up-to date with the latest buzzwords, it’s about next generation RSS protocols like HubSubPubBub, RSSCloud, XMPP (that powers GTalk), Synaptic Web, Twitter API and a bunch of other technologies and ways of thinking about the Web and Mobile space.
Intended audience are developers and people who are close to them (e.g. interface designers, product managers, etc.) and will need to innovate in this space in the next 6 months.
We’re doing it a bit more limited this time, just 50 spaces. I’m interested in seeing how a smaller and more focused group changes the dynamics of such gathering.
The rules for the tickets are the same as the last time. Send description of your talk early and you get a ticket, or hope that you can click fast enough for the left-over tickets later. I believe that extra effort should be awarded.
The official language this time is Slovenian since we’ve figured out that locals that are not native speakers understand our geek talk enough that it shouldn’t be a problem and we can understand them as they lecture in their own language.
Disclaimer: this is a partly cleared transcript of discussion; I didn’t follow the authors of comments in order to be able to catch as much as I can. Correct me if I quoted someone incorrectly and please don’t be angry with me.
Present at the discussion:
Stephanie Booth, 8 years blogging, Freelance social media consultant, interested in blogging, and everything thatâ€™s online
Justin Tomboulian, Microsoft, lives in Kyoto, Japan – responsible for solutions delivery; part of the network that takes care of 80k users ecosystem; trying to solve big-company illness problems; internal private social network and return the learnings to the community
John Breslin, DERI, interested in porting of data, SIOC, data portability initiative
The topic is: â€œAdoption issuesâ€; what prevents people from using new technologies? The discussion turns to the question, why the big guys (FaceBook, etc.) are not adopting these solutions. Can we show that if we have portability, we will have more users.
40% of pictures on MySpace were referenced through PhotoBucket, so this was their biggest weakness when being acquired. So MySpace bought them, but the question is – was this a good thing for users? It means that MySpace killed the data portability of PhotoBucket. If you are looking at the photo that is sitting in photo-bucket, but is embedded into MySpace -> is this real portability or just â€œview-ability?â€
So what portability really is? Should we copy the objects, or just reference it? It embedding YouTube portability of the video?
Quick explanation of aggregation vs. federation. News reader is aggregation -> data is on the web site, and Iâ€™m using special glasses to take a look at the data; itâ€™s an aggregated view. Federation Is actually about â€œmovingâ€ data around. â€œAggregation does not mean portabilityâ€; Reflection from a startup point of view: APIâ€™s are part of the discussion about portability, and the question was – why would we let others user precious data that users gave us. â€œItâ€™s oursâ€. The point that Stephanie tried to get across: if you make your data available to other services, then this data is more valuable to users since then it will be available as parts of other sites.
The discussion turns into the fact weather FaceBook keeps a copy of your data and if you can get it removed. The right to delete the data is fundamental part of data portability. â€œWhoâ€™s data is this blog post? Just authors or of everyone that was thereâ€. It is also hard from technical perspective. Itâ€™s also noted that web pages are cached and it is hard to quickly remove it from Google cache. It can be months, or days. Is it your right to delete your comments on a forum and disrupt the community. There is also a question of deleting blogs and the comments with them. The content becomes â€œpart of communityâ€, and with the deleting of the blog you are also removing other peoples original contribution. Users bill of right is mentioned – http://opensocialweb.org/2007/09/05/bill-of-rights/.
What is the business model of â€œall these servicesâ€? â€œThe because effectâ€ – you do not make money with your blog, but because of it. The business models should turn more into that, instead of locking down the data to their islands.
What can you â€œbringâ€ with you? Do you â€œmoveâ€ -> delete original after copying; making a copy and having two copies; or are you existing in kind of a shared space that gets synced back and forth. Is business model – we are making money â€œwithâ€ the users content, not â€œbecauseâ€ of it.
If this content is great, then there must be money in that? Is that a good way of thinking about business models? The value of FaceBook is monetized eyeballs; they make money with branding ads since they actually charge according on time users spend on their site. They canâ€™t make money from AdWords, they have to brand. These big sites do not have interest to open up their data until the competition comes. Using other big players in industry is possible for them to leverage their interest to make the data a bit more open.
What users want – is freedom of data; and companies want more face time, so there is no real interest for them to open data. â€œIs this similar to FOSS vs. proprietary debatesâ€.
Data portability is a lot about business models. As long as business model issues are not solved, you can offer as much technical solutions as you want, you will not get adoption. â€œUsers can vote with their feetâ€. Amnesty App – enabling users to migrate in one hop to another service. Static data formats are a problem, because we canâ€™t know what will matter in a few years.
Ideal thing is that I have a store somewhere where I have all the information that I can allow others to read it. Whoâ€™s going to build it and the fact is that you can not design it correctly for the future. You could turn around it around and charge it to providers or the users, depending on the point of view on your data. What kind of business model is behind that?