The bmannconsulting.com website
bmann.ca
1---
2title: Mostly POSSE
3date: 2024-01-06, 11:07:48 -08:00
4tags:
5 - blogging
6 - POSSE
7 - crossposting
8categories:
9 - BMC
10---
11An overview of my social accounts and posting. It can be summarized as mostly [[POSSE]].[^overload]
12
13This started as a short post to put directly into a single Mastodon post about my three Mastodon accounts, but kind of got out of hand, so now it’s a blog post.
14
15* I use [@boris@cosocial.ca](https://cosocial.ca/@boris) as my main Mastodon account. It receives cross-posts from my [personal blog](https://blog.bmannconsulting.com). Food photos, local Vancouver adventures, travel.
16
17* [@boris@fission.social](https://fission.social/@boris) is my work account - decentralized compute [@everywherecomputer@fission.social](https://fission.social/@everywherecomputer), [[IPFS]] and protocol discussions
18
19* [@boris@toolsforthought.social](https://toolsforthought.social/@boris) is hooked up to my [journal posts](https://bmannconsulting.com/journal/). The journal items also get cross-posted to [@bmannconsulting.com on Bluesky](https://bsky.app/profile/bmannconsulting.com)
20
21My <https://bmann.ca> landing page links to all my social accounts[^all], and [@bmann.ca is also my Bluesky username](https://bsky.bmann.ca).
22
23[^all]: Technically not all of them. I have Instagram and Facebook accounts that I don’t use. I have a Swarm/Foursquare account. Maybe I will eventually list _all_ my accounts for completeness 😅
24
25I used [[Bluesky]] a lot in the early days, less so now. I’m more interested in [[ATProtocol]] than any particular network built with it, and am also interested in their [[DID]] based user ID system.
26
27My third Bluesky account is for my [[FoodWiki]] and is [@foodwiki.bmann.ca](https://bsky.app/profile/foodwiki.bmann.ca). For a change of pace, it has no automation and nothing cross posts to it! I hand post food pictures and recipes that I put on my FoodWiki. In part I made that a Bluesky account because many Mastodon users expect Content Warnings (CW) on things like food pictures.
28
29I still have a Twitter account, but only use it for cross-posting to. The [[Twitter]] note page here also details my archive.
30
31I have a [[Farcaster]] account and access that protocol through the [[Warpcast]] app.
32
33[Tech Blog](https://bmannconsulting.com/blog/) posts I’m not auto cross posting. In part because they come across as just title plus link without any context in [[Micro.blog]]’s feed cross posting. Until I relaunched this site over the holidays, my long form tech blogging had effectively lapsed. We’ll see what the year brings!
34
35[[Fedica]] is a commercial service that does cross posting that I’m experimenting with for sharing blog posts.
36
37The Fedica model supports 8 accounts even at the free account tier, which is great! But, even at paid tiers, you can only use one account per network, so right away it doesn’t support my three Mastodon accounts. And yeah, I have a pile of company and project accounts I run for work on the [Fission Mastodon Server](https://fission.social/@fission).
38
39There’s a whole other discussion to be had here about the affordances of each network[^affordances] that fights against cross-posting. No hashtags on Bluesky or Micro.blog. No quote posting on Mastodon. And different character count lengths and embedding support.
40
41[^affordances]: [[Erin Kissane]] has been doing lots of writing and research about this, like her [Affordance Loop](https://erinkissane.com/the-affordance-loop) article: “Affordances, in the simplest terms, are _what an object offers or provides to a specific individual at a particular moment in time_.”
42
43I’ll continue to experiment across many different networks, servers, and protocols. I’ll produce [[feeds]] from here.
44
45I’ll look to own my accounts and data, and continue [[pooling capital and collaboration]] to work with others.
46
47[^overload]: And overload! Yes I realize this is a lot of accounts and protocols and platforms to experiment with. The last time it was this dense was the mid 2000s. This time around, I’m hoping we can end up in more interoperable protocols, with my hope being that [ActivityPub and ATProtocol](https://bmannconsulting.com/blog/2024/01/05/why-not-both-protocols/) are both solid foundations for the next generation of not just social networks, but many apps.