home.social

#fedicon — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fedicon, aggregated by home.social.

fetched live
  1. Much like the work that goes into the protocols and software behind the web, most people don’t know about trust and safety—including the harms that exist and the tools to combat them.

    We attended FOSSY to chat with, learn from, and help educate fellow open source developers.

    #FOSSY #FediCon

    T&S Across the Fediverse: ROOS...

  2. Much like the work that goes into the protocols and software that power the open social web, most people don’t know about the field of trust and safety—including the harms that exist for every platform and the tools that are developed to combat them.

    We attended FediCon and FOSSY to chat with, learn from, and help educate the open source developers building the fediverse, and to find ways our open source tools can help keep people safe across platforms.

    roost.tools/blog/trust-safety-

    #FOSSY #FediCon

  3. Avoid explaining “the fediverse” in a blog post challenge (impossible) 🙈

    As long as we’re writing up a post-FediCon blog post, @cassidy felt like we kind of *had* to at least introduce the term that the conference was named after. How did he do?

    > “Fediverse” is a community-coined term that refers to an open social network made up of thousands of interoperable sites and services built with many different software platforms, but all on the ActivityPub protocol. Platforms like Mastodon, Pixelfed, Loops, WriteFreely, Bandwagon, Bookwyrm, Lemmy, Flipboard, Threads, Ghost, WordPress, Discourse, and many more are part of the fediverse; millions of people using these platforms can find, follow, and interact with people and content across the entire network.

    Keep in mind the audience of this blog post is going to skew a bit technical; it’s a post-conference recap of a track at FOSSY, after all! We don’t recommend introducing the idea of the fediverse this way to your friends and neighbors. 😅

    #FOSSY #FediCon

  4. I was thinking about the talk @evan gave at #fedicon. One point brought up was fedi users don't stay fedi users very long. They get an account, but the account goes inactive not too long after signing up.

    iirc a large factor in this is they don't have anyone to follow. I was talking to someone with a different reason; they didn't get notifications on their iPhone, only to their email.

    I do wonder how many people are lost to UI problems we don't even know about. Really difficult problem.

  5. Hot take: naming doesn’t matter. The term “fediverse” is goofy and nerdy *and fine, actually.*

    You use the “Internet” every day. “Email” is ubiquitous. We install “apps” on “phones.” You ask for the “Wi-Fi password.” These are all goofy names, yet nobody bats an eye.

    What we call something doesn’t factor into its adoption as much as nerds would have you think. But arguing about naming is easier than doing all of the *other* work required for adoption.

    #FediCon #fediverse #OpenSource

  6. I may admit, I discussed mysql vs postgres at #FediCon a lot, it kinda went like this:

    "one does not simply have problems with mysql

    its uptime is guarded by more than just replicas. there is an innodb there that does not sleep, and the great eye of postgres is ever watchful. mostly watching its own autovacuum

    pixelfed, loops and writefreely chose the path of peace.

    zero incidents.

    we simply do not know what downtime is"

    @matt 🤣

  7. One thing that stood out at #FediCon was hearing devs mention seeing @evan at conference after conference.

    I can’t think of a better ambassador for the fediverse than the person who started it nearly 20 years ago.

    From @swf and #SWICG to supporting E2EE work with @Bonfire, @benpate and more, Evan keeps showing up.

    That kind of long-term stewardship matters. ❤️

  8. I guess I really should write up a blog post about my experience at #FediCon for @roost, huh. I have so many thoughts!

  9. If you posted about us or T&S at #FediCon, prepare yourself for ROOST to BOOST your TOOTS

  10. If you were at #fedicon, and we talked, and I haven't followed you yet reply here so I can. I know I'm missing at least two people, but knowing your faces and what we talked about isn't enough for me to find you with search.

  11. I got a bunch of swag from #FediCon, including this @roost keychain from @cassidy

    Really looking forward to adding support for Roost in Loops and Pixelfed 🚀

  12. FediCon panel:

    @ozoned: "what do you think the max hashtags per post should be: 3, 5, or 60?"

    @mapache: 3
    @matt: 5
    @benpate: 60

    me, already halfway out of my seat: 61

    *announcer voice* DANSUP, COME ON DOWN

    (this actually happened)

    #FediCon

  13. My favourite slide from my FediCon talk about Loops was the very last one I added at 3am the night before my talk.

    "Someone hears about a thing, they go to sign up, and the first screen asks them to choose a server. And they don't know what a server is. They don't know what any of these words mean, and they've now been asked to make an infrastructure decision before they've seen a single video. Most of them just leave"

    #Loops #FediCon

  14. RE: floss.social/@karen/1170724829

    Yay!! I hope to see all you nerds somewhere in less than a year, but if all else fails, see you back here next year!

    #FOSSY #FediCon

  15. 5/ In my mind those are the main barriers to fediverse growth. Everything else is a kludge or a work around. #FediCon

  16. 4/ The next most important barrier to fediverse growth is the ever present elephant in the room: money. Most of us run instances on a shoe string for our own gratification and the benefit of others, but unfortunately that's not a recipe for growth. If you want to address growth you need to look at how to generate funding and that conversation ends up at sponsorship. How doe we navigate that responsibly? It's a question nobody asks and everyone should be if we're talking about growth. #Fedicon

  17. 3/ So our brand at the Canadian is obviously Canada, a home for Canadian users much like mtdn.ca. Gander is our main commercial competition and they're eating our lucnh, why? Because they have a brand, they have an app and they have a cohesive message to the user. Meanwhile we're still explaining what an instance is. That just doesn't work and sadly it never will, at least not for growing the fediverse #FediCon

  18. 2/ The response to where do I download the app is usually a confusing explanation about various choices and you've lost them almost 100% of the time. We need to start building instances with their own brand differentiators and apps. Establish that and then one of your competitive edges is that you can access users from all these other great platforms as well. In an ideal world I'd say you should check out or social media site The Canadian, here's where you download the branded app #FediCon

  19. 1/ Didn't have a chance to go to #FediCon this year, however it looks like the driving question is the same as last year: how do we grow the fediverse? My answer is to stop treating the fediverse as the product, it's not. The fediverse is the engine on which you build a community. The secret sauce is that you can connect those communities together.
    When you say to someone, you should join the fediverse, whats the immediate response? Where can I download the app? How do you respond?

  20. Thank you every at #fossy and #fedicon. I have never been to a conference like this before and had an absolute blast. Met so many nice and awesome people, far too many to list and count.

    Hope to make next year!

  21. Okay! @benpate @ozoned @matt and anyone else at #FOSSY ( #FediCon day 3? ) who would like to look at Coop from @roost and poke around/hack on things: let’s congregate near the registration desk in the Fred Kaiser building after this session, around 3 PM! I can show it a bit and then dig into how to deploy/integrate w/it.