This is a #nos-dev-diary from a mostly-backend-developer.
Not much progress as I got sick after #nostrica but I landed a couple of improvements to https://tweeter.nos.social/. It is cool to see people use it!
- tweets now contain https://njump.com/ links to the associated events
- it will now avoid cutting links in half when shortening notes
- it correctly detects nostr nevent/npub/note links and translates them to https://njump.com/ links
- fixed a bunch of backend bugs so it should be more reliable
If you have bug reports, feedback or any other suggestions post them here or create an issue. The service is open source of course. I try to translate all feedback to issues so that it doesn’t get lost.
https://github.com/planetary-social/nos-crossposting-service/issues
Plans for the near future:
- investigate why purple pages sometimes doesn’t return events in response to queries, this makes the service struggle after restarts (this is how the service grabs your relays)
- resume work on a crawler-like service that will feed events into our other services e.g. the service that generates push notifications, the service that tries to analyse content reports using AI etc, we could also spin up an alternative to purple pages on top of that service
This is a #nos-dev-diary from a mostly-backend-developer.
We posted about our Twitter crossposting service a short while ago but there were some problems with the Twitter API and messages got stuck in the queue resulting in tweets not being posted. What I speculate has happened is that some people exceeded their personal API limits and their tweets got stuck in the queue blocking other tweets from being posted. I can't confirm this since Twitter reports that we have not exceeded the API limit despite responding with “Too many requests”. I released an update which resulted in some tweets being sent by implementing proper backoffs and handling messages out of order.
Given that fact that I suspect people wouldn't be happy with a sudden wave of tweets being posted I haven't copied the messages that were stuck to the new queue for now so only new notes will generate tweets.
The service is available here: https://tweeter.nos.social
If someone has seen weird Twitter API behaviour similar to the one I described where all calls fail with “too many requests” but clearly no requests succeeded in the windows specified in the docs please let me know.
Previous:
nostr:nevent1qqsdh7cce4tu85a4gushmt0gexkfyc27h49nte8f9hennk4dfe9fm8qpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzpee3efp8cxq9n4nxxmwl4mhtz5qjhskm8nwj0w0yet09q4axaqhdqvzqqqqqqyanyrx7
#twitter #nostr
boreq's #japan experiences: don't try to queue at the store 50cm to the left of the queue markers they put on the floor instead right on top of them or you will be yelled at #nostrasia
Yeah Twitter API constantly responds with "rate limit exceeded" even though it itself reports that we didn't exceed it so it is quite confusing, I will see if I can try to fix it tonight as my previous fixes failed.
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.
https://github.com/planetary-social/nos-crossposting-service/issues/41
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.
https://github.com/planetary-social/nos-crossposting-service/issues/44
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.
https://github.com/planetary-social/nos-crossposting-service/issues/42
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.
Oddbean new post about login | logout
Notes by boreq | export