Thanks for proposing this Holden.
On 12/1/22 17:09, Holden Karau wrote:
The main negatives that I can think of is an additional account for the
PMC to maintain so if we as a community don’t have many people on
Mastodon yet it might not be worth it.Would need probably about ~20
minutes of
The main negatives that I can think of is an additional account for the PMC
to maintain so if we as a community don’t have many people on Mastodon yet
it might not be worth it. Would need probably about ~20 minutes of setup
work to make the sync (probably most of it is finding someone with the
Since this is just syndication I don't think arguments on the benefits of
Twitter vs Mastodon are that important, it's really just what are the costs of
additionally posting to Mastodon. I'm assuming those costs are basically 0
since this can be done by a bot? So I don't think there is any
My personal opinion, one of the most features of Twiiter that it is not
federated and is good platform for annonces and so on. So it means "it
would be good to reach our users where they are" means stay in twitter(most
companies who use Spark/Databricks are in Twitter)
For Federated features, I
I agree that there is probably a majority still on twitter, but it would be
a syndication (e.g. we'd keep both).
As to the # of devs it's hard to say since:
1) It's a federated service
2) Figuring out if an account is a dev or not is hard
But, for example,
There seems to be roughly an aggregate
Hello,
Does any long-term statistics about number of developers who moved to
mastodon and activity use exists?
I believe the most devs are still using Twitter.
чт, 1 дек. 2022 г., 01:35 Holden Karau :
> Do we want to start syndicating Apache Spark Twitter to a Mastodon
> instance. It seems
