Occasional post to remind folks that I'm always on the look-out for new projects and fun uses of the #MastodonAPI - let me know what your favourite new tools are! 👀
Czy chcielibyście rozszerzenie do przeglądarek (Chromium i Firefox-podobne), która pozwala szybko udostępniać linki na #Mastodon poprzez #MastodonAPI? 🤔
Ist es irgendwie möglich, per #MastodonAPI einen Datenexport anzustoßen und runterzuladen? Würde das gerne 1x monatlich machen & um trotz 2-monatlicher "automated post deletion" mein Archiv automatisch lokal komplett zu halten.
Weder MastodonPy noch rtoot scheinen das zu können. Vielleicht kennt @ordnung eine Lösung?
This may have been around for awhile, but I just found that Postman has an AI code generator that can assist with making visualizations of API responses, including Mastodon search results.
🆕 blog! “How far did my post go on the Fediverse?”
I wrote a moderately popular post on Mastodon. Lots of people shared it. Is it possible to find out how many different ActivityPub servers it went to? Yes! As we all know, the Fediverse is one big chain mail. I don't mean that in a derogatory way. When I write a post, it appears on […]
#HowToThing#016 — Building a small (and very incomplete!) Mastodon UI with #ThingUmbrella. Still, the following features are included so far and demonstrate:
Looking up Mastodon account details & loading public messages for any given username
UI design heavily inspired by the amazing @phanpy (😍)
Alas, the code for this new example (#131) is too long & too split up for showing here in this format, but it's well documented and you can find it all linked below...
I hope this (and other parts) of this ongoing #HowToThing series are interesting to you. If so, please consider boosting and/or supporting my #OpenSource work via GitHub or Patreon. Thank you very much in advance!
🆕 blog! “On The Fediverse, No One Knows You're A Liar”
One of the reasons I'm still on the original Mastodon.social instance is that I am vain. I joined shortly after the project was announced and, as a consequence, I have a "joined" date of 2016 and a user ID of under 10,0001. This doesn't make me an "elder statesman" and is rarely useful beyond bra…
The latest version of Mastodon includes search functionality. It's early days, but seems to work pretty well. Here are some of the interesting things I found when using it. Search is complex - expectations I don't mean the act of searching a database - that's routine - but I mean it is socially complex. Lots […]
Is it possible to restrict your timeline by ... time? Like "12h ago to 4 hours ago". Other than by scrolling scrolling scrolling, keep them thumbwheels scrolling, rawhide ...
I'll take answers that apply to Mastodon web, or Android apps Mastodon or #Tusky or #Megalodon. Or in fact anything.
I'm also up for coding this in #Python using the #mastodonapi. But I suspect the protocol may not encode time.
Fedi/Mastodon programmers... with the #MastodonAPI, and given a url to a post on any instance (assuming I have access to the toot from my account), how might I get my instance to fetch it and give me a "local" ID that is suitable for passing as the "inReplyToID" in a toot payload?
@ivory does the #MastodonAPI make it possible to make a list of #hashtags to follow? I’d love to be able to switch over to a list that just follows hashtags relevant for a topic.
I just noticed that Mastodon web is identifying Group accounts in the UI and happy to see it.
With the #Threadiverse expanding, I appreciate knowing that I am replying or interacting with a Group account, where my response may end up in front of audiences I wasn't expecting.
Hoping more third party clients will start adding this as well.
The identifier is included in any Account element returned in through the official API.
Adding #e2ee to DMs on the fediverse sounds relatively simple, but is actually more complicated than I initially thought.
A property for a public key could be added to the object contains info about a user (name, pfp, inbox, etc).
This public key can then be used to encrypt the contents of a message/note, except for the recipient.
The remote server will still be able to see what server the message came from and who the message is for.
The recipient's client then needs to decrypt this message, but where is the decryption key stored?
Perhaps it can be stored on the server encrypted using the user's password?
Upon logging in, the encrypted decryption key would be sent to the user.
This wouldn't actually work, a server admin can always modify the server code to log passwords.
Encryption would have to be implemented client side separately.
The private key can't be stored on the server securely. The user needs a way to create a key pair, then send the public key to the server and store the private key.
On browsers this would require JavaScript that needs to be downloaded from the server, which can be modified to add a backdoor. On apps this would work a lot better.
But when a user just installed a new app/client, they won't be able to see their older DMs.
The only realistic way of implementing this is as an extension to the mastodon api, it's too easy to backdoor on browsers by either server admins, malicious browser plugins or network admins.