- From: Adam Lake <adam@mosaic.social>
- Date: Mon, 11 Feb 2019 21:36:15 -0500
- To: Timothy Holborn <timothy.holborn@gmail.com>, Melvin Carvalho <melvincarvalho@gmail.com>
- Cc: public-solid@w3.org
- Message-ID: <5a4e4178-721f-02ac-97e3-acc069a9f7d5@mosaic.social>
Hi Timothy On 2/10/2019 11:28 AM, Timothy Holborn wrote: > Great notes... > > May I suggest a horizontal timeline rather than a vertical one.and Interesting and compelling suggestion. I will play around with that idea int he mockups > > Beyond differentiation, > > A. I have noticed younger people in particular really enjoy scrolling > through the comments on a post. This could be achieved by way of > vertical scrolling > > B. The ability to create faceted results via preset & defined queries, > could enable horizontal scrolling to have multiple dimensions > > C. The ability to leverage ontological datasets might also provide the > means to enhance the informatics modalities of any "related posts", > particularly if the community are encouraged to support ontology > production; for instance, news genres, and social discovery and > classification of posts from news / web sources, etc. > > D. I suspect the ontological framework around the solid address book > will provide far more granular & flexible opportunities, that might > in-turn support user experiences that incorporate functionality > otherwise considered to be separate products; for instance, Not sure I am following everything here but easy filtration of news feeds along with custom and pluggable algorithms is part of the current design. > > Short messages / Twitter > Business / professional networking / LinkedIn > - personal > - communities > - dating / friend finding > - meetup like functionality, Inc. > - discoverability of local offers; i.e. happy hours or takeaway / > dining specials - in Australia, often pubs have dinner specials > - etc. > > Therein, my thoughts consider how a multimodal is framework might help > redefine social. > > Beyond that, I think it's worth noting that most social sites have a > bunch of underlying data services supporting it. > > such as; > - media / video transcoding, > - geo representation & contextual discovery based on location, etc. > - instant messaging > - sharing of contacts, encouraging others to join, means to import old > data, etc. > > In a decentralized model, there are new opportunities. Some include > enabling the end user to pick an api provider, whilst this is > Generally a fee based service (i.e. various google or Amazon APIs), > and there's other opportunities. > > Often also, the large provider are encouraged to.do kyc/aml, for > various reasons. I am not sure whether this is achieved via the solid > provider, or the app. I note also, a bunch of potentially very good > democracy enhancing solutions come about if kyc/aml related checks are > done - elected parliamentary persons want to engage real people in > their electorates, for example... I am absolutely interested in civic engagement use cases and you are correct that identity is critical here. Verifiable credentials seem to be a big part of the solution here. It's a matter of getting authoritative entities to start issuing digital voter registrations. > > So, > > Great work, But my eval bitumen to consider that perhaps a faster > path to market was to build the plugins for WordPress to make it > interoperable with solid, noting there are already some social > networking frameworks built for WordPress, alongside many other > solutions... > > I have a non-federated / ref enhanced example > https://au.webcivics.net/community/ > > Having written some of my thoughts > > https://au.webcivics.net/2018/10/24/wp-webcivics/ > > Whilst I believe the capacity to build a very interesting update for > social engagement has a bright future, with solid, > > Throughs were, building the relevant php framework parts for > WordPress, should be quick and relatively easy, in addition to, if > done well, providing means to extend php framework works for.use with > other php frameworks, as are used by the vast majority of > organisations across the web, looking for an easy way to get involved > and start testing out how their market engagement, internal > collaborating and others web related functions, across education, > government, commercial sectors, smes, > > Can start to deliver meaningful improvements as may in turn be used to > free up development investment, and support new use case related > considerations by w3 members, as a means to support the continual > standards development works overtime. > > I note finally, > > The W3 cg website has a WordPress based front end... how could we > make that better? > > Timo > > On Mon., 11 Feb. 2019, 12:17 am Melvin Carvalho > <melvincarvalho@gmail.com <mailto:melvincarvalho@gmail.com> wrote: > > > > On Sun, 10 Feb 2019 at 01:25, Adam Lake <adam@mosaic.social> wrote: > > ** > > *Hi All, * > > * > > It is great to see so many passionate and capable people in > this group. I am sorry to have missed the kick-off call but > hope to make the next one. > > > My interest in Solid is the power of its principles to enable > a more free, open, and cooperative Web and world. To me it > represents the promise of coming closer to the original vision > for the Web, a platform that would increase human capacity, > our political and economy health, and our collective > intelligence. My assessment is that individual sovereignty on > the Web, an extension of civil rights in the digital age, is a > fundamental requirement to achieving these broader social > ends. Solid’s data ownership and data portability architecture > are critical pieces of the puzzle. I am probably preaching to > the choir! > > > My role is to help “bring people together to build the next > generation Web”. You can learn more here > https://mosaic.social/. The objective of Mosaic is to connect > teams, technologies, and financing to bring user-centrc (“Self > Sovereign”) P2P apps to market. My hope is to facilitate the > connection between disparate parties that may not know about > each, but who together can provide all of the necessary > ingredients required to brings Solid apps to market, have a > sustainable business model, and designed to maximize social > well being. The technology is critical, but so are funding, > business models, marketing, and psychologists who specialize > in human-centered design. > > > The Mosaic website was launched to communicate a basic > technology framework*(very much still open for debate)* and > some app concepts to spark the imagination and get dialogue > going about what app ideas have the most support (e.g, > existing technology, funding, and public demand). I am heavily > leaning toward starting with a decentralized Facebook > application because it exemplifies the struggle for the future > of the Web and because an alternative, or anti, facebook is a > simple concept for people to understand. However, choosing > this app presents some challenges as there are deep problems > around distributed search, fake news, and identity to solve. > These issues may prove to be intractable problems but I think > it’s worth systematically exploring whether a good > decentralized and Solid-based Facebook could be designed. > Opinions on these topics are most welcome! > > > I would gladly engage with others in this group around these > high level design considerations as well as sustainable and > equitable business models for bringing Solid apps to market. > > * > > > Looks very interesting. > > I've had done some work on a timeline app but I never got a chance > to complete it, as focus shifted to the server. The auth doesnt > work with the node solid server in OIDC mode yet, tho. > > demo : > http://solid-social.github.io/timeline/?date=recent&profile=https:%2F%2Fmelvincarvalho.com%2F%23me > code : https://github.com/solid-social/timeline > screenshots : > https://melvincarvalho.gitbooks.io/solid-social/content/appendixa.html > > I believe darcy is also looking at this route : > > https://darcy.is/ > > So, it helps to understand what facebook did well. They created > their system based on the idea of giving everything an HTTP URI > and growing a graph around that. > > Porting this idea to solid I think is an excellent idea, and would > allow a cross origin social network with strong privacy and > everyone controls their own data. > > Seems like a compelling use case, so the question arises as to why > no one in open source has done this yet. > > The answer is that resources are scarce. And those that have > tried inevitably have taken on too much. Such the very common > idea of making it P2P or creating a new DNS. Such premature > optimizations have never worked, and if we have learnt from > history are not the best strategy. It becomes tougher still > because advocates of protocol X are widespread trying to promote > their system, whereas solid is just the web with more cross origin > features unlocked. > > Doing one thing well which is porting social network functionality > via a graph of URIs can be easily realized if we have someone to > code it. A small team, or even a single person, could realize this > in a few months. The prototyps of facebook was apparently coded > up in about 2 weeks. > > Solid is an ideal technology to achieve this. But the danger is > going off piste and tagging on the latest social protocol du jour > and ending up with an architecture inferior to facebook. There > was a massive opportunity missed by the social web working group > imho when I suggested this route, that the social web about > people, friends and connections. Whilst I thought this was self > evident, it idea was rejected, in favour of building a > microblogging system. Well that worked, but we sacrificed social > networks on the altar of the micro blog. > > Id suggest doing one task well ie porting social networks to > solid, then think about adding more protocols. > > What is needed? You need a timeline, you need profile management, > a friendship graph. You need friend requests. Messages, replies > and likes. It can either be done as one system or in modular > parts where different groups work on different aspects and then a > team ties them together in a single app. > > Id suggest working out what is in scope and what is not, and > trying to make something as minimal as possible. Then trying to > achieve a rapid prototype. Perhaps work together with darcy if > they are going to build a solid solution > > * > > Kind Regards, > > Adam Lake > > * >
Received on Tuesday, 12 February 2019 02:36:53 UTC