I happen to know Toni Schneider the new CEO of Bluesky, from his tenure at Automattic. I have some ideas for him, people that follow me will recognize them. ;-)

hey toni, i'm sure everyone is giving you advice on how to evolve your two products, Bluesky and AT Proto. i am no exception. :-)

i think you have to merge the two. make it so that the writing tools you've attracted, that don't fit in with the 300-char limit, and other restrictions you have inherited from twitter, are first class citizens on Bluesky.

When I write in Pckt, i should be writing a Bluesky post. Simple limits, basically what Markdown supports (people love Markdown).

Twitter's limits imho were a good idea at first in 2006, but they have already started getting rid of the limits, and it has made a big difference in the medium.

in other words, i think you and your users need what leaflet, pckt et al are doing. and their posts should be first class citizens on bluesky and that means relaxing the limits.

i see the developers struggling to try to create a namespace for their products, but nothing they come up with can compete with bluesky, nor should it -- the users only know the bluesky name, trying to start something new here gives you a third name of something technical for people to learn, and in the end it'll be what bluesky becomes, because twitter is already getting rid of the limits. and twitter is, like it or not, still the leader in this space.

btw, this editor would fit in there nicely, but i decided in 2017 that i wasn't going to try any longer trying to fit into the hodgepodge of different regulations for each of the social media systems.

anyway, you could be the leader in this space, not by dominating but by dropping the barriers. a bluesky that keeps the limits while twitter is removing them is a bad place to be. you have to be the scrappy innovator, again imho of course.