@bob For the being based on the am looking at Odata as the rest API core as this is an outgrouth of and and comes from a long process of open development What do you think?

@Hamishcampbell @bob It looks like this is the relevant specification document:

I'm not aware of anything currently using the OData format and in the context of federated systems I think it would be better to stick with the ActivityStreams vocabulary, which is what ActivityPub is based on.

@bob @Hamishcampbell this is based on atompub which is the same thing activertypub is built on. Am format agnostic as long as its #4opens am not soure that activertypub implements the update data option, its not in any of the apps. For the backend am looking to build a huge distributed "lossy" database - the data soup were the apps are just laddles tto this bubbleing coldren. No resion you can use activertypub to dip in for norshment :) @bob ie. its anything in and anything out - mediated by trust. Then its up to "commernerty" what they do with this and up to the individuals what commerty they choices or if a bit geeky can be an individual. its just soup (data soup) of coure my project is to build a media/news network out of this other people can build other things @bob the data soup is feed by folsonmeny flows of taged data objects mediated by trust. the consumemption is based on the same. all with a nice UI lossy, redundencey, trust are fetures. the seeing these as problems needs to be overcome. What do you think?

@Hamishcampbell @hamishcampbell @bob Also try to create infrastructure which operates in a clear and simple way. If you create a murky soup of data with unclear attribution then this provides habitable cover for the real bad actors. We've seen that happen in previous attempts to disrupt the open web, with ISIS and then the alt-right.

@bob @Hamishcampbell the idea (#4opens) is that the flow metadata and tag history is added to the data object (that is redundently stored) all a bit lossy which of course is a security risk - the are likely checksum/hash solutions that can fix these but important to keep it human #KISS at bootup.

@hamishcampbell @bob @Hamishcampbell It sounds like what you want is a distributed database with redundant storage. Tahoe-LAFS is similar to that in that some servers can go down but the data can still be reconstructed, but those things are usually immutable data only.

If you're using text files as a database then the old skool method would just be to rsync a bunch of servers. Syncthing would be a more modern way of achieving the same result.

@Hamishcampbell @bob

ie. its anacky in code - much like the #openweb was. its a social tecnlogicl project. not a tecnilogical social project. ie. the social comes first to clearly moive away from the #'geekproblem. but how to get the #geekproblem to implement something that is desined to move power away from them... thats the problem.

@hamishcampbell @Hamishcampbell @bob The open web is both social and technical. Over its history we've learned a few lessons the hard way. If you create ungovernable social spaces then they will be colonized by the worst people on the internet.

Cryptography doesn't create trust (as the Bitcoiners often like to imply) but it does provide a framework within which it's possible for trust relations to happen.

@bob "open" to create trust and value. if people brake the trust the tools are all about moveing them into a commerty were there views can be trusted. If they have no vlaue then they will be organicly dropped from the network - spam is an example of this. The network is inherently lossy and leeky to cross the filterbubbles and keep the data from ossifying as our current silos do. Open has power that closed duse not. Yes open has dangurs we know well that closed duse not in anyway solve.

@Hamishcampbell @bob

the exciting bit are the "flows of trust" bulding commertys. the tech and code are just tools.

* nothing new

* all #4opens

* good UI

@Hamishcampbell @bob this is of coures what mastodon trys to build on the work of twitter. BUT mastodon is based on individuals - am looking to build the same based on "flows" which can be anything. This should speak activertypub, RSS, activertystreams and odata etc. its just data in and out - what matter is who conects the flows - the social side of tech, and what these flows nurish as an outcome #indymedia

@hamishcampbell @Hamishcampbell @bob That sounds similar to the Hubzilla/Zap "channels". A channel can be an individual, but it can also be a group or a fanpage.

@bob yep Hubzilla can be a usefull part of a #OMN its just data in and data out medated by trust flows.

@bob what we have to build is the "trust network" and datasoup infrustructer. all the current apps becouse laddles and soup bowls.

@witchescauldron @bob

What we are building is like the WWW its a user built sematic web runing over the current internets with existing distributed data and tools to use it. the key word is KISS which is a good start to a flertation ;)

Sign in to participate in the conversation

To support this server and the OMN project