A fun graph/network diagram would be people <> languages/frameworks

Would be such a great at-a-glance way to understand where in the network one could go to lightly tap relevant expertise.

Awesome. This could be of interest to @rabble @rabble @Rabble @Rumblemunk

@Connor that's a #somebody-should ! Want to lead it?

@mixmix could be a #somebody-should , but didn't initially think of it that way. More a spur of the moment thought that broadcasted.

But since you mention it I might play with some kind of poll that could get at those relationships

huh ... @piet this proposes a really interested alternative use case : desktop / laptops as thin clients for phones

The thing I hate about phones is they're hard to type on, and there's limited space. Imagine if I could go to a library, put my phone on the wifi, then in a browser go to ipaddress:port, enter a password FDs56x (provided by my phone) and then boom be browsing my phone

Now that is a nice example of a query... guess I can eat my lunch at the desk later today.

We're pretty heads down working on #verse at the moment. I think it's awesome there are other iOS projects. Most of the ssb part of what we're doing is being released here: https://github.com/cryptoscope/ssb

Right now the way verse works is the gosbot provides a http end point and the swift front end calls it, pulls out the data, and puts in a sqlite db... Our plan is to try having both gosbot writing to and the verse swift code reading from the same sqlite.

I think the ssb-patchql stuff is super interesting, although i don't personally like doing react and graphql, but i know it's a really good model for pushing the queries out to the client. We should think about the privacy / data protection / security implications of multiple clients being able to do queries on a user's db. For now it's not a big deal, but what happens when zynga does scuttlebutt words with friends.

On another note we're ready for alpha testing #verse. I gave out some invites at #data-terra-nemo and would be happy to bring on some folks here if they have iOS devices and will help us test. We locked this alpha version to a different cap / network because we didn't want to break things with our tests.

with the code provided above I was able to get "pagination" to work too. It took some time until the dots connected in my head (the value of the endCursor can be used post(before: "HERE")) but then getting pagination to work was quite easy.

Crude sketch of my query (there's probably a cleaner way to insert things)

function fetchLatestMessages(cursor) {
  const before = cursor ? `, before: "${cursor}"` : '';
  return apolloClient
    .query({
      query: gql`
        {
          posts(last: 100, orderBy: ASSERTED${before}) {
            pageInfo {
              endCursor
              hasNextPage
            },
            edges {
              node {
                id,
                author {
                  name,
                  id
                },
                likesCount,
                text,
                assertedTimestamp,
                rootKey
              }
            }
          }
        }
      `,
    })

thanks for the samples and the AWESOME sidebar documentation on localhost:8080!

Of course, what's your email?