Thread

Replies (13)

I get this when I try to X authenticate error calling login or register handler: transaction error: error calling the provided function: error getting or creating account: error creating the account: error saving the new account: error executing the insert query: database is locked
This is the proper flow. I remember a big turn off when I first started exploring Mastodon some years ago was the majority just seemed to be Twitter bots reposting from Twitter. Make no mistake this is a hostile attack. Having the authentic conversation here only to leave the platforms a ghost town of unresponsive bots. Keep up the good work.
[Apologies if this is the wrong place to post feedback for this service -- please feel free to direct me to a better place.] Thanks again for creating this service! It's great--I'm glad to have it. My feedback is only intended to help improve the service. 1. I know Twitter doesn't yet support uploading longform tweets via the API. When it becomes possible to do so, I would prefer that the tweet not be truncated. 2. May we also have a flag to turn off the njump link? Unfortunately, Twitter posts mostly a duplicate of the tweet as a preview in blinding black on white text. 3. Would like to be able to upload attached images directly to Twitter. As I think only one image per upload is allowed, upload the first image in the tweet, if there are multiple images. Example tweet posted below. image
Ok I finally managed to sit down and think about this after I got over the jet lag and getting sick. I translated all the suggestions into GitHub issues to make sure that they aren’t lost. I think posting long tweets would make perfect sense and would let us remove the njump links completely which you mentioned as a problem in the second point. That being said I agree that right now I don’t think this is possible using the API? I feel like it should be so maybe there is a way but the docs for the new API aren’t great right now I feel. Regarding the njump links: I like them because it helps find the original content but at the same time I agree that they look awkward and out of place. I can think of multiple approaches: - skip rendering njump links when notes aren’t cut off because they fit in one tweet - remove njump links completely even if a note is cut off - don’t post notes which are too long - post long notes as threads with multiple tweets - let people decide what to do on a per-feed basis which unfortunately complicates the website All of those solutions have downsides and I don’t know what the best one is. Images can be posted directly to twitter but the problem is that that loses context around where that image was in the note. For example I often post links to content images and write in between them like I did in this note. This just doesn’t translate into the twitter format. Basically I feel we are dealing with all the typical problems of crossposting from one platform to another :( If anyone has any suggestions regarding any of those problems please let me know.
A related issue with long links in addition to the awkwardness is that this, for example: takes 85/500 chars on Mastodon toot. 24/300 in Bsky (it’s capped on URLs) or none if posted as an embed and not in the body), and 43/300 in X (if I got it right). That makes cross-posting or composing notes hard to do at once. Weirdly, you can put more characters on Bsky by deleting the URL from the body text than what X allows (for non-verified) 😁