# IPFS stewards \<\> advocates sync **URL:** \ **Category:** Ecosystem and Usage\ **Created:** [April 4, 2022, 2:41pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893 "2022-04-04T14:41:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![mosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/mosh/32/5637_2.png) [@mosh](https://discuss.ipfs.tech/u/mosh)\ **Post date:** [April 4, 2022, 2:41pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/1 "2022-04-04T14:41:55Z")
We’re piloting a biweekly sync between IPFS stewards and advocates. Let’s use this thread for meeting recaps and related conversations. ---
**Author:** ![mosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/mosh/32/5637_2.png) [@mosh](https://discuss.ipfs.tech/u/mosh)\ **Post date:** [April 4, 2022, 2:49pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/2 "2022-04-04T14:49:33Z")
## April 1 Attendees: `@adin @lidel @achingbrain @BigLep @mosh @dietrich @Jorropo` ### People need more conceptual toolboxes - Eg I want to create an efficient index - Eg I want to traverse these blocks, how do I do that ### We need a place to drop semi-official knowledge Examples like Adin’s IPNS writeup and other docs that aren’t fully baked enough to go into Docs, but having it will be 100x better than nothing. After exploring many options (blog, discord, hackmd, notion), we decided to try using the wiki feature on this forum (it allows posts to be editable by many people). There are also stub pages in Docs like [Best practices for IPFS builders | IPFS Docs](https://docs.ipfs.io/how-to/best-practices-for-ipfs-builders/) ### “Getting Started” content could be better tuned to learning & introduction - People think of js-ipfs as a monolith, but it’s more modular by far and you most likely want to use them independently. We have some people who want to build on our stack who aren’t interested in decentralized transfer of data, eg someone is going to host servers with all the data using IPFS content addressing. - In browser land, users getting started are probably more interested in a daemon already running somewhere and just using some JS IPLD libraries. - Jorropo: Telling people to use go-ipfs as a library is a really big beast with complicated plumbing. You only need a few features provided in all the packages: DHT, bitswap, blockstore. @hector has an IPFS lite package, use that content instead as intro. Imports only the things you need and learn IPFS from the ground up in only 300-500 lines of code, plus better config options. [ipfslite package - github.com/hsanjuan/ipfs-lite - Go Packages](https://pkg.go.dev/github.com/hsanjuan/ipfs-lite). - Mosh: I"m hearing people looking for the IPFS way to do standard software things, like databases. Do we need better middleware? - Lidel: This will get way better when we support IPLD on gateways, namely [DAG-JSON](https://ipld.io/docs/codecs/known/dag-json/). When we remove the need for middleware, devs can just talk javascript and store JSON somewhere. - For a lot of people, IPFS = gateways, = UnixFS, != IPLD… smush everything into a directory, or just let the gateways support these things. ### There’s an early and important fork in the road when choosing to use IPFS: files vs. data. We call the whole thing IPFS but if you want dags all the way down, you’re going to need IPLD. This is an important concept for new users to understand but it’s missing an explanation. ## Links mentioned: - [Monthly Developers Report - 2022 March - Google Slides](https://docs.google.com/presentation/d/1-RpfekmmxQkMgs9k0z6JHYo6oObV4Ejp3FtOkBxVkvs/edit#slide=id.g12087249b7e_0_0) - Fabric.ai needs and conversation: [IPFS Data Indexing, Searching and Linking - HackMD](https://hackmd.io/aLJCT3wTTTauZP4mp8oYqg) ## Next time: - April 15 - As a group, try to create _the_ primer on IPFS for files vs. IPFS/IPLD for data structures. ---
**Author:** ![mosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/mosh/32/5637_2.png) [@mosh](https://discuss.ipfs.tech/u/mosh)\ **Post date:** [May 5, 2022, 2:00am UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/4 "2022-05-05T02:00:17Z")
## April 29 Attendees: @lidel @adin @mosh ### Proposed agenda: - Input on 2 grant proposals for [IPNS pinning service](https://github.com/mrodriguez3313/devgrants/blob/master/open-grants/%5BDraft%20OPEN%20GRANT%5D%20Fierro%20IPNS%20Pinning%20Service.md) and [emergent reputation](https://github.com/ckartik/devgrants/blob/ckartik/emergent-reputation/open-grants/open-proposal-emergent-reputation.md) - Learn about IPLD / DAG-JSON support on gateways - What IPFS means ### Notes #### IPLD/DAG-JSON support on gateways In go-ipfs 0.13 we introduced the concept of asking for a specific response from gateway. This will be used in the next release to support asking for dag-json and dag-cbor, and therefore any IPLD codec (represented as json/cbor). It’s useful if people are using IPFS as a backend service for internal usage. In the future you might want a concept of a verifiable-only / trustless gateway. #### What is and isn’t IPFS? The definition of IPFS is blurry. Here are some things that various people think IPFS is: - the [ipfs.io](http://ipfs.io) gateway - go-ipfs - anything that supports bitswap and the dht - anything that supports libp2p — but do you have to support ipld? what if you use http to transport the files? - do you have to implement all the codecs? - what if i just implement the bittorrent codec? Where do you draw the line that makes something IPFS or not? How do we choose who gets to make choices? What’s the line between being permissive and gatekeeping? - If we are going to insist that IPFS is everything in the universe that’s content addressing, we might want to define a subsystem that has requirements for an X-compatible implementation. - For every AND on the client, you have an OR on the server. for every OR on the client, you have an AND on the server. - Example: You have a protocol named pandora. If every pandora server must implement bitswap AND graphsync, then every pandora client may implement bitswap OR graphsync to ensure any client can talk to any server. - Content routing systems and other things around the edges get more complicated. e.g. if i say you may use DHT on the client OR indexers. Then you have to support both… or have a bridging system. - Need to decide if the indexers are a real system or not (multiple entities that you can treat the same way). Most companies would want to only index their own stuff, so if you assume all indexers are indexing everything, you’ll end up not being able to find stuff. This topic came up because go-ipfs can’t solve every problem. Neither can js-ipfs. Or any monolithic design. We need to redefine the IPFS project & protocol to explicitly make space for new implementations to emerge. Example: Brave mobile can’t run a full node, battery would die. So they’re taking a new approach, list of public gateways, fetching data and verify locally. Basically a lite ipfs client without libp2p. They may start libp2p amongst a local network. You could say there are at least 5 IPFS implementations already: - go-ipfs - js-ipfs - [estuary](https://estuary.tech) - [ipfs elastic provider](https://github.com/web3-storage/ipfs-elastic-provider), which is ipfs optimized for cloud infrastructure - [agregore mobile](https://agregore.mauve.moe/blog/2022/04/ipfs-with-chromium) ---
**Author:** ![mosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/mosh/32/5637_2.png) [@mosh](https://discuss.ipfs.tech/u/mosh)\ **Post date:** [May 13, 2022, 1:19pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/5 "2022-05-13T13:19:50Z")
## May 13 ### Proposed agenda: - Welcome @danieln 🙂 - IPFS camp - Proposed “protocol & implementations” track, is that the right theme, what are important discussions, who should chair this track? - What else? ---
**Author:** ![mosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/mosh/32/5637_2.png) [@mosh](https://discuss.ipfs.tech/u/mosh)\ **Post date:** [June 10, 2022, 2:30pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/6 "2022-06-10T14:30:19Z")
## June 10 Attendees: @mosh @danieln @lidel @discordian @BigLep @adin @Jorropo ### Agenda: - New blog post: [Gateways Part 1](https://blog.ipfs.io/2022-06-09-practical-explainer-ipfs-gateways-1/) is live. Part 2 coming soon. - IPFS operators manuals - New Docker example from @tommyhall: [go-ipfs-docker-examples/gateway-copilot-backend-service at main · ipfs-shipyard/go-ipfs-docker-examples · GitHub](https://github.com/ipfs-shipyard/go-ipfs-docker-examples/tree/main/gateway-copilot-backend-service). Essentially one-click deployment of a gateway as a “backend service” (autoscaling at Fargate Spot pricing, each node has a port open so is a full participant in libp2p, 200G ssd for the datastore, 4cores and up to 30G RAM, no LB though - dns based discovery for client-side load balancing). - Customizing Docker image [docs](https://docs.ipfs.io/how-to/run-ipfs-inside-docker/#customizing-your-node) - [PR with initial IPFS Gateway Specs](https://github.com/ipfs/specs/pull/283) – in review, looking for feedback from stakeholders - Stewards will be introducing light RFC process for ipfs/specs, initial notes [here](https://github.com/ipfs/specs/issues/286) – good ideas / prior art of pleasant processes welcome ---
**Author:** ![BigLep](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/biglep/32/5869_2.png) [@BigLep](https://discuss.ipfs.tech/u/BigLep)\ **Post date:** [June 10, 2022, 3:03pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/7 "2022-06-10T15:03:30Z")
## 2022-06-10 Actions 1. ✅ Archive the #ipfs-gateway-operators channel in IPFS Discord. 2. ✅ Add a “Operators” to [discuss.ipfs.io](http://discuss.ipfs.io): [Working Groups & Communities - IPFS Forums](https://discuss.ipfs.tech/c/domain-specific-and-location-specific-communities/10) that we can point people to: [https://discuss.ipfs.tech/c/ecosystem/gateway-operators/31](https://discuss.ipfs.tech/c/ecosystem/gateway-operators/31) ---
**Author:** ![Galactus](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/galactus/32/6540_2.png) [@Galactus](https://discuss.ipfs.tech/u/Galactus)\ **Post date:** [June 15, 2022, 2:09pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/8 "2022-06-15T14:09:17Z")
> [@mosh](#): > > The definition of IPFS is blurry. Here are some things that various people think IPFS is: The basic reason, what I think for this is the name/word ‘IPFS’ which is being used by the further mentioned tools with just minor/no change. ---
**Author:** ![lidel](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/lidel/32/9853_2.png) [@lidel](https://discuss.ipfs.tech/u/lidel)\ **Post date:** [June 24, 2022, 4:21pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/9 "2022-06-24T16:21:06Z")
### June 24th - @danieln’s [auspinner](https://github.com/2color/auspinner#readme) – a stateless CLI tool to easily pin CAR files to IPFS pinning services. It’s essentially a client for the [IPFS Pinning Service API](https://ipfs.github.io/pinning-services-api-spec/) that speaks HTTP and [Bitswap](https://docs.ipfs.io/concepts/bitswap/). - `go-ipfs`→`kubo` rename [in progress](https://github.com/ipfs/go-ipfs/issues/8959#issuecomment-1156963447) - reframe (pluggable routing) pieces are landing in kubo, we will need “DIY content routing” tutorials and examples in near future ---
**Author:** ![mosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/mosh/32/5637_2.png) [@mosh](https://discuss.ipfs.tech/u/mosh)\ **Post date:** [July 22, 2022, 2:33pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/10 "2022-07-22T14:33:56Z")
### July 22 - IPFS Thing followups - Overall wrapup blog post - Optional track leader wrapup blog post - [ipfs.io](http://ipfs.io) website reorienting - How to resource? - Emojibase! - [kubo/docs/changelogs/v0.14.md at master · ipfs/kubo · GitHub](https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.14.md#-emoji-support-in-multibase) - [IPIPs](https://github.com/ipfs/specs/pulls?q=is%3Apr+is%3Aopen+IPIP) (IPFS Spec/Improvement proposals) looking for more 👀 - [IPIP: format for denylists for IPFS Nodes and Gateways](https://github.com/ipfs/specs/pull/299) proposed by Cloudflare - [docs.ipfs.io](http://docs.ipfs.io): initial changes landed to reflect Kubo rename and push for more implementations - [Reference | IPFS Docs](https://docs.ipfs.io/reference/) - [https://docs.ipfs.io/basics/ipfs-implementations/](https://docs.ipfs.io/basics/ipfs-implementations/) > [@Notes on Reframe which is now available in Kubo 0.14](https://discuss.ipfs.tech/t/notes-on-reframe-which-is-now-in-kubo-0-14/14818): > > With the release of [https://github.com/ipfs/kubo/releases/tag/v0.14.0](https://github.com/ipfs/kubo/releases/tag/v0.14.0) It’s now possible to point Kubo at any reframe server, e.g. It’s currently mostly useful for fetching content (there’s no way to do delegated publishing yet [https://github.com/ipfs/specs/pull/285](https://github.com/ipfs/specs/pull/285)) Use-cases Scaling a larger IPFS architecture by splitting responsibilities, e.g. running two accelerated DHT clients kubo nodes and delegating content routing request from other nodes to them, Another way to look at the previous … ---
**Author:** ![mosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/mosh/32/5637_2.png) [@mosh](https://discuss.ipfs.tech/u/mosh)\ **Post date:** [July 26, 2022, 1:09pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/12 "2022-07-26T13:09:13Z")
### Aug 5 Participants: @lidel @BigLep @danieln @Discordian @mosh @adin @Jorropo Agenda: - js-ipfs release & making circuitrelay work (@Discordian) - [Case studies](https://docs.ipfs.io/concepts/#examples-and-case-studies) (@mosh @danieln) - open source program manager - let’s list some example responsibilities (@mosh) - Ecosystem, awesome-ipfs, and [community/projects at master · ipfs/community · GitHub](https://github.com/ipfs/community/tree/master/projects) (@danieln) - (all are welcome to add other items here) Notes: - @BigLep : determine if we need to move the meeting time to accommodate US Pacific. - We have moved [ipfs.io](http://ipfs.io) to **ipfs.tech**! This means [ipfs.io](http://ipfs.io) is reserved for gateway usage, and any DNS issues don’t affect the main websites. - js-ipfs and circuitrelay: - [Snapshot](https://snapshot.org/#/) - IPNS - Docs are getting a lot of use, let’s invest in them ---
**Author:** ![BigLep](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/biglep/32/5869_2.png) [@BigLep](https://discuss.ipfs.tech/u/BigLep)\ **Post date:** [August 5, 2022, 9:49pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/13 "2022-08-05T21:49:19Z")
@mosh : I got feedback that 8am Pacific (15UTC) would make the meeting more Pacific accommodating. Are you ok to update? I can shuffle any EngRes Stewards meetings around to accomodate. ---
**Author:** ![mosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/mosh/32/5637_2.png) [@mosh](https://discuss.ipfs.tech/u/mosh)\ **Post date:** [August 6, 2022, 12:25am UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/14 "2022-08-06T00:25:41Z")
That works, and is still reasonable for European timezones. Just moved the invite. ---
**Author:** ![mosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/mosh/32/5637_2.png) [@mosh](https://discuss.ipfs.tech/u/mosh)\ **Post date:** [August 6, 2022, 12:26am UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/15 "2022-08-06T00:26:37Z")
## 2022-08-19 (@mosh will be OOO. Who is game to facilitate?) Participants: ### Agenda: 1. IPNS Docs 2. Redirects 3. Integration story? 3.1 Lite client for IPFS 4. IPFS Event ### Notes: IPNS Docs - This is an area that @danieln will be focusing on week of 2022-08-22. - What does it mean to be using DHT, PubSub - High level stuff has been in launchpad PR: [https://github.com/protocol/launchpad/pull/188](https://github.com/protocol/launchpad/pull/188) - Plan is to copy and expand to docs.ipfs.tech - Discussion around \*.storage’s naming solution (w3name). Our docs should cover the kind of details that w3name is glossing over. We don’t want to hide over the security details/implications. Meta: launchpad docs. - Sometimes what is copied is going to be out of date. Ideally should be linked to canonical source and remove from launchpad docs. Redirects - Lidel: I would add ongoing bikeshed about \_redirects: [https://github.com/ipfs/specs/pull/290](https://github.com/ipfs/specs/pull/290) (link [Web Gateway support for \_redirects file](https://discuss.ipfs.tech/t/web-gateway-support-for-redirects-file/15011) - already public) - There is concern about how this translates to native implementations (e.g., Brave Mobile and how it won’t use Kubo) - Will let marinate while Lidel is out - Positive here is that we have real users and usecases on this Integrations - Needing more input on languages, hardware, sandboxing of network requests - Want a doc that says “this is what the Chrome peopleare willing to tolerate, this is what the curl people are willing to tolerate” - ONe thing have learned: there won’t be one language or implementation that will rule them all. There isn’t a world of write in C and use everywhere - Have success when folks in Ecosystem go and talk with the communities, ask what they want, etc. Wanting to understand their workflows, if there are internal champions, how they do testing, etc. This is a slow very-attentive approach. - Usecase: Gateway range request. Input: car, path, and range request and returns bytes. - It may be useful for Mark to report back on who he’s spoken with, what he’s hearing, etc. - UnixFS - EngRes focus on specs - Outercore understands the needs and the mechanisms for working with parties - We then meet as an IPFS community on how to get this delivered. ---
**Author:** ![mosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/mosh/32/5637_2.png) [@mosh](https://discuss.ipfs.tech/u/mosh)\ **Post date:** [September 2, 2022, 3:00am UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/16 "2022-09-02T03:00:03Z")
## 2022-09-02 Participants: ### Agenda: 1. [Snapshot case study is live on Docs](https://docs.ipfs.tech/concepts/case-study-snapshot/) (h/t @danieln) 2. IPFS Camp (@mosh) - Ops updates - Content planning - Tell me all your other hopes & dreams for Camp 3. Facilitating this sync (@mosh) - Proposal to rotate every month or quarter (alternating between Stewards and Outercore) 4. Jourdan, virtual events producer at PL, is proposing bringing back a regular quarterly virtual community event. May have already spoken with some people here already. 5. IPNS docs PR [https://github.com/ipfs/ipfs-docs/pull/1258](https://github.com/ipfs/ipfs-docs/pull/1258) @danieln 6. Community calendar ([Community Calendar - options other than Google Cal?](https://discuss.ipfs.tech/t/community-calendar-options-other-than-google-cal/14954)) @danieln 7. Clarify DHT in js-ipfs PR [docs: clarify state of DHT in js-ipfs by 2color · Pull Request #4181 · ipfs/js-ipfs · GitHub](https://github.com/ipfs/js-ipfs/pull/4181) 8. Other? ### Notes: - Meta - Next time use something like hackmd to do collaborative editing - @BigLep Invite Reid to this sync - Usecases: please share if there are other interesting IPFS usecases like snapshot - IPNS Docs - @lidel will look at this while also doing IPNS specs work, thinking about this holistically ([Update IPNS specification · Issue #314 · ipfs/specs · GitHub](https://github.com/ipfs/specs/issues/314)) - @lidel thought: probably don’t need to over-document all the configuration options and flags. - State of js-ipfs union documentation - [Slack](https://filecoinproject.slack.com/archives/CRLC5H4J0/p1662090891190809) (in #ipfs-chatter) is a good thread of someone trying lots of js option - Might be related to [deps: upgrade @multiformats/multiaddr to 10.4.0 by lidel · Pull Request #4178 · ipfs/js-ipfs · GitHub](https://github.com/ipfs/js-ipfs/pull/4178) - @danieln and @biglep will collaborate on getting the blog entry out. - Community Calendar - [Community Calendar - options other than Google Cal? - #2 by BigLep](https://discuss.ipfs.tech/t/community-calendar-options-other-than-google-cal/14954/2) - It’s not easy to just opt into single a specific event - Currently, there’s too much clutter when subscribing - [https://lu.ma/](https://lu.ma/) is already being adopted by Fission - Ideally we’d show all the different events and let users choose - @danieln will reach out to Yuni,Andrew Woo and even Luma to ask about better Google Calendar integration. Specifically, if we can have Luma export and update events to the shared Google Calendar. - IPFS Camp - It is happening Oct 28-30 - There are lots of tracks - Things we hope to see happen - Wish there was less FOMO - missing out on the shared experience. - there will be an everyone-togrther kickoff session, 2-3 hours on the first day - Want to go deeper into the use cases and apps built on top of IPFS - Specs - @lidel have them in better shape - UnixFS - IPNS - Should be part of the implementer’s track - This will take stewards’ time - Education tracks - 101 - Maybe @discordian? - 201 - @dnorman: designing decentralized applications - 4xx - Optimize in production for performance/scale - ideally someone who is operating IPFS in production at scale. Mosh will check with Dietrich. - Virtual - Some options to dial in and give virtual talks ---
**Author:** ![danieln](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/danieln/32/6408_2.png) [@danieln](https://discuss.ipfs.tech/u/danieln)\ **Post date:** [September 8, 2022, 4:02pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/17 "2022-09-08T16:02:21Z")
Quick update on the community calendar and Luma: > [@Community Calendar - options other than Google Cal?](https://discuss.ipfs.tech/t/community-calendar-options-other-than-google-cal/14954/6): > > That is — a GCal solves certain things but for me (and others I’ve interviewed) just having 100s of events “in” a calendar doesn’t help me plan out eg a quarter at a time in a more agenda style. Indeed, that’s our main problem with the community calendar — it’s all or nothing. What’s more, if you copy an event into your own calendar, it doesn’t stay in with the main calendar What about Luma? In our latest advocates \<\> stewards sync we discussed using Luma given our positive experiences at I… ---
**Author:** ![danieln](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/danieln/32/6408_2.png) [@danieln](https://discuss.ipfs.tech/u/danieln)\ **Post date:** [September 16, 2022, 8:34am UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/18 "2022-09-16T08:34:52Z")
## 2022-09-16 ## Participants @mosh @lidel @BigLep @Jorropo @reid @taylor @danieln ## Agenda - IPFS Camp - js-ipfs examples repo - Luma for the community calendar - See Boris’ reply [https://discuss.ipfs.tech/t/community-calendar-options-other-than-google-cal/14954/7?u=danieln](https://discuss.ipfs.tech/t/community-calendar-options-other-than-google-cal/14954/7?u=danieln) - Will require a shared account - Plausible analytics experiment - docs are public: [https://plausible.io/docs.ipfs.tech](https://plausible.io/docs.ipfs.tech) - blog is private; Daniel can give access - Verifying GitHub Org - [https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization](https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization) ### Notes - IPFS Camp - [js-ipfs examples repo](https://github.com/ipfs-examples/js-ipfs-examples) - IPNS Spec - ✅ Verify domains for IPFS GitHub org! ## 📕 Action items - @Jorropo : think about applied UnixFS talk - Engres folks planning on attending should RSVP to the event so that we could get a head count - @daniel ask #ipdx to set up the Github management (similar to [https://github.com/ipfs/github-mgmt](https://github.com/ipfs/github-mgmt)) for [ipfs-examples](https://github.com/ipfs-examples) - @danieln Ask Russel, Lidel, Alex to help with the cleaning of the examples. ---
**Author:** ![mosh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/mosh/32/5637_2.png) [@mosh](https://discuss.ipfs.tech/u/mosh)\ **Post date:** [September 30, 2022, 3:04am UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/19 "2022-09-30T03:04:18Z")
### 2022-09-29 ### Participants - Reid - Mosh - Lidel - Jorropo - Daniel - Tmo # IPFS Stewards \<\> Advocates sync notes 30.9.2022 ## Notes - Docs new topics requests - Redirects! - IPNS - Kubo releases happening in “tick-tock” pattern - Outreachly - IPFS Camp - ipfs-docs: Lidel published some notes for browser vendors: [/how-to/detect-ipfs-on-web](https://github.com/ipfs/ipfs-docs/pull/1295) - Jorropo’s UnixFS talk - docs.ipfs.tech: ---
**Author:** ![Discordian](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/discordian/32/4692_2.png) [@Discordian](https://discuss.ipfs.tech/u/Discordian)\ **Post date:** [October 14, 2022, 2:24pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/20 "2022-10-14T14:24:01Z")
### 2022-10-14 ### Participants - Reid - Mosh - Lidel - Jorropo - Daniel - Discordian - Steve - Elliot ### Discussion topics - @discordian How to advance [Issues connecting from IPFS nodes over WSS · Issue #18 · libp2p/go-libp2p-relay-daemon · GitHub](https://github.com/libp2p/go-libp2p-relay-daemon/issues/18) - For “Create a Simple Chat App” we heavily utilize CircuitRelayV1, since it was removed from Kubo, we looked at using libp2p-relay-daemon, but haven’t been able to connect to it from the JS side in browser (or desktop). - It sees we have a bug related to Secure websockets in go-libp2p that touches TLS termination - One bug related to WS that is present in Kubo 0.16 [fix: websocket transport should send host header by thibmeu · Pull Request #1829 · libp2p/go-libp2p · GitHub](https://github.com/libp2p/go-libp2p/pull/1829) - WebTransport is now available in js-ipfs. It will likely be released as part of the upcoming js-libp2p release this coming monday. Example ([GitHub - libp2p/js-libp2p-webtransport: WebTranport module that libp2p uses and that implements the interface-transport spec](https://github.com/libp2p/js-libp2p-webtransport#libp2p-usage-example)) - 🎬 @biglep: figure out what we need to do get proper regression tests in place for go-libp2p and Kubo so that CI breaks when we’re broken like this. - @danieln IPFS Roadmap & Advocates plan for Q4 - Additional notes from Mosh based on conversations with Daniel, Biglep, Lidel, Dietrich, Reid, JB, Molly - Reposition IPFS as a production-grade solution for key problems with building on today’s web, vs. a cool thing for hackers to try. Improve our internal understanding, & then communication, of what 2-4 use cases IPFS is great at solving, then double down on features, messaging, and devrel for those. - Most devs want end-to-end example apps that showcase the power & capabilities of IPFS (docs & blogs today often focus on 1 feature at a time, which is harder to translate into practice). 2 examples are coming soon 🙂 - Accelerator & seed-stage teams need stronger & more personal technical guidance for making tradeoffs & decisions. - On-ramps for learning & contributing are hard to navigate - Everything should be slightly uncomfortably open (example: roadmap docs themselves) - Specs feel abandoned. IPIP is a good first step. - Docs has accumulated a lot of duplicate material - Smaller-contributions: lacking contributor guides, good first issues, etc. - “Even if we invite people to the restaurant, there are no chairs.” - Traffic on our owned properties is very, very low – a good IPFS blog post gets 300 views. Need to take this show on the road, to conferences beyond Web3, popular programming podcasts, etc. - What are they key quesitons we want to answer? - Getting insight on IPFS reposition around production scale / converge on 2-4 killer use cases - Pull out what the details are and what are the gaps - Understanding others experience contributing to the project - Personas - Contributors - Operators - Consumers / app builders on top - Altruists - fans of the protocol - Another option: going to the other tracks and listening what users are saying like “DeSci” - Analytics - [Plausible · docs.ipfs.tech](https://plausible.io/docs.ipfs.tech) - @Jorropo unixfs talk at IPFS Camp - Looking for a track to speak at - Planning to discuss light IPFS clients & UnixFS - Would need about a 15 minute talk duration ---
**Author:** ![danieln](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/danieln/32/6408_2.png) [@danieln](https://discuss.ipfs.tech/u/danieln)\ **Post date:** [November 18, 2022, 3:08pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/22 "2022-11-18T15:08:59Z")
### 2022-11-18 ## Attendees - @tinytb - @BigLep - @mosh - @lidel - T Mo - @dietrich - @danieln ## Notes - (Mosh) Prelim dates for 2023 events - IPFS Thing likely March 27-31 - working on details with 4 venue options - IPFS Camp co-scheduled with Lab Week, last week of September - (Steve) Congrats on IPFS Camp! - Lots of wins! IPFS 201 track, libp2p day, community call, etc. Great team effort! - (Daniel) | IPFS Website overhaul - (Lidel suggestion) add a section like [https://user-images.githubusercontent.com/3689720/122604033-4e4d3100-d043-11eb-83ab-524760d5acc6.png](https://user-images.githubusercontent.com/3689720/122604033-4e4d3100-d043-11eb-83ab-524760d5acc6.png) (seems its mostly implemented, but we dont embedd yet? [Externally embeddable view · Issue #38 · ipfs/ecosystem-directory · GitHub](https://github.com/ipfs/ecosystem-directory/issues/38#issuecomment-864212924)) - (Daniel) | [demo ecosystem page automation improvements](https://github.com/ipfs/ecosystem-directory/actions/workflows/airtable-pull.yml) - Steve ideas: - Awesome - thank you! - ok to add a readme to [GitHub - ipfs-shipyard/ecosystem-dashboard: A dashboard for monitoring the ecosystem around an open source project.](https://github.com/ipfs-shipyard/ecosystem-dashboard) about the relationship with IPFS Awesome List? - Maybe update [Rebooting the IPFS Awesome List](https://discuss.ipfs.tech/t/rebooting-the-ipfs-awesome-list/14647) ? - (Daniel) | demo [ipfs.fyi shortlinks](https://github.com/ipfs/ipfs.fyi/) - (Daniel) | IPFS Tweet suggestions form [https://ipfs.fyi/suggest-tweet](https://ipfs.fyi/suggest-tweet) - This is for IPFS Twitter account tweets for now (not blog posts, youtube) - (Daniel) | IPFS Advocates Q4 goals - (Steve) Surfacing working groups that are propping up - [Move the Bytes WG](https://discuss.ipfs.tech/t/about-the-move-the-bytes-wg/15454/2) - [Content Routing WG](https://pl-strflt.notion.site/Content-Routing-Workgroup-e59fa94a9c3f48d58480b7daf15bd356) - (Mosh) Spoke with Iryna from Bacalhau earlier this week, she will also add seeds/pointers to Bacalhau in Forum and Docs. - (Steve) FYI: changes likely coming to Hydras (dialing them down) and defaulting CID contact integration into Kubo - [Notion](https://pl-strflt.notion.site/2022Q4-Hydra-Dial-Down-c39f63d473e64f6fabcbfc38fb11d670) - (Steve) Any blog entries need help with getting over the line? - [ipfs.io](http://ipfs.io) and ipfs.tech decoupling - Can related this back to: [August 20 IPFS.io Gateway Outage Resolution & Next Steps | IPFS Blog & News](https://blog.ipfs.tech/2021-08-27-IPFS-io-gateway-outage-resolution/) and [Gateways and gatekeepers: How Google’s mistakes can still affect web3](https://blog.nft.storage/posts/2022-04-29-gateways-and-gatekeepers) - Spam/maleware on IPFS - [https://www.securityweek.com/attackers-using-ipfs-distributed-bulletproof-malware-hosting](https://www.securityweek.com/attackers-using-ipfs-distributed-bulletproof-malware-hosting) - [Revert "feat: add ipfs.pinksheep.whizzzkid.dev" by whizzzkid · Pull Request #331 · ipfs/public-gateway-checker · GitHub](https://github.com/ipfs/public-gateway-checker/pull/331) - Relevant for anyone running a gateway - In the long run, we want to have some mechanism - Both organisational challenge and technical one - The technical challenge will be addressed [by the spec](https://github.com/ipfs/specs/pull/340) ---
**Author:** ![danieln](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/danieln/32/6408_2.png) [@danieln](https://discuss.ipfs.tech/u/danieln)\ **Post date:** [November 25, 2022, 3:57pm UTC](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893/23 "2022-11-25T15:57:16Z")
## IPFS Stewards \<\> Advocates sync 25.11.2022 ## Participants - @Discordian - @lidel - @danieln - Tmo ## Discussion topics - new IPFS examples & connectivity challenges - Two avenues of exploration: - native app with less constraints (Ryan’s work with Tauri) - [GitHub - TheDiscordian/disco-chat: A peer-to-peer messaging app.](https://github.com/TheDiscordian/disco-chat) - Browser apps utilising IPFS (Daniel) - Adapting [GitHub - olizilla/ipfs-get: Get and verify a file by CID from an IPFS gateway over http](https://github.com/olizilla/ipfs-get) to work with the CAR gateway spec - OrbitDB example - how it mutability achieved - [GitHub - peer-base/peer-pad: 📝 Online editor providing collaborative editing in really real-time using CRDTs and IPFS.](https://github.com/peer-base/peer-pad) - CRDTs and append only logs - js-ipfs communication - [Discussion](https://filecoinproject.slack.com/archives/C046HDAHA13/p1669306947192179) - Update docs and Github repo [Next page](https://discuss.ipfs.tech/t/ipfs-stewards-advocates-sync/13893.md?page=2)