home.social

#swicg — Public Fediverse posts

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

fetched live
  1. 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. ❤️

  2. 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. ❤️

  3. 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. ❤️

  4. 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. ❤️

  5. 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. ❤️

  6. @Edent nice article!

    I notice you didn't mention as:Place in #ActivityStreams vocab. In your previous article you mentioned "there is good news and bad news" around as:Place, and I deduced the bad news was that Mastodon didn't support it.

    Regarding the #SWICG #GeoSocial task force proposal, you wrote:

    > The primary thing missing from the proposal is any form of understanding what users want to do with a geotagged post.

    In both the observation on Mastodon support and mention of a geotagged *post* there's an implicit assumption on the application domains this pertains to: (micro)blogging social media.

    I gather that the range of business/app domains that may have geosocial capabilities is much broader than that. And while a list of generic use cases can be brainstormed for support, things will be quite solution-specific. And the TF perhaps better provide good guidance and building blocks for that.

    Broader question is whether fedi is already tied shut in a microblogging straitjacket.

  7. @Edent nice article!

    I notice you didn't mention as:Place in #ActivityStreams vocab. In your previous article you mentioned "there is good news and bad news" around as:Place, and I deduced the bad news was that Mastodon didn't support it.

    Regarding the #SWICG #GeoSocial task force proposal, you wrote:

    > The primary thing missing from the proposal is any form of understanding what users want to do with a geotagged post.

    In both the observation on Mastodon support and mention of a geotagged *post* there's an implicit assumption on the application domains this pertains to: (micro)blogging social media.

    I gather that the range of business/app domains that may have geosocial capabilities is much broader than that. And while a list of generic use cases can be brainstormed for support, things will be quite solution-specific. And the TF perhaps better provide good guidance and building blocks for that.

    Broader question is whether fedi is already tied shut in a microblogging straitjacket.

  8. @Edent nice article!

    I notice you didn't mention as:Place in #ActivityStreams vocab. In your previous article you mentioned "there is good news and bad news" around as:Place, and I deduced the bad news was that Mastodon didn't support it.

    Regarding the #SWICG #GeoSocial task force proposal, you wrote:

    > The primary thing missing from the proposal is any form of understanding what users want to do with a geotagged post.

    In both the observation on Mastodon support and mention of a geotagged *post* there's an implicit assumption on the application domains this pertains to: (micro)blogging social media.

    I gather that the range of business/app domains that may have geosocial capabilities is much broader than that. And while a list of generic use cases can be brainstormed for support, things will be quite solution-specific. And the TF perhaps better provide good guidance and building blocks for that.

    Broader question is whether fedi is already tied shut in a microblogging straitjacket.

  9. @Edent nice article!

    I notice you didn't mention as:Place in #ActivityStreams vocab. In your previous article you mentioned "there is good news and bad news" around as:Place, and I deduced the bad news was that Mastodon didn't support it.

    Regarding the #SWICG #GeoSocial task force proposal, you wrote:

    > The primary thing missing from the proposal is any form of understanding what users want to do with a geotagged post.

    In both the observation on Mastodon support and mention of a geotagged *post* there's an implicit assumption on the application domains this pertains to: (micro)blogging social media.

    I gather that the range of business/app domains that may have geosocial capabilities is much broader than that. And while a list of generic use cases can be brainstormed for support, things will be quite solution-specific. And the TF perhaps better provide good guidance and building blocks for that.

    Broader question is whether fedi is already tied shut in a microblogging straitjacket.

  10. @Edent nice article!

    I notice you didn't mention as:Place in #ActivityStreams vocab. In your previous article you mentioned "there is good news and bad news" around as:Place, and I deduced the bad news was that Mastodon didn't support it.

    Regarding the #SWICG #GeoSocial task force proposal, you wrote:

    > The primary thing missing from the proposal is any form of understanding what users want to do with a geotagged post.

    In both the observation on Mastodon support and mention of a geotagged *post* there's an implicit assumption on the application domains this pertains to: (micro)blogging social media.

    I gather that the range of business/app domains that may have geosocial capabilities is much broader than that. And while a list of generic use cases can be brainstormed for support, things will be quite solution-specific. And the TF perhaps better provide good guidance and building blocks for that.

    Broader question is whether fedi is already tied shut in a microblogging straitjacket.

  11. @blog Insightful post. People in the SWICG geosocial task force are trying to turn your third strategy's hope into help. We’re writing explainer docs for implementing specific user stories, which has instigated work on a few related missing pieces to make federated Foursquare possible. It’s gonna happen!

    github.com/swicg/geosocial/

    #SWICG #GeoSocialTF

  12. @blog Insightful post. People in the SWICG geosocial task force are trying to turn your third strategy's hope into help. We’re writing explainer docs for implementing specific user stories, which has instigated work on a few related missing pieces to make federated Foursquare possible. It’s gonna happen!

    github.com/swicg/geosocial/

    #SWICG #GeoSocialTF

  13. @blog Insightful post. People in the SWICG geosocial task force are trying to turn your third strategy's hope into help. We’re writing explainer docs for implementing specific user stories, which has instigated work on a few related missing pieces to make federated Foursquare possible. It’s gonna happen!

    github.com/swicg/geosocial/

    #SWICG #GeoSocialTF

  14. @blog Insightful post. People in the SWICG geosocial task force are trying to turn your third strategy's hope into help. We’re writing explainer docs for implementing specific user stories, which has instigated work on a few related missing pieces to make federated Foursquare possible. It’s gonna happen!

    github.com/swicg/geosocial/

    #SWICG #GeoSocialTF

  15. @blog Insightful post. People in the SWICG geosocial task force are trying to turn your third strategy's hope into help. We’re writing explainer docs for implementing specific user stories, which has instigated work on a few related missing pieces to make federated Foursquare possible. It’s gonna happen!

    github.com/swicg/geosocial/

    #SWICG #GeoSocialTF

  16. Notes from the 2026-04-09 #SWICG #GeosocialTF meeting:

    - @herebox update on geosocial work presented at AT Protocol Atmosphere conference
    - @evan microsyntax for location doc PR
    - FediForum session planning

    hedgedoc.socialweb.coop/s/L0a0

    Next meeting: 2026-05-14

    Agenda: github.com/swicg/geosocial/wik

    #fediDevs

  17. Notes from the 2026-04-09 #SWICG #GeosocialTF meeting:

    - @herebox update on geosocial work presented at AT Protocol Atmosphere conference
    - @evan microsyntax for location doc PR
    - FediForum session planning

    hedgedoc.socialweb.coop/s/L0a0

    Next meeting: 2026-05-14

    Agenda: github.com/swicg/geosocial/wik

    #fediDevs

  18. Notes from the 2026-04-09 #SWICG #GeosocialTF meeting:

    - @herebox update on geosocial work presented at AT Protocol Atmosphere conference
    - @evan microsyntax for location doc PR
    - FediForum session planning

    hedgedoc.socialweb.coop/s/L0a0

    Next meeting: 2026-05-14

    Agenda: github.com/swicg/geosocial/wik

    #fediDevs

  19. Notes from the 2026-04-09 #SWICG #GeosocialTF meeting:

    - @herebox update on geosocial work presented at AT Protocol Atmosphere conference
    - @evan microsyntax for location doc PR
    - FediForum session planning

    hedgedoc.socialweb.coop/s/L0a0

    Next meeting: 2026-05-14

    Agenda: github.com/swicg/geosocial/wik

    #fediDevs

  20. Notes from the 2026-04-09 #SWICG #GeosocialTF meeting:

    - @herebox update on geosocial work presented at AT Protocol Atmosphere conference
    - @evan microsyntax for location doc PR
    - FediForum session planning

    hedgedoc.socialweb.coop/s/L0a0

    Next meeting: 2026-05-14

    Agenda: github.com/swicg/geosocial/wik

    #fediDevs

  21. Notes from the 2026-03-12 #SWICG #GeoSocialTF meeting:

    - First draft of explainer doc merged: github.com/swicg/geosocial/blo
    - Starting of validation implementation of Places OrderedCollection proposal
    - Starting microsyntax proposal for location without server-side support

    hedgedoc.socialweb.coop/s/QyKM

    #fediDevs

  22. Notes from the 2026-03-12 #SWICG #GeoSocialTF meeting:

    - First draft of explainer doc merged: github.com/swicg/geosocial/blo
    - Starting of validation implementation of Places OrderedCollection proposal
    - Starting microsyntax proposal for location without server-side support

    hedgedoc.socialweb.coop/s/QyKM

    #fediDevs

  23. Notes from the 2026-03-12 #SWICG #GeoSocialTF meeting:

    - First draft of explainer doc merged: github.com/swicg/geosocial/blo
    - Starting of validation implementation of Places OrderedCollection proposal
    - Starting microsyntax proposal for location without server-side support

    hedgedoc.socialweb.coop/s/QyKM

    #fediDevs

  24. Notes from the 2026-03-12 #SWICG #GeoSocialTF meeting:

    - First draft of explainer doc merged: github.com/swicg/geosocial/blo
    - Starting of validation implementation of Places OrderedCollection proposal
    - Starting microsyntax proposal for location without server-side support

    hedgedoc.socialweb.coop/s/QyKM

    #fediDevs

  25. Notes from the 2026-03-12 #SWICG #GeoSocialTF meeting:

    - First draft of explainer doc merged: github.com/swicg/geosocial/blo
    - Starting of validation implementation of Places OrderedCollection proposal
    - Starting microsyntax proposal for location without server-side support

    hedgedoc.socialweb.coop/s/QyKM

    #fediDevs

  26. Notes from the 2026-01-08 #SWICG #GeoSocialTF meeting:

    - @evan’s Personal Places API proposal
    - Discussion of how an overlapping W3C Community Group and Working Group might function
    - The FOSDEM Social Web track is going to be even more awesome this year

    hedgedoc.socialweb.coop/s/ME48

  27. Notes from the 2026-01-08 #SWICG #GeoSocialTF meeting:

    - @evan’s Personal Places API proposal
    - Discussion of how an overlapping W3C Community Group and Working Group might function
    - The FOSDEM Social Web track is going to be even more awesome this year

    hedgedoc.socialweb.coop/s/ME48

  28. Notes from the 2026-01-08 #SWICG #GeoSocialTF meeting:

    - @evan’s Personal Places API proposal
    - Discussion of how an overlapping W3C Community Group and Working Group might function
    - The FOSDEM Social Web track is going to be even more awesome this year

    hedgedoc.socialweb.coop/s/ME48

  29. Notes from the 2026-01-08 #SWICG #GeoSocialTF meeting:

    - @evan’s Personal Places API proposal
    - Discussion of how an overlapping W3C Community Group and Working Group might function
    - The FOSDEM Social Web track is going to be even more awesome this year

    hedgedoc.socialweb.coop/s/ME48

  30. Notes from the 2026-01-08 #SWICG #GeoSocialTF meeting:

    - @evan’s Personal Places API proposal
    - Discussion of how an overlapping W3C Community Group and Working Group might function
    - The FOSDEM Social Web track is going to be even more awesome this year

    hedgedoc.socialweb.coop/s/ME48

  31. The monthly SWICG GeoSocial Task Force meeting is about to start if you have thoughts on location data use cases and the social web.

    w3.org/events/meetings/ed630a3

    #geoSocial #GeoSocialTF #SWICG

  32. The monthly SWICG GeoSocial Task Force meeting is about to start if you have thoughts on location data use cases and the social web.

    w3.org/events/meetings/ed630a3

    #geoSocial #GeoSocialTF #SWICG

  33. The monthly SWICG GeoSocial Task Force meeting is about to start if you have thoughts on location data use cases and the social web.

    w3.org/events/meetings/ed630a3

    #geoSocial #GeoSocialTF #SWICG

  34. The monthly SWICG GeoSocial Task Force meeting is about to start if you have thoughts on location data use cases and the social web.

    w3.org/events/meetings/ed630a3

    #geoSocial #GeoSocialTF #SWICG

  35. The monthly SWICG GeoSocial Task Force meeting is about to start if you have thoughts on location data use cases and the social web.

    w3.org/events/meetings/ed630a3

    #geoSocial #GeoSocialTF #SWICG

  36. How's the #SWICG "Activitypub and AT Protocol Discourse statement" going, anyway...?

    https://github.com/swicg/general/pull/48

  37. How's the #SWICG "Activitypub and AT Protocol Discourse statement" going, anyway...?

    https://github.com/swicg/general/pull/48

  38. How's the #SWICG "Activitypub and AT Protocol Discourse statement" going, anyway...?

    https://github.com/swicg/general/pull/48

  39. How's the #SWICG "Activitypub and AT Protocol Discourse statement" going, anyway...?

    https://github.com/swicg/general/pull/48

  40. @ophiocephalic

    Ah yes...

    Mr #EvanProdromou

    Or Mr #MaxiFedi as I like to call him

    Willing to concede anything to expand his universe infinitely, consequences be damned

    #Mastodon #Meta #SWICG

  41. @ophiocephalic

    Ah yes...

    Mr #EvanProdromou

    Or Mr #MaxiFedi as I like to call him

    Willing to concede anything to expand his universe infinitely, consequences be damned

    #Mastodon #Meta #SWICG

  42. @ophiocephalic

    Ah yes...

    Mr #EvanProdromou

    Or Mr #MaxiFedi as I like to call him

    Willing to concede anything to expand his universe infinitely, consequences be damned

    #Mastodon #Meta #SWICG

  43. @ophiocephalic

    Ah yes...

    Mr #EvanProdromou

    Or Mr #MaxiFedi as I like to call him

    Willing to concede anything to expand his universe infinitely, consequences be damned

    #Mastodon #Meta #SWICG

  44. @ophiocephalic

    Ah yes...

    Mr #EvanProdromou

    Or Mr #MaxiFedi as I like to call him

    Willing to concede anything to expand his universe infinitely, consequences be damned

    #Mastodon #Meta #SWICG