My first serious feature for #TweeseCake landed in the master branch today. There are places for improvement, but still it's a step forward, I'm far more familiar with the code and with Mastodon protocol now. #Development@app
@menelion@app Can I suggest something? Here's two bugs I'd really, really like to see fixed.
First is when you get a new follower but this person hasn't shared content with you yet, pressing ctrl+d on their follow request because that's all you got access to is only giving you a message saying, no toot. You can't write a private message this way.
Only way I found is to use ctrl+shift+u, copy their username, then get out of there, make a new post, set visibility to direct and manually add the first @ then paste the username.
@menelion@app The second bug is when you edit a post which has a content warning set, instead of having the content warning and the post text defined each in their respective field, the post text field gets something like this:
Content warning: some content warning post text: your post text
Which means you've got to edit that out and manually add the cw again.
@menelion@app And a few features I'd really, really like to see added are: lists support, adding descriptions to attached media (it's very ironic that a client made for the blind doesn't let you use alt text), interaction and creation of polls.
@ner@app I cannot disclose where is the code, but we do use version control system indeed, it's logical :). and of course, even closed-source projects work using the same model, at least, most of them. For instance, in the company where I work (I mean, my full-time job) we use Git and of course each developer sends pull requests.
Add comment