Lens - milestone update (month 1)

[djfnd]

Hi all, I have put together the first draft of our submission to Lens re: the work we have been up to this month:
https://hackmd.io/@T6wnxp9DRcWdWiHtcSxvXA/rywXeXAHh

Please take a look and provide any feedback you have. I'm sure there will be elements that I have either missed or misinterpreted. And if there are any links that you think should be included and aren't then that's useful to know too.

I have also added a couple of ideas for milestones for the next month, but also let me know what you think.

CC: @il3ven @neatonk

[il3ven]

We don't have permission to see the hackmd page. 😅

[djfnd]

Try now!

[il3ven]

Working!

[neatonk]

Looks good to me.

I'm going to be pretty busy this month, so it would work out well to just discuss and refine the neuIP this month. Then, if we're ready to implement something in the following month, that would be good timing.

I can also look into using Arweave for distribution as a way to help with the goal of onboarding lens apps. Not sure how much time I'll have to work on it though.

[djfnd]

Looking to get this send over by COP today, so any further feedback today would be appreciated. Once we're happy with it I will additionally pull together a public-facing "update" blog.

In terms of month 2 funding allocation, my proposal is to do this split:

• Get the Lens crawl up and running: @il3ven - $3k
  • Continue the ongoing work and get things operational in production
• Onboard front ends in the Lens community to neume: @oakgroupworldwide - $1k
  • Lens focussed content creation & liaising with suitable Lens front ends
• Refine and further develop the specification of neuIP-5: @neatonk - $1k
  • Discussion, research, and further development of neuIP-5

[neatonk]

Looks good to me.

For the neuIP, a specific outcome that could be mentioned would be an updated schema and reference implementation which can be used to generate subset schema IDs and derive subsets via constraints. This would also aid discussion by making the proposal more concrete.

One thing I'd like to include in the discussion are ways to link datums across related schemas, like tracks and NFTs. Alternatively, related datums can be embedded to simplify access. Ideally we could support both use cases and let node operators choose the trade-offs that make sense for their use case.

Feel free to include any or none of this in your updates.

[djfnd]

Fantastic, I will add this yeah. This is great context.

[djfnd]

Proposed blog PR here: neume-network/website#20

[djfnd]

I have now sent this