Distributed Press Weekly Sync

# Distributed Press Weekly Sync Archive 1: https://hackmd.io/AjEo3DQ7T4GaX7AkobeOCw?edit Archive 2: https://hackmd.io/3-gm0zRrQyKC0vIvLNTQPA?edit Archive 3: https://hackmd.io/wm5Tl5TrTZGBwcEKkEXVxA?edit Archive 4: https://hackmd.io/_fi_yJvwSmaXRQVeJwdlIA?edit ###### tags: `distributed press` `dp meetings`  ### Camille - Wind Down - Composting practices session Our proposal for the session: 1- Narrate case studies (10min) FFF (censorship and dWeb), TLGB (attacked, site recovery, static site and dWeb), LUNAR (site recovery and static site for a winding down project). "We'll explain very soon each of these technical terms, we begin by talking about its benefits and use cases" 2- Then describe: what is dWeb? what is a static site? We could cover the 3 website models (dynamic - CMS server and archives; pre-generated - CMS and archives; static - just archives, to preserve and not change) 3- TIPS / Q&A / or a practical exercise (fauno to decide on this) Exercise such as: did you check if your website has this or that structure? scenarios - disaster planning or challenges people might have when transitioning (wind down, founder leaving, etc) * technical topics: https://hedgedoc.sutty.abyaya.la/yH2riZmaQt-R01ISeDJkcQ# ### Kate Harris - works with US nonprofits that work in a collective manner - mergers, collaborative agreements - functional changes in how they collaborate - very structural - managing humans and emotions - similar to Camille's work, but more on the merger asset transfer side of things - timing - US facing significant challenges w/ website take downs - data security - networks and sharing - data archiving - the sustained collaboration network https://sustainedcollab.org/ - they make grants to orgs that are collaboring - Kate is part of the collab network CoP/learning committee - we could be a resource to a network as well - find Stanford PACS resources for Kate - DP - sutty's website shutdown services - most cost effective - OUR use cases: 1. People who want to preserve their website - cheaper and long-term, almost no maintenance 2. Groups worried about censorship 3. Advisors who want to learn about alternatives to Big Tech - education piece Group of consultants gather once a month - 2nd Monday of every month - step in and educate people about distributed web and federated social media. How does our work bridge with merger and dissolution tasks? ## TLGB Bolivia letter Hello dear Sutty's colleagues, We hope you are well. We thank you deeply for taking the time to write to us and for the interest in telling our experience with the recovery of the website, framed in the attacks we suffered. We feel that this gesture not only makes visible what happened, but also contributes to a collective narrative of resistance against digital hate. ### On the attacks suffered and the loss of the site We confirm that the loss of the site was a direct consequence of a series of digital attacks that we suffered since the beginning of the year 2024, and that intensified in the first months of this year. The most serious attack was a defacement, where the content of our page was replaced in a campaign about maternity in young people and the change was made showing that our organization supported that girls should be mothers, this generated explicit hate messages against people of our organization, which made us think of an organized ideological motivation. We became aware of the attack because several allied people alerted us via social networks and instant messaging. For a few days, our site was inaccessible, and when we managed to access it, it had already been completely compromised. This situation had a strong impact on us: Outwardly, it affected our public presence, just when we were in the midst of an advocacy and resource -sharing campaign for human rights defenders. The loss of online materials and documents temporarily limited access to key information. Internally, it generated anguish and insecurity in the team, and forced us to review our communication and protection strategies. Fortunately, all members of the collective are safe, and we were able to activate containment networks quickly. ### On the context and progress of hatred in Bolivia We completely agree with your interpretation: there is a systematic advance of trans-hate and anti-LGBTIQ+ discourse in Bolivia. This wave of hate is expressed on multiple levels: from discourses in social networks, traditional and religious media, to regressive public policies. A key point in this context was the legal setback linked to the Gender Identity Law, from court rulings that limited its scope, especially in 4 rights: marriage, adoption, political participation and confidentiality. This was exploited by ultraconservative and religious fundamentalist sectors to legitimize hate speeches, discredit the rights of trans people and, in many cases, justify symbolic and physical violence against our communities. Political Characterization: Opposing and Allied Actors In our specific case, we identified several actors who have played an active role in fostering this climate of hostility: **Opposing actors:** Fundamentalist religious groups and collectives, many of them articulated under the umbrella of “pro-life” and “pro-family” organizations, with strong media presence and significant economic resources. Conservative political leaders, both from right-wing parties and conservative sectors within the ruling party, who have used transodiant narratives to gain social base. At this moment, presidential candidates are expressing hate speeches. Some media outlets, especially television, have reinforced stigmas and given space to voices that deny the human rights of LGBTIQ+ people. Bolivian digital platforms and organized accounts that are dedicated to disinformation, many times anonymous, but with a clear line of attack to our community, we mention digital warriors, who launch disinformation and discrimination campaigns to our population. **Allies:** Feminist and human rights organizations that quickly came out to support us and have denounced the digital attacks as part of a broader pattern of criminalization. International support networks like yours, who have been key not only technically, but also politically and emotionally. Allied journalists who sought to tell our story with respect and context. Some local ombudsmen and human rights offices that have shown sensitivity to the issue, although with limited resources. ### About the recovery process and digital care The recovery of the site was possible thanks to the campaign that you promoted, for which we are very grateful. The technical support was essential, but so was the political recognition that it was not just a technical problem, but an attack on our existence and our voice in the digital space. Based on this experience, we began to implement some digital security measures -such as changing passwords, reviewing access, using two-step authentication and basic training for the team- but we are aware that we need to continue deepening this work. Many of our organizations do not have the human or economic resources for a robust digital strategy, so support in this regard is vital. About how we found your campaign We learned about your campaign thanks to an email communication where we found the call for proposals, and we decided to apply with hope but also with some urgency. Receiving Sutty's support was a great joy and a sign that we are not alone in this struggle. Thank you again for joining us, for bringing your bodies ("poner el cuerpo" en español), your knowledge and your listening to this process. The solidarity you generate not only rebuilds sites, but also strengthens resistances. With love and resistance, TLGB Bolivia ## 2025/04/29 - Weekly Andi<>Ania Sync ### Agenda & notes - send Brynn the marketing report - MOU - Dripline post - Andi to work on this - schedule a meeting with **Kate Harris group** :white_check_mark: - prep for that meeting https://www.kateharrisgroup.com/ - validate a one-pager service offering for Camille (the wind down) that she can use in her meeting with **Exit to Open** [Link](https://docs.google.com/document/d/1wbOS9Y2lvdHaIp2rrMcFsms6DyMLlHtTQEDG4Ccnxa4/edit?usp=sharing) https://ssir.org/articles/entry/closing-nonprofits-exit-to-open?trk=feed-detail_main-feed-card_feed-article-content https://www.colorado.edu/lab/medlab/exit-to-community The reference is Password: uuv3ieghoh0ma7Ia https://presupuestos.sutty.nl/en/the-maintainers/ - The Maintainers follow-up - fauno to send a *hiiiiiiii how you've been?* - Plan future comms pieces ## 2025/04/17 - FFDW Final Sync ### Notes - What went well - good team work - had room to experiment - changed the milestones - ended up with great tools - Planned to have IPFS in the infrastructure - directed from CMS to the IPFS but this didn;t work - sync protocol changes - didn't get to adopt the IPFS Rails plug in; this was a miss - but have the whole activitypub implementation - Anai - UX add-on was really helpful - Akhi - building UX on the Dweb publishing - Bryyn - how to balance the solidarity work with the paid services - Danny: AT Proto - there is some funding available for this; and there is also the IPFS and FC link; they ise IPLD - would love for DP to saty in engaged in the broader FFDW community and quarterly calls - sutty as a UX leaders in the DP space! - there have been a few conversations about talking about usablility in dweb; it's not easy to fund though but maybe this is because there isn't the right level of cooperation amongst groups - UX hackathon idea - - - ## // - FFDW Quarterly Sync ### Participants ### Agenda ### Notes - Funding Ops and Impact Team (FOIT) pronounced Foh-it - this is new FFDW impact team - Erin O'Connor is a new Prog Manager - Some projects will move between portfolios (from Brynn to Erin and vice versa) - Guardian Project + Proofmode - inventing in marketing - they have some cool vidoes and graphics in their slides - ProofMode Capture is a open source camera app for iOS an Android - OpenAI model - ghibli mode - no guardrails? - AI detection is key component of this work - will run an AI model to detect AI runs in the browser - Preserve - education - cutting room - journalist tool - using proofmode tech - rightscon - Witness + Guardian were also part of the labratorio event in Ecuador - Smithsonian - very cool project where they have recovered and reconstucted recordings from the 1820s! Alexander Graham Bell and Thomas Edison days ## // - Weekly Team Sync ### Participants andi, ania, mauve, fauno ### Agenda - wrapping up ### Notes What's on our plate to wrap up?? **TECH DELIVERABLES**: - we need to merge a few PR, update documentation and do an announcement - PR for uncensorable frontends is ready - akhi mentions that docs are ready - imlpemented a limit for titles and descriptions in the explore.dp... - social inbox activities - update homepage with explore and donate **COMMS** - craft a calendar for the following pieces - case studies - andi will check grammar (ping on signal) - (indexer, a tech term) EXPLORE PAGE - Will do announcement about explore.distributed.press, post calling other nodes to join the index. Tracking issue: https://github.com/hyphacoop/distributed-press-organizing/issues/224 "How do I find stuff that's on the dweb? We've released our new explore page that shows every known site that uses Distributed Press If you have your own DP server, add it to our explore page and help people discover your sites" - uncensorable front ends - finishing site recoveries and case studies about desarquivo and LGTB Bolivia - once the websites are recovered, do an announcement about that - marketing report and strategy - Ana needs and extra week to finish the report because she had emergent trips during February - she got the information she needed from documents and conversation with other team members - marketing report will be presented to andi te get her feedback and validation before finalising - UX report **ORGANIZATIONAL** - agree on the long term governance - maintenance of DP between hypha and sutty - final report to FFDW - when is the deadline, end of March? - present the project at April 4th meeting - define agreement on what we want to present - andi has been working in the governance piece **MAINTENANCE** - haven.day and fight for the future have used DP to distribute their sites - do they require maintenance? or any type of health-check from time to time? - infrastructure: hypha team figuring out how to do long term maintenance - bug fixing and making sure that sites don't go down - we need to set up a process to automatically update thigs for us - i.e.: dependabots - split the certificates to get one cert per website and be able to renew them independently - everything is updated in the same process, even if the certs are independent, if the process fails everything it will affect everything - we can postpone this until we get some money and then invest some hours refining this - communication channel with infra team: ping elon through matrix. there's also a public infra room - DP monitor - there is not a definitive list of things that need to be maintained and fixed yet - if hypha will do that work, we need to have a definitive list and assign it to specific persons **CLIENTS** - can we use open collective for clients? we need to craft it in terms of "you are donating to DP" instead of *payments* - and what about for labor hours? - andi can talk to ben to get details about OC use - The Maintainers **Next meeting: March 27th** Let's schedule a Wrap-up party!! ## 2025/02/20 - Weekly Team Sync ### Participants ### Agenda - confirm meeting with brynn :heavy_check_mark: - tech update - Uncensorable front end - What's left for explore.distributed.press? - Periodic clone - website recovery status - keeping track of leads and alliances - optional: small retrospective on our progress - tech update - uncensorable front end: akhi has an initial version, mauve will do a code review - screenshots look good! **- pending documentation** **- pending announcement post** - Will do announcement about explore.distributed.press, post calling other nodes to join the index. Tracking issue: https://github.com/hyphacoop/distributed-press-organizing/issues/224 Also will add some sites that aren't marked as public - TO-DO: add links in our main page (homepage, below GET STARTED button) for - EXPLORE - UNCENSORABLE FRONT END: Donate - host that on IPFS and share a public link, instead of a domain - Periodic cloning: it could have high impact - Mauve will add a new api - Sutty could add a box on the onboarding, when users do the clone, they can choose "periodic clone every week" - website recovery status - brazilian website recovery is progressing - they provided backups and docker compose files - sutty was able to run the actual server in a computer - wget and hyperlink to find linkrot - suggested a few changes to the website bc there was too much pagination, the org agreed, so it's recovery + optimization <3 - bolivian website recovery happening next week - they also provided backups - Ania working on two articles (deliverables) short case studies that explain situation and how the site was lost, and how sutty solved it. Aiming to have them by March 3, send to Brynn and on blog. Should use them strategically - Leads and alliances: - Added table to project board - Haven.day: email sent, waiting for their reply. Maybe send another email announcing that we will be working on periodic cloning and how that will benefit them - Shared updates about Wind down, Fight for the Future and Flick Foundation - we are waiting on the three of them - Andi suggests that we wait for Camille's reply and then remind her about the intro with The Decelerator, (offered by her) - Bizdev: Chad met Patrick a couple of times, andi has to follow up, it's similar than what we wrote for the grant - Check how the social inbox handles activities - fauno suggests that we take a look at this - Mauve wants to check what's the implication of this - will look at this on Wednesday - fauno adds that it's good enough to document how we handle social activities - he can write it - Helia small grant - we received a comment in the Slack encouraging us to apply - mauve suggests that we get a soft-approval, maybe having a champion inside protocol labs first - Project governance - Sutty to add their ideas to Mauve's document :heavy_check_mark: https://hackmd.io/w5y3IVcfTXSnlV7cC4PE8A?view - Reflection on what we've built: Ania will send a few questions to each team member to reflect on our progress, the value of our tools, the cases where they could be useful, etcétera. - Will work as a brief retrospective for the team members - Will be useful to keep crafting social media posts about our tools ### Notes ## 2025/02/13 - Weekly Team Sync ### Participants Ania, Fauno, Mauve ### Agenda - website restoration - potential lead in sciop - follow up on haven.day - the wind down progress - final report and closing meeting with brynn ### Notes - checkin: - fau coworking on website restore - Ania work-cationing - Mauve went to cofounder speed dating - Updates on leads: - fight for future - No new updates - whats missing from their side? - They want to publish *all the sites*. Can we aim smaller? - Offer to book something short to help or announce what we've already done - Ania: Send announce draft and CC mauve's calendar, send via email - Faras (?): Arranging meeting with fight for the future, be aware but not mixing the activities - flikr foundation - We could send an email to follow up - Ania: Check in on their IPFS experiment and offer help - peter&patrik&andi grant - Are there details in the doc they're putting together - Fauno commented on matrix and will add to the doc - Doc: https://docs.google.com/document/d/1Tfprd9zXvYTqYIHXYcgjdxckOOiGq2IO_YIGPLz6BIM/edit?usp=sharing - Leaving this for next month, would be useful to review by next week - haven.day - They added info about DP to their site - We should make sure the clone is periodic and they have docs for view - Potential feature would be to make DP do the periodic sync themselves - Mauve sent an email, waiting for a reply and will aim to craft a strategy together - Ania or fau down to join the meeting - sciop - distributing datasets that could be deleted by nazis over torrent - reached out asking for mutable torrents - a pita to implement - voluntary but high impact for visibility - communities would seed, opportunity for social pinning - Could go for rapid response grant - sutty could reach out to accessnow.org, they have a digital safety helpline - Mauve will invite johnny to matrix, will keep talking about this The wind down: - Meeting this monday, presenting proposal with amounts. Amounts are similar to what other services are providing. - Sent email on Monday with service offering and outline for the joint article - Could we migrate data from social media? (fb, insta, etc) - Social medias can be updated themselves - we could convert the exported data to AP, scope a grant for this and wind down can help find potential users/funders - Small volume of clients right now, works with bigger org called deaccelerator who does 50-40 orgs monthly, could do intro to them - Would want a form down the line to make it more "Self serve" - Should make site to help with cost estimation: explain how it works, crawl and explain estimate, make it visual - Question about open collective, can we get subscription payments? Can we do custom links like "click this to pay 500 a month" - Existing OC: https://opencollective.com/distributed-press - Seems like we can set up predefined tiers. Could do monthly or 1&2 years up front - strategy - hypha would subsidize work on bizdev/grant writing for a couple months - FFDW - Site recovery: need two brief articles by March 3rd, by Feb 20th will do small marketing campaign then 2 weeks later will be marketing strategy. - Have a backup of desarquivo, also got a docker compose recipe for their old PHP project. Really big website so will run it overnight, will then run fix for links. Looked at the DP scraper but will focus on wget first. Bolivia folks working to produce backups, need them by next week or we'll recover via wayback machine. - Will do announcement about explore.distributed.press, post calling other nodes to join the index. Tracking issue: https://github.com/hyphacoop/distributed-press-organizing/issues/224 Also will add some sites that aren't marked as public - Need to update docs with indexer - Also UX report brief - Linkrot project (Brandon) reached out before but lacked budget, maybe we can offer our new numbers for site hosting - Should coordinate a live demo with mai to clone getdweb live. Should test it out first before live demo. Mauve will reach out to Mai ## 2025/02/06 - Weekly Team Sync ### Participants Mauve, akhi, fauno, ania ### Agenda - check-in - indexer - gitcoin uncensorable frontends - sites recoveries - social inbox + templates - governance ### Notes - check-in - mauve's birthday yesterday! - akhi doing an activity on campus - fauno a lot of argentina issues! - ania trying to keep up with the news and still live the life - indexer: - "This milestone collates previous Distributed Press work, gathering it into a site index that lists websites currently using Distributed Press. Basic site metadata will be scraped and made available. The deliverable will conclude with an announcement post calling for other nodes to join the index. Documentation will be updated to include index mentions". - announcement: - on the git hub repo we have a JSON file wchih lists all the instances - if you have a DP instance you are hosting, add yourself here and you'll be included in the index, by sending a pull request here - to-do: add public manual sites https://github.com/hyphacoop/distributed-press-organizing/issues/223 - update documentation - apply character limit to site descriptions - uncensorable frontends: - akhi suggested polygon or optimism - mauve suggests to poke vincent to choose this - estimated completion date: end of month - sites recoveries - the process is running smoothly, the 2 chosen organizations are replying and sending their backups - social inbox + templates - fauno added social interactions in sutty templates - testing this in dweb.sutty.nl - found an error in Social Inbox (comment removal is not updated by the Social Inbox) - we should experiment asking people "please reply here and interact" so we can test the interactions on the site - governance - sutty had an assembly and discussed the proposal for co-governance. they want to keep DP up as it has value for the coop - suggests that we have a written agreement on how we'd put DP in maintenance mode until we get funding - sutty's commitment to maintenance - book some monthly hours to pursue grants - wondering if hypha also want to commit an hour or two each month to grant search - mauve could support with reviewing - systems maint. by hypha infra team - how much time could this take? aprox 1 hour/month - we could talk after 18/02 when andi comes back - TO-DO! suggests that we add this ideas to the hackmd that mauve started ## 2025/02/06 - Meeting with Brynn ### Participants ### Agenda ### Notes - How was the open call? 10 submissions - Sutty has also responded to the people who were not chosen to offer some technical advice that can help them out without doing the full recoery - The "winners": - Brazil - feminist archive - Bolivia - LGBTQ+ collective - Brynn: how are we going to engage with the remaining 8 organizations? - fauno: if the websites aren't in maitenance can move these to DP; others need help with malware infections - group in Cameroon interested in internships - mentioned the Wind Down and other interest that the campagin has generated - Go over the indexer progress - Brynn - add FFDW site to the list when it's done - have one last synch after the end date of the current grant - Brynn to send final report template shortly ## 2025/01/30 - Weekly Team Sync ### Participants Ania, Akhi, Fauno, Mauve, Andi ### Agenda check-in biz dev/ grants: https://nlnet.nl/commonsfund/ charging the wind down removing KUBO and replacing it with helia chosen orgs for the open call ### Notes check-ins: origin of names in the team, nicknames, and meanings. story of the name "Sutty" fauno is fine, fixed som bugs and is close to having the fediverse interactions in one main template of the CMS akhi: indexer is almost done, final PR is ready to merge mauve: tried releasing one of fauno's bug fixes. investigating Helia instead of KUBO andi: is good. she's been working with some biz dev pieces ania: is fine #### biz dev/ grants: * NLNET Commons fund * https://nlnet.nl/commonsfund/ * new funding that closes on Saturday * reached out to Patrick, he doesn't have time for this, but based on previous conversations they've had, andi is putting together a proposal for the fund. pieced as a research piece, doesn't have much technical challenges * will share the application once it's ready * if we don't manage to get it drafted by Saturday, we can participate in a next round * IRAP (?) funding * andi will have an introductory call, if DP is selected for this, then she'll loop back with the group * Follow up with Maria Bustillo * Wind Down * Mauve and fauno did cost estimates and arrived to: 2USD Giga / year / node (with IPFS and Hypercore) * Did not include organization or infrastructural costs * We need to decide what exactly we're offering * Long term archival 5ish years? 10 years? * Adding Filecoin long term achival * Helping organizations understand how to deal with their site while they are cooling down * We can scope it: * small: helping with the preservation of the site while they are cooling down * medium: Long term archival 5ish years? 10 years? * Basic storage: one website for year, bottom 1 Gigabyte in size * Ballpark our fees of labour and infrastructure * Org comes to us, we clone the website. Here's the static site. Here's the cost of maintenance. I.E: one hour per month. Our labor hour is expensive, would it be payable? * SaaS is built on having a large amount of users and charging a small fee to each one * fauno: Vercel and Netlify are not cheap at all * We need to be able to charge them upfront for the amount of years they want to have preserved * After the initial labor of cloning the website, it's just maintenance of keeping the server running. That could be split between the websites we end up hosting. * Are we the ones to do this work? is DP neccessary for this * It comes as part of our narrative, as we are working to help with resilience, recovering sites that are lost, that we can also work in preserving sites. * With 500 sites a month at 20usd a month we would reach out current burn rate * or 40 sites paying a year upfront * We can establish a range of costs that we want to charge, and talk to Camille the see the viability of this, and also the volume of work she foresees. * When we want to invest of social pinning, we can move forward with creating a few nodes and go in that direction * Ania and fauno will put something in writing and share it with Camille for next week * chosen orgs for the open call * 3 orgs picked, 2 from Brazil and 1 from Bolivia * interviewed the Brazilian one and the one from Bolivia * interesting profiles: * LGBT nation-wide org, were attacked and lost a website. * archive of feminist anarchist antiracist organizations and material. might have backups pero else, we can recover with wayback machine * KUBO :wave: and Helia - welcome ? * it would lower our costs * if we want to migrate infra in the future - KUBO is demanding of resources and complicates the migration * would IPNS keys be able to migrate? * Helia is faster, uses less resources ## 2025/01/23 - Weekly Team Sync ### Participants Ania Andi Akhi Fauno Mauve ### Agenda Checkin Indexer status Gitcoin grant Open call (site recoveries) update fediforum Future of DP ### Notes #### Checkin - Andi: went for a skate and got fresh air - Akhi: Went skiing, way too expensive - mauve: played a Magic The Gathering with really commited people - Ania: Seeing friends - fauno: has been training and the club's temperature is hot --> ### Indexer status - akhi is working in the UI now, creating a table - the structure of the code is pretty set - we're about to release the first version, when that's done Mauve will ping us for feedback - who could give feedback about the UI - anyone on the team that could do a sanity test - the indexer website should be linked to the home page - how often should it fetch data? a weekly sync could be good enough ### Gitcoin grant proposal - we did a proposal for uncensorable frontends - once the index is done, akhi will start working to develop this - we got around 800usdc - it will be enough to deliver a small thing and then try to aim for a bigger funding ### Recovery cases - we got 10 submissions - feminist organizations, lgbt collective from bolivia, indigenous collective from (?), someone from brazil - fauno suggests that we keep it open to keep collecting cases, even if the grant is closed, to have a bigger database of people who need the recovery and we could get in touch with. - EMAIL THE NON SELECTED with: we didn't selected you this time, but here's a list of resources they could use, "if none of this things work for you, get in touch with us and we can offer our service to support you" - another idea is to use that database to pursue a grant saying "we can recover all this sites and help preserve collective memory if you fund us" - tomorrow they will be selecting the cases. apparently there are at least 2 or 3 technically recoverable and also interesting and aligned <3 - next week they'll be contacting the selected cases - another case (outside the Resilient Grant) is Disco Coop Primer - we are waiting for them to get back to office and write the comms about this - Ana could meet with Andi because she want to gain understanding on strategic ### Fediforum - there's a fediparty and fauno could do a demo of the CMS and Social inbox and Social Reader - there's momentum to talk more about the social inbox - fauno will register for fediforum in april ### Fediverse and AP / Social inbox offering - we have a bunch of open threads which are moving in the right direction but not quick enough - should we send the deck about social inbox to new contacts? - andi says that she would prefer to have a more solid proposal and a really narrowed offering before contacting people, because we don't want to repeat the loop of "showing something nice to people and have them say 'that's cool' without a clear sales proposal" - andi suggests that adding atproto could draw more eyeballs - considering the conversations she's read along this days - how would we fund work into adding bluesky? - idea: since the data is open, we could integrate atproto into the social reader (i don't know if i got this part correctly into the notes, need mauve to edit this) - andi mentions that chad has been looking at funding around this and will let us know if there are any leads ## Future (collective?) governance - Mauve put together a document with all the resources there are in DP - Had a meeting yesterday with the strategic team of Hypha - Questions about the benefits for Sutty, benefits for Hypha, from DP - Sutty should read this and answer, then we can reconvene and re-group - Sutty has a coop asamblea next week and will analyze this ## 2025/01/20 - cost estimates * storage is triplicate: https, ipfs, hyper * more protocols are more storage (unless we change storage model?) * so it's 3x per node more expensive per gb than s3 * we don't have per gb, we have a bulk amount that's already paid * so s3 comparison is the bare minimum * digital ocean volume storage was a more accurate cost because it's what we're using (6 cents / GB / month) * backblaze and storj are cheaper than s3 * 6 cents * gb * month * 3 = 18 cents / months * 12 months = 2.16 USD / year * egress is unlimited at DO * charge per website rather than storage * looking at other services https://vercel.com/pricing * sutty did this and they tend to be super expensive * most websites are going to be under 1GB * charge a flat fee * proposal: * minimal amount per month * charge per GB per publisher * minimum per website * every website adds load to the service ## 2025/01/16 - Weekly Team Sync ### Check-in fauno: emotional yesterday, worried today mauve: presenting at AI tinkers, a local meet-up, a language model does "tone changing", applied a calm and caring tone to a trump tweet ania: cats getting along, pheromone diffuser seems to help andi: kind of distracted and confused tbh ### Agenda: - biz dev opportunities or leads that are on - review project board - open call - sites recovery - index ### Notes - biz dev opportunities or leads that are on - the wind down supports organizations that are in the process of shutting down - giving recommendations about what to do with their sites - she has a narrative around the importance of keeping sites "up" or archived because it's social proof for individuals that move on or are fired - sent a follow-up email - suggested that we write sth in collaboration - sutty discussed what could we propose to them - "we need to archive this website for 10 years, what would yo do?" - we can already clone the websites, give instructions for people to add or delegate DNS records to DP - ideally sth that orgs can do with a couple clicks. - orgs should pay i.e. 10 years ahead domain registration in order to have that up for a long term - we need to put a price on how much will cost to host a website for 10 years and that would be paid upfront - long-term registration - sutty had an idea for a mutual aid domain registration entity - instead of having personal responsibility for keeping a domain up, you delegate that to the mutual - andi thinks the call went well and camille has a lot of interesting contacts - put parameters around what the solution would look like and send it along to her - how this would be different to webrecorder? - in the blog post, we should also gather other orgs and resources that we suggest for closing processes. "you migh wanna do different things, this is one that we offer, there are other such as... webrecorder, etc" - **TASK 1**: create a draft for a collaborative post Wind Down + DP - **TASK 2**: write down a commercial service offering for Wind Down and get Camille's feedback on how this serves the orgs (and WD) needs - cloning now is we crawl every single page and create a static site now - webrecorder does not save the records as a static site. you need to replay the record in their specific software. very hi fi archive but it has to be replayed by a specific software. - ours is a different experience - do they care about the dweb aspect of this? or they just want to keep the site up - we know that wind down is dweb adyacent - mauve feels that a better solution is sth that does a crawl and uploads it to github - regular storage services offer less risk than us - what are we actually providing besides file hosting, since file hosting is not what we do better. - **we should find out what volume of work this would imply. is this a game changer, a big revenue stream for DP? or sth ocasional? what would they be willing to pay?** - Wind down: fauno will lead this offering - Schedule a date to follow up with Flickr Foundation - Fight for the future: waiting for them to run the script on all their sites. Announcement ready - Patrick - Chad from Hypha is preparing ideas for journalism conferences and dweb - Maria Bustillo: digital ebook alternative - we are waiting for an information from her and where would DP fit in - open call and site recoveries - extended the deadline for applications - we have 7 applications (bolivia, uruguay, guatemala, africa) - their work is what we were aiming to help! - checking the technical criteria - also taking notes on all of the channels we used and the feedback, so that Ana from marketing can run an analysis - two pieces coming up about site recoveries (lunar and commons transition) - sharing on personal accounts - hypha also shared and did direct outreach - timeline: are we on track besides pushing the open call one week further - index - akhi is working in the changes that mauve requested - submitted pr for renaming the DP cli package - mauve submitted a PR to DP API, making it more efficient for building the index - p2p links as well as urls - UI: website names, descriptions, protocols - how would it look like? - we seem to be on track - ffdw call scheduled with brynn, regular bimonthly, Feb 6th - send an update by the end of the month ## 2025/01/14 Wind Down Meeting Camille suggests that we check https://endings.uvic.ca/ and https://donotresearch.substack.com/p/sarah-wambold-and-rem-moore-only "Dignified degradation" We explain the service of migrating to a static website for easier hosting and stewarding. Less about recovery and more about long term stewrdship. Availability of resources for average person? What's long term? She mentions a 5 - 10 years window that allows people to have social proof about what they've done. Flat static site version of this. For ORGs that do white papers, a way of storing them. System in decline - composting Berkana Two Loops - she'll send an article about this If you aren't sure what to do with the website - where to point them to? "What's the wish for this organization?" To have people touch a button and that puts their site on freeze, archived, preserved. Manage the email links that were present in the site. We should manage the domain thing. Andi suggest that we write something together - given that Camille has a newsletter. And then align the technical services that we could offer! Also adding us to "themantainers.org" community *** andi's notes*** * Archival and long-term stewardship of websites * Camille is connected to the Dweb Community * Not so much recovery focused here * fauno gives an overview of the project * so we could create a static version of the websites that belong to the organizations that are closing * what would be required in terms of stewardship? * [https://endings.uvic.ca/](https://endings.uvic.ca/) * Martin and Jenelle - cool people * Graceful Degradations - survey about digital humanities that have been lost * They are using subversion for version control * Long term persistence for long term resources * https://dh-abstracts.library.virginia.edu/works/1179 * what does long term stewardship mean? 5-10 years * have some ability for ex staff to point to the work they have done * static site version of this * but there is along longer term document storage * berkana two loops model - about composting the work * things that get touched more often are easier to recall; things that are less used are not as available * if you aren't sure what to do with your website then here are some steps to take x, y, z * version control feature? * wish: that they can do somewhere and bury their website where is can live for 5-15 years; name a benefactor to steward the work * ability to take the snapshot and provide a winding down plan * start-up non profits is an area of focus this year * on advisory board of the Maintainers !!! * Hospicing modernity * SSIR issue on this ## 2025/01/09 - Weekly Team Sync ### Participants mauve, andi, ania ### Agenda - check-in - update on M5 milestones: index and site recoveries - supporting the open call outreach - Social Inbox Dripline post - biz dev: flickr foundation and the wind down ### Notes - check-ins - ania: peaceful and chill days - mauve wanted to accomplish tech things during their time-off but possibly needed a break from computers - andi: didn't almost touch the computer during the break. had an "all-ages" new year party with 25 persons - akhi: worked on peersky, had a family member loss - update on M5 milestones: index and site recoveries - indexing - indexing is ready, requested changes from mauve - mauve needs to change sth in the raw URLs to support the indexing - akhi plannig on publishing his art through DP-CLI and document that - site recoveries: in december covered process for recovery (setting up legal agreement with selected group, crafting terms and conditions, made english and spanish visuals) Need to extend a few days to get more applications in. Are there particular orgs to involve? try a personalized approach. Ana from sutty working on marketing suggested we don't change tactic too hard. Stick to traditional approach to be able to do an analysis on what's working now. Wind Down and Stewarding Loss are potential candidates. **- Please add your contacts here:** https://docs.google.com/spreadsheets/d/1dHS5DNLjWVoJ3LFJTlS5IrplGE400b-nuHB5_jp3Bzg/edit?usp=sharing - talk to the wind down with a "by the way..." and send our open call :heavy_check_mark: - OPEN CALL links! https://x.com/dwebpress/status/1876280594742857912 https://bsky.app/profile/dwebpress.bsky.social/post/3lfasw3vymc2l https://distributed.press/2025/01/06/get-your-website-back-reclaim-your-history/ https://social.coop/@distributedpress/113798539028668871 https://social.coop/@distributed@distributed.press/113782059513468530 https://sutty.nl/en/recovery-form/ - Hypha will write a dripline post about the social inbox integration, talk about how we implemented and how it relates to social media landscape - **wind down**: camile helps NGOs end their projects. Need to be able to archive sites that won't be maintained anymore. Need to find out if they need a provider or a collaboration. - decentralized publishing is relevant here? - won't be better to use webrecorder? - or the wordpress to static site pipeline would be better? - not only archiving but also having a way to showcase them over the dweb - like a "graveyard" of closed NGOs - we should try to get them to apply at least one website for recovery - **flickr foundation**: - if they take 3 months to move, it would be difficult to keep up with our current budget - it would be cool if they wanted to do the social pinning - this month they'll be pretty busy and want to do their thing with IPFS - send a follow-up email with a link to the collab channel in matrix, also the onboarding page for them to clone a site for free https://distributed.press/get-started/ Hi George, I hope you're having a great start to your week. It was great meeting both of you on Thursday and having the opportunity to discuss the work Flickr Foundation is doing, as well as sharing the purpose of Distributed Press’s work. We truly appreciated our conversation about the possibilities and challenges around decentralized publishing and social pinning—it’s always inspiring to explore these issues with like-minded individuals. As mentioned during our meeting, we’re more than happy to assist with ideas or provide guidance if our team can help yours. Please don’t hesitate to reach out through email or join our collab channel https://matrix.to/#/#distributed-press-collab:tomesh.net if there’s anything you need as you move forward. We also suggest you try our single-site publisher, an excellent way to easily have websites published over decentralized protocols. The tool is available for free here: https://distributed.press/get-started/ We’ll be in touch next month to check in, in the meantime, wishing you the best with the next steps! Warm regards, https://matrix.to/#/#distributed-press-collab:tomesh.net - write now but send by end of February - "how did the IPFS go, we talked about the social pinning idea?" - we have all this peer-to-peer links but don't have a plan on how will people view them - similar to the problem we were adressing in OTF grant and Equalite - idea: translate Agregore and Peersky docs to Spanish - the idea is that we should add a small tutorial on how to actually view this things on the dweb - we have published content - and we have a browser that loads that from the dweb - small fund to run an event in Argentina to use this tech? - https://grayarea.org/initiative/cultural-memory-lab/ - many opportunities: https://github.com/ralphtheninja/open-funding ## 2025/01/09 - Flickr Foundation Research Notes (move elsewhere as needed) ### Agenda Preparing for the meeting with George from Flickr Commons ### Notes - Key about Flickr Commons pages to read: 1. https://www.flickr.org/programs/flickr-commons/ and 2. https://www.flickr.org/programs/flickr-commons/flickr-commons-how-it-works/ - They are developing a 100 year plan to safe guard the Flickr Commons; it definitely has co-op roots/ influences. More about the plan here: https://www.flickr.org/about-us/the-100-year-plan/ - This includes the **Data Lifeboat** plan (presented at an FFDW call last year): https://www.flickr.org/programs/content-mobility/data-lifeboat/ - An update on this work: https://www.flickr.org/from-desiderata-to-readmes-pt1/ - Take a look at the four programs: https://www.flickr.org/programs/ - I wonder if there is something we can tap into or add in their Content Mobility stream? This reminds me of the work that Starling is doing and I wonder if there is a way for DP to support this in the same way we have worked with Starling? https://www.flickr.org/programs/content-mobility/ - - PCC post on the origins and beginnings of FF https://platform.coop/blog/how-you-can-help-to-preserve-billions-of-photos/ - Flickr repos: https://github.com/Flickr-Foundation - Mauve talked to infrastructure team and knows what we should charge by Gigabyte What might be interesting to George? - Distributed Press overview; especially as it relates to **archives** and long term resilience - Ask questions about the Data Lifeboat project; where it's going next and what the outcomes will be. What does the technical roadmap look like. - Potential to use DP to pubish the Flickr Commons website? - Would they be interested in working with us to distribute their website(s)? - Website cloning feature? it's free up to site limit 1 Gigabyte. If there's more data, they should pay - Create a frontend for Flickr Commons for people to onboard - content mobility policy - getting people to help pin the content and make it available for others - Similar to DAT protocol for academic publishing https://dat-project.org/resources/publications/ ## Notes from the meeting with Flickr Foundation - George - software for 20 years. was in design - co-fonded Flickr Foundation 3 years ago - Want to keep the photos around for 100 years - they are both in London - Alex - is a developer; in the GLAM sector for about 8 years - mostly focuses on long term storage - two Flickr archives that are generated with the same content query (?) - Data Lifeboats - found that people were not super interested in the emergcy situation - but were more interested in using the service when things are fine - making a tool that allow people to collect/ehance their collections - it's tricky to find software where it decentralizes in numerous platforms - Mauve suggests holepunch/hypercore/pears and why it's better than IPFS - what's their technical stack? - sitting on local hard drives - experiment with IPFS in a couple of weeks - 10K most viewed pics into IFPS - they are working with FFDW on the dentralized piece - aren't sure if they'll add them to Filecoin; roadmap isn't clear - we ask how do they want to approach to content mobility - Flickr Commons - adding pictures from museums to Flickr content mobility stream of programming - Content mobility means: Have an understanding of the life cycle of a picture, where it comes from, where they propagate to, including all the annotations and conversation they've received - like data portability - we explain the idea of social pinning - archival of Flickr content could use this protocols and add a layer, a front end to incentive people to store copies and help keep it around - "open an app and be able to contribute, without having to install and administer complex systems" - social group being able to archive an amount of photos - they have 120 cultural institutions, trying to convice them to be part of a network - safe ?? network - this is a more formal situation - informal social archiving network - bc there's a lot of social structure woven into flickr - use case for journalists and activists, bypassing censorship - mauve suggests that tools for communities could scale up to larger institutions SIMPLE EXPERIMENT could be: - shove data into DP and put together a simple app - list of URLS and file explorer - ## 2024/12/12 - Weekly Team Sync ### Participants ania, mauve, fauno, andi, akhi ### Agenda - FFDW Final Report - Website updates - Open call updates - Index updates - Flickr Foundation intro - Launch new onboarding? ### Notes - FFDW Final Report - andi asked for feedback in a couple places. deadline for this: Fri 13th - ania will double check by EOD - budget: we don't have a surplus, we netted out as expected - Website updates: - Rewriting Services, new copy of the home page + small edits to other pages - https://docs.google.com/document/d/1W7CRkT5beqRwStHeofjjEEYseHubu1aAJCTm4c0mIaI/edit?usp=sharing - Open call updates - Have spanish and english version https://hackmd.io/D9GPj80rQZeT4WII40kBzw - Feeling good about content - Have it as open as possible, once folks apply to a form that's where we'll have more conditions/disclaimers - Friends that looked at framework said this could be in incident response. For websites under attack they publish static versions temporarily while fixing, then go back to dynamic. Need to make it clear we're just recovering websites that have been down for a while, not ones under active attack - Disclaimers such as: Recovery is free of charge but of course grantees would have to cover the domain payment en adelante (can't find the word) - We want to make clear that the website is down, not just under attack, we should filter people who have lost the site temporarily due to attack - Ania workijng on visuals for the campaign - Text is almost finished and form will be up in January? 2nd or 3rd. - Index updates - akhi will push initial implementation tomorrow - we can continue this on January - initial implementation includes API endpoints - Flickr foundation - Ania followed up on introduction offer - Sent out message yesterday, Brynn will help make an intro - Going to see if they're interested in dweb - Launch new onboarding? - Wait for January - This will also allow Andi to update the rest of thw website - Craft action plan with Andi & Ania - Fight for the future - Tried poking KEn but no reply yet - Poke again next week via DM? - Let's try to poke him next week so that we don't lose momentum on what happened recently - Marketing: - Ana can work on a smaller campaign based on the info we have and the initial results for the open call - For marketing strategy, that will need to be by March, otherwise it's too short a time window - Governance for DP - we want to work on this through January ## 2024/12/05 - Weekly Team Sync ### Participants akhi, ania, mauve, fauno ### Agenda - Closing M4 - checking board - Opening M5 - tasks and timeline - Comms: FFF, launch onboarding and Open call for lost sites - Meeting with Patrick - Equality Fund dismissed the proposal - reframing Distributed Mobile Publishing proposal? - FFDW Social Call ### Notes - Closing M4 - https://github.com/orgs/hyphacoop/projects/20/views/1 - fixing staticpub template - default sites to be public, for annoucements and discoverability - dp-cli demo video - register an email, publish to staticpub, then posting to fediverse - dogfooding replies, almost ready in hypha.coop and ready in distributed.press/blog - Starting M5 - index tasks - open call - we should try to boost and retweet this as soon as possible, around Jan 2nd or 3rd - recovery - case studies - initial mkt strategy - we could do a first version of this report that allows us to implement sth during February - and then do a second version that includes the case recoveries for March 3rd - Meeting with Patrick - interested in how publishers can get into the fediverse and bluesky - bridges between fediverse and bluesky - bridgy - created a signal chat with them - staying in touch with them, sending them news, and try to apply to grants with them - not so interested in peer to peer in particular, but they are interested in ActivityPub and the fact that it doesn't have to be crypto - were curious about data portability ## 2024/11/28 - Weekly Team Sync ### Participants Ania, Andi, Mauve, Akhi ### Agenda - **Dogfooding**: Add Social Inbox to DP instead of Hypha - Can we get this set up on Distributed Press site before Wednesday? - **Meeting with Patrick & Peter** - the ask "1: uncensorable content publishing with ease (IPFS etc.), 2. hosting fediverse servers for a news organization, distribution there. Eager to discuss. IF: Internet freedom." - In Progress issues: - website cloning bug - Mauve looking at this - error messaging is not blocking (could we do it next week?) - depends on fauno and Sutty - CLI SDK: we're done - Mauve full fully review and merge in a few hours - Docs.distributed.press - there are some PRs to review and merge - HTML snippet - powered by Distributed Press - New repo staticpub template - trying to figure out why clone API is not working for mauve - will follow up with Akhi async - FFF reshares (see below) - Yearly report - News on M5 - sutty contract - andi to send through - we signed the contract, yeiii! - We'll work on the project board async and have a look at it on Tuesday - Is there money leftover from original grant - still running numbers ### RECAP: Tech - debugging things before next Wed - dogfooding Distributed Press's blog with replies and interactions Business - publish about FFF collab (test hyper and IPNS versions first, draft a text, have it approved by Ken) - prepare for meeting with Patrick and Petr Comms - publish about FFF - prepare campaign for M5 Project - Ania will create M5 milestone and larger issues - send the issues for the team to complete on Monday ## // - Comms Sync ### Participants Andi, Ania ### Agenda - Fight for the Future reshares - 1. how are they using DP exactly? - they used our new cloning tool to create decentralized backup versions of their existing websites - Which sites? https://www.keepkhan.com/ - Has Ken set up the rest of their sites? - 2. what messages should we share? - Ania to draft something and we can discuss - We should link to IPNF and Hyper versions of those sites Action item: Mauve to test this versions first - we can also use Agregore or Peersky to test - Ania or Andi can use the gateway to test the hyper version https://domain-name-com.hyper.hypha.coop/ or there is an IPFS gateway Action items: - follow up with Ken to see if he did the rest of the sites and/or needs help with it - create a message about our work together and supporting FFTF in their mission - https://hackmd.io/2sMafrM9TduJHI8QXHjBAA?view - talk about the values of DP and why we do this important work - Patrick & Peter meeting: the ask "1: uncensorable content publishing with ease (IPFS etc.), 2. hosting fediverse servers for a news organization, distribution there. Eager to discuss. IF: Internet freedom." Action Items: - andi to take a first go at creating a custmized deck based on the last conversation - - Social Inbox opps - Maybe we can get this set up on Distributed Press site? - Can we get this done before Wednesday? - andi to talk to fauno and vincent about social inbx integration this afternoon - New DP site copy edits - FAQ and Pricing texts: https://hackmd.io/su4hIe3iTDqi0Oarc7y-zA - UXDI report ### Notes ## 2024/11/25 - News for FFDW update Highlights from your organization's or initiative's past quarter! We ask for one-two bullets with a max of 2-3 sentences per organization (links are great). This can be anything from a recently launched project or report to a question you’ve been mulling over that you want to discuss with interested parties. Proposed text (Ania): - **Streamlined workflow for Distributed Publishing**: We developed a new user-friendly workflow enabling users to easily distribute a website to IPFS and Hypercore. This included creating a cloning API, automating distribution via a single command, and validating the process with a real-world client, [Fight for the Future](https://www.fightforthefuture.org/). Now, users can effortlessly clone and publish a site to IPFS and Hypercore using just its URL. https://distributed.press/dns-configuration/ - **Enhanced onboarding to the Distributed Web**: Our website underwent a comprehensive redesign to streamline onboarding for new users. We unified all potential use cases of our tools—ranging from creating a distributed site from scratch to distributing an existing one or leveraging our API for further development—into a cohesive and accessible framework. The redesign introduced a “Get Started” section with clear calls to action, including the new workflow for a seamless one-site trial of distributed publishing. Explore Distributed Press 2.0 at [distributed.press](https://distributed.press/get-started). ## 2024/11/21 - Weekly Team Sync ### Participants ania, andi, mauve, akhi ### Agenda - Yearly report: https://docs.google.com/document/d/1I9KDz_seIiykh_CTuDSrILihzQ0oVG64Od090uifmmw/edit?tab=t.0 - Update on documentation, SDK and cloning - Testing onboarding and new site - OTF feedback - M5 timeline - News for FFDW update: we ask for one-two bullets with a max of 2-3 sentences per organization (links are great). This can be anything from a recently launched project or report to a question you’ve been mulling over that you want to discuss with interested parties. Do you have an upcoming event? An open position you’re having difficulty recruiting for? Please share it with the larger community in this quarterly newsletter by sending it to me just before Thanksgiving, EOD Wednesday, November 27th, to ensure they are included" ### Notes - Yearly report: we want to add the "high-level, key outcomes you’d like to share" - checking if they include M3 and M4, or just M4? - replies and interactions in social inbox - **Social Reader:** - - **Randomized Timeline:** Highlights non-chronological content, showcasing custom timelines and exposing users to a wider range of posts. - - **Nested Replies:** Displays replies in a clear, recursive format for easy engagement with conversations. - - **Easy Customization:** Allows users to create community-specific versions by modifying a simple JSON file for default lists and settings. - **DP-CLI:** Creatred a command line utility for interacting with distributed press and social inbox APIs as well as a collection of example commands for developers to get started. Combined with the new "trial account" feature and "cloning" the website, this lets developers get started without additional involvement from the DP dev team. - created an initial script for cloning, validated it is useful with a client (Fight for Future) and then incorporated the cloning/distributing to the Distributed Press API with a simple command that just takes the site URL and performs the clone automatically. - easy onboarding for new users, including all the distributed publishing flows - 1) using Sutty CMS for site creation, 2) cloning/distributing an existing site automatically, and 3) using our API through a token - Improved reliability and performance of the social inbox. We automatically handle Delete requests and are able to send out updates and delete requests to all "interacted users" to ensure stray copies of stale data are addressed. - Changed the startup code in the Distributed Press server to account for the large number of sites we have to re-sync upon boot NEW STUFF! - We should report in the overall project summary that we understood the need to have easy demoing of the service, and thus added this “new deliverable” We created a new workflow for new users to easily try out distributing one website to IPFS and Hypercore. Created an initial script for cloning, validated it with a client (Fight for Future) and then incorporated the cloning/distributing to the Distributed Press API with a simple command that just takes the site URL and performs the clone automatically. Created single-site publisher from email address and developed a clone API. https://github.com/hyphacoop/distributed-press-organizing/issues/198 https://github.com/hyphacoop/distributed-press-organizing/issues/199 - Another expansion of our intial scope was redesigning our site to include an easy onboarding section, pricing and FAQs We enlarged the scope of this deliverable besides documentation and messaging, including a full redesign of the website to create an easy onboarding section for new users with communication strategy and User Experience refined for onboarding visitors. Here we unified all the possible uses of our tools: from creating a site from scratch, to distributing an existent one, to using our API to buld upon. This includes Pricing, FAQs, and a Get started section with clear call to actions. A new workflow was added in this call to actions, that allows an easy “one-site trial” of distributed publishing (see next item) Tasks: UXDI team analyzed the user activities and flows to propose the redesign and prototype it. New visual design and texts for new sections of the site were developed. Distributed Press site version 2.0 available: https://distributed.press/ - Update on documentation, SDK and cloning - Mauve can help with the HTML snippet and also add it the docs - Akhi progressed with CLI and started with templates - Documentation: akhi will add documentation about the CLI after he's done with CLI itself - Testing onboarding and new site: we should schedule a time to test this - Ania and Mauve, Monday - OTF feedback - we talked about censorship a lot - maybe it's too big a job, overly ambicious - sutty could ask remy via email if we interpret their feedback correctly and whether we should re-send a new version of the application ## 2024/11/14 - Weekly Team Sync ### Participants fauno, akhi, mauve, ania, andi ### Agenda - Meeting w/ Brynn - Update for quarterly FFDW call - GitCoin grant - M5 budget - M5 deliverables and smaller tasks - December schedule (time off when?) - Onboarding site status - SDK (cli) update - Replies dogfooding - Cloning issue ### Notes - Onboarding site status: functionalities are done, testing them. Sutty left an issue for Mauve about the API. - We intend to show this to Brynn tomorrow at the meeting, but if we can't make it, it's fine to send it async when it's done - Test site: https://distributed-press-onboarding.testing.sutty.nl/ - Cloning issue: Mauve thinks that there is a problem with the length of the paths, due to spanish characters being converted to unicode and getting larger - We should be able to demo sth with a short URL. - Mauve feels that we should launch the onboarding flow. We could have this as a to-do and solve it while we launch this. - fauno asks about the report that we'd receive when cloning fails - we don't have any notifications about errors, and thus we just see errors when we look at the logs - maybe Elon in January could articulate a few lines and include error reporting CLI updates: - added trial account creation, can publish sites - verification for emails could be important, sending them a verification link - will have social inbox cli by next week - then working on the docs and a short demo - we'll change the tasks ins issue #130: Let developers use the node/react templates instead of creating repositories from scratch with a pre-configured template - for a simpler way that doesn't require to create a repo from scratch Dogfooding replies: FOR HYPHA DRIPLINE - Vincent making slow progress on this - Mauve created an allowlist for replies, which could reduce the amount of moderation - Waiting for the replies to be added to the template - Vincent and fauno already set up a moderation queue - We could get this done before end of November FOR DP SITE - could add this task to the onboarding website? - transition to the new site that includes onboarding - we should check all links - the blog is publishing to the fediverse, it's the section that should have replies - https://distributed.press/blog/ - @distributed@distributed.press M5 budget and deliverables were sent to Brynn this morning Meeting tomorrow will be focused on the agreement for this extension https://docs.google.com/document/d/1DZOzJlygYsPId3Ehtnuh-CKQjxg-c5YN-RWoIAo8JNc/edit?tab=t.0 Are completion dates ok for everyone involved? Index deliverable could be done by February 1st actually Sutty is ok with dates but should start working on the campaign right away in order to have some breathing time We as a team would be starting on January 1st and work Jan and feb, but Sutty could start earlier, on December, with the campaign. Same amount of hours but distributed in more weeks. TO-DO: There might be a surplus of around USD 3k, but Mauve and Andi have to check this In December we would take two weeks off - bill only half a month - Update for quarterly FFDW call We should send updates for the newsletters before Nov 26th (Ania) Gitcoin Grant - apparently we have around 800 USD from Gitcoin grant funding What can we do with this amount? Really tiny Proof of concept - Basic page we can load from a gateway When would the funds be coming through ## 2024/11/07 - Weekly Team Sync ### Participants fauno, akhi, ania, mauve, andi ### Agenda - check-in - tech update - bizdev update - milestone 5 time estimates / budget updates ### Notes -check-in: fauno is travelling next week and still doesn't know some of his plans akhi has everyone around really concerned about the election mauve is thinking about sponsoring it's partner from NY to Canada ania: Cats getting along better, learned from the "cat enchanter". Less open war. #### Tech update - new release in the server with fixes, so that the initial sync happens in the background; we had too many sites for the prior configuration - new DNS API. fauno has to test it - fauno will continue development on the onboarding website after some fixes needed for the backend - akhi: working on the CLI, integrating the trial API so that putting an email gets a token, aiming to fini8sh by last week of nov - who could work in documentation? mauve would start and when akhi is done with CLI, he'll hop i to help with docs #### Bizdev - andi had a meeting with Maria Bustillo and Sebastian from Liccium. there are no immediate opportunities for DP here. - Maria has her own idea about an improvement for libraries - Petr is oficially finished, will remove from chat and turn email int9o redirect - Ania: put together pitch deck, first draft right now. Looked at existing list of contacts. Is it a good time to get in touch with Flickr Foundation? we have skills to move data to the dweb, could talk to see if we can collab - New Public, recreating a more healthy digital civics. They've mentioned DP before. They have a directory, we should get DP in there #### Milestone 5 Need to do a final year report, going to start the process now. Initial deliverables: https://hackmd.io/qSZX26aGT3KX5D0MEKdVOQ Sutty meeting tomorrow to do time estimates. Do we need to figure out what we'll do? Need to estimate tasks and estimates to see what items actually fit in the budget. More time constrained. Can we reduce scope to make constraints realistic? Need to estimate work anyways so we can see what fits. The scope is limited and achievable, what we need to check is if the time fits properly The indexing deliverable has been analized by Mauve Start Dec, 2 week pause, end mid feb Riask factor: Orgs might not get ready in time or reply. Will need time constraint on orgs responsing. 48 hours? Unsure if going over time is an option. ## 2024/11/06 - Grant Extension Meet ### Participants Andi Ania Fauno Mauve ### Agenda Go over what we will do with the extension. ### Notes Should aim to get closer to sustainability with the grant extension. #### Recover and distribute lost sites - Regarding south american activist archiving, will they be paying clients? If not how will we find paying clients? - Initial idea was case studies and success cases. Put out call for X websites and get groups to reach out. WilL get DP with potential sites. With list we can get grants for social impact. Currently have 4-5 case studies, only Anias site is in latin america. Also need a marketing strategy on top of the case study. Distributed protocols aren't a necessity that folks want. However for people that lost their site, being able to recover and distribute it's a powerful case, people can be enthusiastic about the recovery and the added distribution. Will have limitations on which cases we will recover. - Does it make sense in the extension, or would it make sense to double down on something we already did? - Already have option to distribute, have some users, but realizing a need is people losing their sites, preserving via dweb is meeting a use case. Not entirely new. - Is there other polishing we could do? This doesn't need new features, maybe perf adjustments, as is is just publishing sites and making sure the HTTPs certs are fine. There's grants for when websites are being attacked. There's providers that do forensics after the fact, ones that prevent attacks, but the idea is preservation is in between in the area of incident response when a site is lost. There's money to be made. Just need marketing strategy. Demonstrates that we are doing social good. When peopl feel the pain of losing their site, they become great advocates on the importance of preserving and distributing their site. We would be adressing a real need and also creating examples on the benefits of dweb #### Indexing The indexing allows showing off all the sites we've distributed. Agregating from different sources. It also links with the @announcements AP #### Need for another node - LatinAmerican DP backup server? #### ActivityPub? - It's jnot as mature yet - Would be good to stay focused - Could commit to continuing on pitching social inbox and the product offering - Could trump win more folks want to do decentralized social media? Could be opp for non-algorithmic social media. Might be good for pitch deck. - Let's craft a small deliverable around this - In addition to publishing indexer data with HTML, we can incorporate the AP jekyll plugin to also announce sites to the fediverse to help with discoverability #### Hackathons? - seems to be mostly targetting devs, unsure if that's who we will be focusing on enabling - Could be good to dedicate to bounties for security vulns? e.g. "If you find a vuln we can pay X amount". IA was down due to vulns. - It's a good idea but we lack budget, maybe add to backlog, good exposure but lack return - Would be good to put towards labor costs #### Cost breakdown - everyone take half of dec off - take three months to do about 2 months of work total = 2 burn * 2 = total wanted burn = total /2 delta = wanted burn - burn Reduced hours, reduced Andi's hourly rate https://docs.google.com/spreadsheets/d/1zldWklBE_9v2hsyqr7BYcjiIRShy9qC8_od7Ygovxv0/edit?gid=916205450#gid=916205450 TO-DO: - estimate the hours and dedication for the deliverable on indexing - estimate the hours and dedication for the deliverable on recovering sites - estimate the hours and dedication for the deliverable on marketing strategy based on *recovery and preservation* ## 2024/10/31 - Weekly Team Sync Template ### Participants ania, mauve ### Agenda - messaging for gitcoin grant - fast onboarding progress - proposal for grant extension - use cases status: FFF and disco.coop ### Notes Messaging for uncensorable frontends: - Don't need a domain if pubklishing fully p2p - No need for a complex backend - Your application state is mostly on-chain and can be loaded from a wallet - Use any p2p gateway to load your app and connect to a users wallet - Enable offline and mesh network use cases when using p2p enabled browser - Avoid censorship by not having a single point of failure We have p2p publishing tools but the uncensorable frontends folks don't know about this **By having templates to get started with**, we'll help builders to arrive to truly uncensorable frontends. User cases: sex workers, cryptocurrency sutff (we're not fans), go fund me but publish peer to peer- i'm taking donations, send the money here and folks would use a gateway to load the website, the crypto wallet would do the donation - streamlining that process (replaces venmo) The DP API is an API that a dweb app can talk to - you can use DP to publish a new dweb app - fast onboarding progress - fauno added the interactive parts of the website, it's on testing - get a token should show an error if the email is repeated or doesn't exist - uploaded had of the "distribute your website" steps - opened a PR to change sth on the DP backend - once it's reviewed, merged and deployed, the screen will say if DNS config is ok - adding design as well - mauve has been going back and forth abour DNS check - should we move the DNS check to the end? - the problem is that we won't be able to demo as easily :thinking_face: - it requires the client to know how to config their DNS - if you have a trial token from your email, you can only clone 1 website - could we clone the website just from the token? - mauve we'll update the issue with the conclusions of this https://github.com/hyphacoop/distributed-press-organizing/issues/199#issuecomment-2445369276 - we are very close to finishing this - we need to deploy the PR, fauno can try to finish today and mauve deploys, then fauno can continue tomorrow - design needs a few days - distributed.press site is managed by the panel - merging the onboarding code with the current sites code could take more time - subdomain would be try.distributed.press - use cases status: FFF and disco.coop - disco - requested backups and waiting for the wayback machine to be stable enough - FFF - next steps we should do socials posts related, get a testimony, or feedback at least, so we can do socials - proposal for grant extension - schedule an extra meeting next week - last meeting we discussed options (pasting here to have them at hand) :point_down: - use a part of the 20k to recover "lost sites" and get them up on HTTP and Hypercore / IPFS as a part of an **incident response strategy** - also, **have a directory of sites**, pull from DP instances, **make sites more discoverable**. Complements lost sites case. For every site we recover, we can showcase it very simply with a comment from the author. - Should budget some existing activities as part of this not prioritized: - *this option requires more engineering* --> get a **second node** to replicate the data, so we don't rely only on Hypha having a second server --> this could come from a different grant "if only we could set a DP node in South America" - could use funds to cover dev time onboarding new users. - crafting a pitch deck on ActivityPub - budget for working on the UX of CMS - going to hackatons and offering a prize for people to build over our stuff ## 2024/10/24 - Weekly Team Sync Template ### Participants mauve, ania, fauno, akhi ## Agenda - are replies and interactions activated in distributed.press ? hypha site? dogfooding our developments - BD - tech update - grant renewal ### check-in - akhi went for a hike, that was fun - mauve also went for a hike, beautiful colours in the trees - fauno had a small dental incident - ania is ok ## dogfooding replies and interactions in live sites - vincent started with hypha site - crafting an initial allowlist for him - he might need help around the replies stuff - do we need to set up the hooks at Sutty? - can make an empty site and add the private key to it - distributed.press/blog --> using the Jekyll plugin we can show interactions --> remote follows needs JavaScript - fauno can take care of this, will get in touch with Vincent - We can copy replies code from compost template and adjust the styles ### BD - fediverse offering - SHould pitch to folks already interested in the fediverse - another section to educate those that don't know - Will figure out clarifications async - Looked at leads - one or two of those leads need fedi offering to be more developed (i.e. New Public) - Regarding DisCo, starting on site, having issues with wayback machine not being up. Getting there, gonna finish next week. - Also ask DisCo to write a paragraph or less as a **user testimony** on why they find this interesting? - CRM - andi and ania divided responsibilities over these leads - OTF grant - Gitcoin grant - Fight for future - ask if they want to do a report with us? - or a paragraph or less as a **user testimony** on why they find this interesting? - add them in "Examples" at distributed.press - write press release and ask them to post it - their case is also useful for us to adjust details, i.e: imaegs from other domains ## tech update - fauno and mauve met, worked in a way to delete accounts for social inbox - mauve working at cloning code, will have an initial PR today - will have to release a new version of API (higher priority) and social inbox including backfill inboxes and email registration - SDK - question from ania and andi: how will it function? - simple command line, no writing code, no writing project structure *WHY: Right now we have JavaScript and HTTP APIs for using our tools which does not cover all developer use cases (and this means writing code). This will make it easier for developers to get started with integrating Distributed Press in their tools.* - akhi workin on CLI - docs - proposal to add graphics from Figma to docs https://www.figma.com/design/ZeubyQempQfjqflxEtGvOr/Distributed-Press?t=EQLVcmzPAduGHU44-0 - onboarding - issues (194? 130? 162?) ## comms - akhi's social reader blog post being reviewed! - (ania) using more hours for BD instead of comms ## grant extension - Choose a time to meet with Brynn: Nov 4th (11am PST) or 5th (10am PST) or **Friday November 15** (10am PST) - Document to complete ASAP: https://docs.google.com/document/d/1xNjjkxBU3WXOspsUG4bCSpyRr1BkWsQt7XrnbIemLwo/edit?tab=t.0 **IDEAS**: - use a part of the 20k to recover "lost sites" and get them up on HTTP and Hypercore / IPFS - also, have a directory of sites (Mauve's idea, I couldn't take proper notes), puul from DP instances, make sites more discoverable. Complements lost sites case. - budget for working on the UX of CMS - we need a second node to replicate the data, so we don't rely only on Hypha, having a second server --> this could come from a different grant - Could use funds to cover dev time onboarding new users. - crafting a pitch deck on ActivityPub - going to hackatons and offering a prize for people to build over our stuff ## 2024/10/21&23 - Business Development Team Sync ### Participants andi, ania ### Agenda - summarize the fediverse offering - distribute CRM contacts and future steps ### CRM offering - we distributed a few CRM contacts between andi and ania, got to line 21 of the spreadsheet notes from ania: - amazed by the work of **New_Public** - their prototypes have really innovative ideas. wondering how we can articulate DP with them :thinking_face: :rose: - they are currently in phase 3 of their 3 phases "Public Spaces Incubator" a multi-year international partnership. For phase "4" (implementation), they say "Post-PSI; Public service media broadcasters will have access to open source content to implement and scale on their owned platforms" - maybe it's interesting for them to connect with social inbox and have their own platforms also experimenting with fediverse interactions, at this stage? - Petr said: "New_Public- follow-up needed on: Submit DP to their directory and send follow-up email to Sam L" https://newpublic.org/study/3375/digital-spaces-directory - **Rebel mouse** they have a lot of clients at media - typical clients (big and smaller - news/media publishers or company brands) https://www.rebelmouse.com/a-look-at-rebelmouses-media-powerhouse - if we want to continue smoothly, we'd need to find out what happened here "contacted via form with DPress intro and suggested chat about potential partnership (we will speak on Aug8)" --> did Aug 8th happen? couldn't find data anywhere ### Fediverse offering - we'll circle back in the next meeting, wednesday at 10:30 (GMT-3) - worked in the offering at this doc https://docs.google.com/document/d/1TFOzORfdelQyoLFa5MTSvVmXbWnY115TGCz6KMh-DWQ/edit?tab=t.0#heading=h.jxx3oaimbsv - ania will start drafting a pitch deck ## 10/17/2024 - Weekly Team Sync ### Participants andi, akhi, ania, fauno, mauve ### Agenda - checking progress in all areas ## tech: - mauve: you are gonna send your email to DP, we are going to do some validation to see if it's real or not. if it's ok, we'll give you a token for one site, and the account will be marked as "limited" - akhilesh: almost done with the reader stuff, will merge that. Working on blog posts and social media posts for Reader - fauno: making progress in the onboarding website. waiting for news about the token and API to start with front-end. when CMS moderators get notified of flags, we would block websites. pingued mauve on the issue to check what will happen in the social inbox in that case. they'll meet next week and talk about it. ## bizdev: - andi had a meeting with **Pete, Patrick and Petr**, will put her notes here. they were mostly interested in the fediverse pieces! - they have no control over their content distribution, struggling to get their content out there. interested in creating distribution channels that work better - general curiosity about the fediverse, being able to use it without having to run an instance by themselves - interested in working with us and looking for grants! - in 2 weeks: meeting with **Maria from Brick and Popula** - one week after that: meeting **Sebastian from Liccium** - getting **Fight for future** back on track - look at the conversation in collab channel and nudge us towards completion - andi and ania can review the CRM list when they meet and distribute the different contacts - **disco**: Andi/Mauve need to see about whether we can use Hypha's OpenCollective to process the payment. Disco -> OC -> Sutty (via wise) ## Gitcoin grant - Andi will be working in this today and tomorrow - we don't need to make a decision rn, there might be things that we can decide afterwards # Call with Brynn - ## 10/16/2024 - Fediverse 'offering' discussion * Fediverse is a bunch of things we developed this year * Social Inbox and Social Reader are really the core offerings for this * Ania: Federated websites or something similar - this is the key piece * This would exclude the Social Reader * Reader would be a separate piece * Fauno: thinks we can talk about the reader and the inbox together * The possibilities are different * Mauve: it’s going to be hard to split all of these pieces apart * AP stuff: we have an explainer for how to publish to decentralized * There is already brand recognition for DP on the fediverse * Should have done it last year * What is the use case for the Reader? How does it help people who want to interact with the fediverse? * Who would be the users of the social reader? * Not just publishing it to AP but to all the p2p protocols * Having a reader side means that you can use the fediverse without a mastodon account * The consumer side to the publisher side * Proof of concept. Akhi’s work that wants to fork it and edit the follower list * For builders not consumers - useful for other static site publishers but not orgs (social inbox) * Is social inbox specific enough? * Fediverse is more recognizable * Some orgs don’t care what they use; other wants static website specifically for security reasons * If this is the case, then the fediverse work is nice to have * Communications teams likely want some kind of metrics and usage stats for how much the inbox is being used * Security better for static sites * Running social inbox is cheaper * Having your own AP instance is not feasible for most org * **Lightweight alternative to AP implementations** * Find a grant to integrate the reader into the inbox * But also make it possible to register accounts to the reader? * Can transfers instances more easily? * If I want to join the fediverse this would be more straightforward * As a reader, you can just get a link and start reading. * More power in the users hands and cheaper to run for the publishers end * Social inbox isn’t going to make user migrate * But there might be WP users who want to pay sutty to migrate them * Social toolbox for static site: inbox, reader - all part of static sites * Jekyll plugin is for making site activitypub-ifiable Use case: run instances over a mesh network because they can synch offline * Like ssb or smtp * Mesh network * Need to talk about how the fediverse differs from algorithmic social media * A social web that’s more caring * There is less reach but more engagement * This is already the same profile of people we work with ### References * https://fedify.dev/ * https://gotosocial.org/ ## 10/10/2024 - Weekly Team Sync ### Participants andi, akhi, ania, fauno, mauve ### Agenda - check-in - write down (and decide) the conditions and disclaimer on Pricing section - look over the DNS config instructions with fauno - discuss how to organize the hours and tasks for client outreach - review the "needs triage" column - discuss making AP-focused pitch deck - disco.coop pricing ## check-in mauve: McDonalds, but hoping there weren't so many teenagers there akhi: almonds, cashews and walnuts - dark chocolate 100% organic :yum: fauno: his eating habits have changed since travelling, mate and sth nice from san francisco andi: cowgirl cookies, amazing and dense ania: green apple, walnuts and almonds ## review of needs triage column - we go over issues #12 #22 #151 - we need to stick to the timeline and focus on the items on "In Progress" during October and November - maybe consider the priorities of the items on "To-Do" and address only those with High priority - akhi will book a slot on Mauve's calendar to review the tests ## decide the conditions and disclaimer on Pricing section + pricing to disco.coop - Mauve looked at the costs of Hypha's infrastructure - 50 cents per gigabyte - 1 dollar a month per site would be enough - only exception are websites with a heavy usage of video, in that case we should revisit the pricing - labor costs? bugs? - if we have a potential client coming, we should budget each one particularly - disco.coop contacted sutty to recover a website that they lost, will be recovered through wayback machine + WP backups - small website, we were thinking about offering to host in DP - charging 100 usd (?) that comes to DP, for 2 uses: 1. rapairing small bugs or 2. fixing things in our DP backlog - be very clear about the scope of this work for 100usd - be clear about who will be responsible for follow up and mainteinance - Sutty can take the https side of things, in their servers - are we expecting issues from IPFS and Hypercore hosting? nope - potential performace improvements in the future - fight for future - we need to follow-up, poke them a bit and move that conversation - be polite and persistent **FREE STUFF:** - Auto-Onboarding is for publishing the website themselves - that's why it is free - 1 website per email, they can have it posted indefinitely - We can suggest that the website limit is 1 Gigabyte - Mauve will flag websites that are heavier than that in the backend ## Gitcoin grant! - they proactively reached out to us - we have 10 days to send it - andi will look at this and suggest which track is most likely to get funded ## discuss making AP-focused pitch deck - any chance that this aspect of the project could fit into the Gitcoin grant? - find audience / what goal is - Social inbox one pager for dweb camp: https://docs.google.com/document/d/1TFOzORfdelQyoLFa5MTSvVmXbWnY115TGCz6KMh-DWQ/edit?usp=sharing - we should meet next week and work on this - checking if we can do Tuesday 2PM BA / 1PM Toronto - we should review Petr's documents beforehand ## look over the DNS config instructions with fauno and akhi https://github.com/hyphacoop/distributed-press-organizing/issues/196 ## 03/10/2024 - Weekly Team Sync ### Participants ### Agenda - check-in - fast onboarding prototype and text - Brynn's feedback to pitch deck - September progress report for FFDW - Quick recap from meeting w/ Petr - CRM follow up ### Notes check-in: - fauno shared the experience in Ecuador at Escuela Común - akhilesh got a huge TV from fb market, using it as a monitor - mauve has been kind of sick, they took the day off yersterday. has to give asthma medication to their cat :/ - andi went to see an author doing some kind of stand up comedy, was nice - ania: running and went to a fun wedding ### September progress report for FFDW we are updating the issue: https://github.com/hyphacoop/distributed-press-organizing/issues/175 ### Brynn's feedback to pitch deck - good questions about the services - simple suggestions like adding a contact From Brynn: - *In the 'reduce link rot and eliminate 404 errors', you state that IPFS "does not depend on specific servers being availible" -- that's not true, someone still needs to be pinning the file to make sure it's availible on the network, and my understanding is that the Distributed Press server pins the content to a local IPFS node run by Hypha.* - How to change the copy to be more accurate? - "as long as someone has a copy of the data." We're exploring the idea of social pinning or pathways of changing stewardship without changing links - if enough people care about the longevity of the data, there is less of a single point of failure. more control in the hands of people - social seeding - integrate with ceno browser and libresilient - *For a lot of the claims around hosting and long term storage and linkrot prevention, I'd like to know more about who you are partnering with to run nodes and/or host the content in a distributed way. Is it just Hypha running these nodes? If so, you may run into much of the same disbelief the Filecoin / IPFS ecosystem runs into (i.e. we haven't been around long enough to believably claim we're better for long term preservation).* - tor exit nodes or relays; everyone can host one, but we are developing relatioships with organizations who are interested in hosting these nodes?? - - I would also add that the censorship resistance market is relatively small, and often doesn't have a lot of money (it's mostly activists and journalists), so I am not sure how valuable that is as a value proposition. The social inbox/federated angle seems much more compelling and novel, and there are lots of companies who are trying to figure out how to engage with the Fediverse and don't really know how. They'd be great customers of Distributed Press. - we have to go through Petr's handoff documents and then decide if - we should include this in the same pitch deck - package, or - we should create a second pitch specifically for Fediverse and Social Inbox - we can reply Brynn that we are thinking about this already, that this was an intentional "simplification" but... ### Petr's handoff There are a few documents we have to look at. There's a summary of the handoff here: https://docs.google.com/document/d/1j25Amq4M_Tv83-zh6ycXgJteiHrap8kSUZkafYDsAhQ/edit Folder of all biz dev materials are here: https://drive.google.com/drive/folders/1_GOip3katnNqFg-OJ85f4cxeXx3d7Phz?usp=drive_link Final report: https://docs.google.com/document/d/1H6Ho4zlcLxFuYYjkC2-0KgYZwEdXEkc05oNucgu5cFQ/edit#heading=h.30yhvnbqctfx Landscape document: https://docs.google.com/document/d/1H6Ho4zlcLxFuYYjkC2-0KgYZwEdXEkc05oNucgu5cFQ/edit#heading=h.30yhvnbqctfx CRM contacs follow up - we have to look at the tech roadmap to see how much time we have left or can squeeze for Customer Relations and calls - Mauve and Ania will meet next week to do this - Stacco from disco.coop want to recover a website, this is paid work and includes DP, fauno will lead this and ping us on Zulip - - IPFS pinning - none of them support mutable content - nothing pins across all protocols - if we want to have tools for people to pin we have to build them - Reader - can be used as an aggregator for orgs with many accounts (?) - Akhi to write a blog post about how this can be used and who it's for - ## 19/09/2024 - Weekly Team Sync ### Participants mauve, ania, akhi, andi ### Agenda - check-ins - board check - fast onboarding progress - tech checkin - bizdev follow-up - Theory of change discussion ### Notes -check-in: mauve is going to toronto next week and has trouble with rust akhi wants to learn surf andi surfed in a few different places, really loved training for it ania adorable but naughty kitten issues; also maybe internet issues ### tech checkin - Mauve: hasn't progressed with clone integration. Adding it to DP API early October - Akhi: performance issue fix. Working in the JSON export ### fast onboarding - add in UI: asking for their email before the DNS setup DISCLAIMER about not using their emails for anything but user communication. Akhilesh dice: if we decide to show them on the website. even for stats. - collecting emails, and what to do about them? ### bizdev - reschedule meeting for hand over - look for further grants in October - ### Theory of change discussion Andi can start working on a template to start discussing this. Shaping what we have in the form ofa theory of chaneg ### Social media posts

Syntax	Example	Reference
# Header	Header	基本排版
- Unordered List	Unordered List
1. Ordered List	Ordered List
- [ ] Todo List	Todo List
> Blockquote	Blockquote
Bold font	Bold font
Italics font	Italics font
~~Strikethrough~~	~~Strikethrough~~
19^th^	19^th
H~2~O	H₂O
++Inserted text++	Inserted text
==Marked text==	Marked text
[link text](https:// "title")	Link
![image alt](https:// "title")	Image
`Code`	`Code`	在筆記中貼入程式碼
```javascript var i = 0; ```	`var i = 0;`
:smile:		Emoji list
{%youtube youtube_id %}	Externals
$L^aT_eX$	L^aT_eX
:::info This is a alert area. :::	This is a alert area.