# Distibuted Press - mauve/mai 1:1 ####### tags: `distributed press` ## Meeting 21 Mar 2024 ### Agenda * Biannual report * My role next 6 months ## Meeting 14 Mar 2024 ### Agenda * Milestone 4 * Moderation * Changed relationship to content discoverability * Reader is reader first, publishing is separate * It's closer to blogosphere, not social media * Just reading now as of M3, no moderation * Tipping + Monetization * Crypto payments: USDT, * Use existing specs: zap and Nostr, Matters * Tipping and paying for premium content * Tap into existing communities * "We're re-evaluating our fourth milestones and will contact your team in the next 2 weeks" ## Meeting 22 Feb 2024 ### Agenda * Finalize product offering doc: https://hackmd.io/GL376L6FRGKc0IHkSuzNfw?both * FFDW meetings ### Notes * Sutty * Ania with product management * Nula with JS work * CMS may not be appropriate for every case * Best parts were relying on executing on tasks * ## Meeting 15 Feb 2024 ### Agenda * Fediverse bridges ### Notes * Pro bridging, opt-out isn’t great * Bluesky has a different culture, it’s corporate * Mauve likes the bridge bc they don’t want to use the apps * All for people protecting themselves against harsh environments * Just bc its public, doesn’t mean they should waive away privacy or safety * Tech company shouldn’t blame users, Fediverse isn’t safe by default * People assume some level of safety or rights from their services, but many of are misled * “Feelings don’t care about facts” * Bridging for the sake of bridging is dangerous * Exposing people to the dangers of corporate systems * Make people make angry, control what info people have access to * All for money * Bridging invites these demons * Bluesky’s data model privileges blue sky * Accountability comes with centralization * Libertarian, free speech * Trying to get everyone on their platform * Federation stuff their doing is centralized * It requires large services, with index servers * Federating with Bluesky is useful to getting normie demographic in * People love or hate fediverse * You can have multiple identities in different instances/communities * Paths from large low context communities * Groups across federated instances, on Lemmy client and server * Will decentralize where communities live, instead of just your instance * Client-server protocol in the Fediverse * Mastodon has their own custim API to interact with the network * Move more logic to the client side, to have more robust client work across implemtneations * How to follow * Global timeline on Mastodon >> great way to be exposed to hate * Local timelines * Hashtags * Server is indexing data: posts, boosts, replies, etc. * Based on your social graph * Large instances, is where context breaks down * Higher context, higher social graph >> less anger * Mastodon * Giant database, instance database, based on who you follow * Grab bag of what is shared between * One large database index based on weird rules, on demand * Receives info, pushed to it, not pulling it * DP Reader * Personal data base, pulling data, personal data instead of community inbox * Exposed if someone on a large instance follows you * Risk is lower if others who you interact with are also using it, having a personal inbox * New physics for how this work * Curation be valued * Pay curators to find content * Ex. Mastodon.art - curating info feed * High social context list of information * Discoverability of people just boosting stuff * SSB: inboxes, send a message to someone even if you’re not familiar with them * But load them because you have some level of social connection * Changing the signal to noise ratio * Changing what you see / WHERE it’s saved, changes how you interact with or see what else is on the network * >> Expense is lower reach * Ex. BBC: More engagement, bc of higher context but fewer followers * Bluesky * Physics of it is not great because it’s based on engagement * Trade offs: how to make different algos for analyzing things, market around AI curation or maybe just a timeline * Prioritizes for lower social context * The more you aggregate the more weak and dangerous it is * People with more privilege, can cause more harm and get aware with it * Needs * CURATION * HIGH LEVEL LISTS * SOCIAL DISCOVERY * Handle shared through talks * Follow based on interesting article * READER IS JUST A READER * Being shown random shit to test engagement level is necessary for corpos * >> OPT-OUT vs. OPT-IN bridges * READ VS. WRITE * Gaze into the abyss vs. the abyss gazes at you back ## Meeting 1 Feb 2024 ### Agenda * Team dynamic reflection * Product offering planning * Opportunities: https://github.com/orgs/hyphacoop/projects/20?pane=issue&itemId=50450847 * Mai: create template email for outreach * Have team review for context * Product offering page draft: https://hackmd.io/GL376L6FRGKc0IHkSuzNfw?edit * ## Meeting 18 Jan 2024 ### Agenda * Product offering planning * Opportunities: https://github.com/orgs/hyphacoop/projects/20?pane=issue&itemId=50450847 * Mai: create template email for outreach * Have team review for context * Pricing? https://github.com/hyphacoop/distributed-press-organizing/issues/81 * Fediverse/threads piece * Distributed Press docs? * https://docs.distributed.press/ * https://github.com/hyphacoop/distributed-press-organizing/issues/99 * mai's hours ### Notes * Product offering planning * Opportunities: https://github.com/orgs/hyphacoop/projects/20?pane=issue&itemId=50450847 * Pricing? https://github.com/hyphacoop/distributed-press-organizing/issues/81 * >> Put in the back burner * Offering page * Live in the DP docs and the DP landing page * Out of the box services * "We do cool shit, hire us to do cool shit for you" * Describe the tools we have, then suggest areas where we can do customizations for others * Let us make new tools and customize them for your use case * Showcase what we can work with, the areas, then customize * Rope in Sutty, if you want a site published, or web design * Would they be down to do DP integration for other CMS's? * To Do: Create place to draft this * Fediverse/threads piece * Accounts -- look at their official statements * social.coop admin mods * miro match * coop.social, mastodon.social, mastodon.art, neuromatch.social, friend.camp * Roe? * leads [badspace](https://tweaking.thebad.space/), talks about moderation, comes at it from anti-racism and safety * https://roiskinda.cool/profile.html * https://mastodon.mauve.moe/web/@Are0h@ubiqueros.com * Angle * FB and IG as a rage machine, and engagement * People constantly nagry * People who don't Fediblock threads, they could open themselves up to that * Even iftheir timeline isn't doing that, people on the threads side could happen * FB's model is not aligned with safety or mental comfort * White supremacy, neo-nazis on social media * They don't get moderated that well * On Fediverse, it s aproblem but you can block instances * On Threads, with amount of each, it's unviable to create individal block lists * Privacy angle * Payment and relationship with mdoerations and server admins * >> Big copros exploit free services >> anger machine * >> Send pitch to Brynn + Jordan * Distributed Press docs? * https://docs.distributed.press/ * https://github.com/hyphacoop/distributed-press-organizing/issues/99 * mai's hours * Grants * OTF - Resilience + privacy: DP and Agregore * Internet Freedom Fund: https://apply.opentech.fund/internet-freedom-fund-concept-note/ * Mauve has connect with OTF * ## Meeting 4 Jan 2024 ### Agenda * Checkin * Comms ### Notes * Comms * Articles/writing * Fediverse integration with Threads: hopes + concerns * ActivityPub client and p2p extension: dweb protocls with the Fediverse? * >> Audience * Fediverse people, potential funders, dweb community, advertising our expertise in our tech for custom uses (B2B - Fedi products consultation, modular tech) * Focus on bringing in new people: Funders, contractors, users * FFDW distribution channel * Get a piece on Wired or other channels where they can spread us * An article not targeted in people in the know, bring new people in * Consulting services * Need landing page that advertises our services * Expertise: Federated social, AP, etc. * https://github.com/hyphacoop/organizing-private/issues/360 * Brainstorm! * "Save on infrastructure cost and developer time" * Cost savings and reliability * Inspo * Keet - Hypercore/DAT folks * Ditto TO DOs * Connect with Luandro * Schedule a meeting dweb/art/local first team re: COMPOST * Schedule meeting with Mauve re: fediverse/threads integration piece ## Meeting 30 Nov 2023 ### Agenda * compost news redirect * on the sutty site * review announcement post once more * add link to sutty's blog: https://dweb.sutty.nl/ * video upload? * Hypha Youtube For Mastodon users: Please note that when you follow an account for the first time from your instance, you will be receiving new posts as they're published. However, you will not see any previous posts due to Mastodon not preemptively fetching the full lists of posts from our outbox. If this something you'd like to be addressed, comment on the [Mastodon issue tracker](https://github.com/mastodon/mastodon/issues/34), or work with us in [our issue tracker](???) to see what you can do to help. * Who are we targeting? * Leads for groups who want to publish to dweb * Static publishing pipelines * People who want to do new magazines want customizable stuff anyway * Things can be glossed over with relations * Happy path isn't working any time * How to communicate with Brynn / FFDW * Success story for their portfolio * Brynn: Make the community happen and keep projects going Considerations * FFDW milestone deliverables * COMPOST release and contributor participation Release * Rolling release * 1 - Github action * Docs are published but needs review * Andi? * Reach out to FFDW groups * DP site build needs to be fixed * Strip down the DP landing page * Landing page to point to docs site * CONTACT US at the very top * Static site published >> any data available on the protocols * Pricing for onboarding work * $1-2 K for each onboarding * Scope it - effort for them to do it vs. using our tools vs. us doing it * Save money and achieve goals that you'd have a hard time doing otherwise * TO DOs * Scope of the product - tasks -- (self-hosted vs. we hosted), level of data, support contracts (how much automated, availability to debug); one-time set-up, call us for support * Pricing * PROMOTION * Uber hackers who can set it up themselves * Everyone else talks to us for set up * 2 - Sutty CMS * Soft release, it can be used to publish to DP but needs onboarding at the moment * Needs to be hands on, get feedback directly * VERY prominent place for feedback * Contact us for deployment or follow it yourself, might be hard and please give us feedback TO DOs * Add this to do to prod release Github * Scope of the product - tasks -- (self-hosted vs. we hosted), level of data, support contracts (how much automated, availability to debug); one-time set-up, call us for support * Price out services and review by Hypha * Finalize review of docs page * Draft an email to FFDW laying out our plans * Discuss on Thursday April 12 all-hands * Review Sutty CMS publishing from start to finish with UX feedback