So say if I was to work on a project or something. At what stage would it make sense for it to become it’s own account? Like is it when it gets to the point of it’s own account to show the project off instead of using my own personal one?
If you’re talking about an account on the fediverse, I don’t think it matters much at this point.
If mean like a typical social media account like an Instagram, or a GitHub page or something, I’d say that when you want people you don’t know to look at it and understand what’s going on, projects should have their own account.
I have a personal Instagram account that I throw 3d printing, car, and some paint related things on so I can easily show my friends and family stuff that I do, but I also sell DnD minis and have a separate account that I only post minis to that has information about pricing and whatnot.
Yes I’m mainly talking about a general Fediverse account through Mastodon, PixelFed or another system.
My concern is obviously if a project is slow developing it might be weeks before you see another post and it just looks like another idea or project that someone just dropped if there’s not frequent posts.
I would say go ahead and make a separate account if it’s here on the fediverse and it’s important to you that progress remains trackable and organized. A vast majority of accounts and communities here have very little content. Even if you’re posting very infrequently, the community here is small enough that people who are interested will see and remember the previous ones.
A small thing that I think would help mitigate the “abandoned project” look is putting the date in the title of your updates. The post will obviously have a timestamp on it that shows how old the post is (ie “posted 4 weeks ago”), but seeing [December 2024 Update] at the top of a profile feels much more reassuring that something is being worked on, and also makes it easier for anyone scrolling through the account to a. get an idea of how much things are being worked on, and b. navigate through the project history.
What do you mean by that? A community?
So say if I was to work on a project or something. At what stage would it make sense for it to become it’s own account? Like is it when it gets to the point of it’s own account to show the project off instead of using my own personal one?
If you’re talking about an account on the fediverse, I don’t think it matters much at this point.
If mean like a typical social media account like an Instagram, or a GitHub page or something, I’d say that when you want people you don’t know to look at it and understand what’s going on, projects should have their own account.
I have a personal Instagram account that I throw 3d printing, car, and some paint related things on so I can easily show my friends and family stuff that I do, but I also sell DnD minis and have a separate account that I only post minis to that has information about pricing and whatnot.
Yes I’m mainly talking about a general Fediverse account through Mastodon, PixelFed or another system.
My concern is obviously if a project is slow developing it might be weeks before you see another post and it just looks like another idea or project that someone just dropped if there’s not frequent posts.
I would say go ahead and make a separate account if it’s here on the fediverse and it’s important to you that progress remains trackable and organized. A vast majority of accounts and communities here have very little content. Even if you’re posting very infrequently, the community here is small enough that people who are interested will see and remember the previous ones.
A small thing that I think would help mitigate the “abandoned project” look is putting the date in the title of your updates. The post will obviously have a timestamp on it that shows how old the post is (ie “posted 4 weeks ago”), but seeing [December 2024 Update] at the top of a profile feels much more reassuring that something is being worked on, and also makes it easier for anyone scrolling through the account to a. get an idea of how much things are being worked on, and b. navigate through the project history.