We'll now throw errors when doing POST /api/v1/push/subscription if the endpoint is an invalid URL, or if the keys values can't be used to encrypt a message.
That prevents you from registering a push subscription that just wouldn't work. We previously lacked input validation here.
Display any notes I might have taken about a user under their follow request in the notifications tab, and let me add new notes.
That would make it much more easy to deal with larger amounts of follow requests right as they come in, see if they follow requested before, and let me write notes for later (i.e. what context they f-req'd in) so I don't lose track of my follow requests.
Usually, when someone follow requests me, I put a note on their profile like this:
follow requested 2024-06-04 after liking, boosting my (topic xyz) post (link to post), replied (link to reply)
Then, when I have the time and energy to, I go through my backlog of follow requests, vet the profiles, and accept or deny the requests.
That requires going back and forth between posts and profiles several times to copy links and such, and whenever I do that, I lose my place in the notifications and have to scroll all the way down again. When I don't have the spoons to, I don't do that, annd those follow requests usually get denied when weeks later I can't reconstruct what they were about anymore.
Having that text field right in the notifications and being able to just copy paste links from the surrounding notifications would be a HUGE upgrade.
@rysiek yeah! I'd love some kind of multi-column layout for that – not the usual multi-column layout that's already available ("advanced interface") that's a UI nightmare, but some kind of context-sensitive columns.
On a 16:9 screen, there's tons of space wasted left and right of the UI. A column there that i.e. displays the poster's profile when you enlarge a post would be amazing.
We keep talking about AI assistants that could enrich our digital experience and provide comfort and semi-automate menial tasks, but we can't even get something like that right. Just put something there that will provide author/thread context for posts.
@matt@ivory it's a sign of the maturing ecosystem, isn't it? most of the major apps are now feature complete compared to the website, so instead of new stuff being constantly added, there's more of polishing and refining :)
It would be so cool if there was an official mastodontext library so projects don't have to copy that slightly modified twittertext into their source. #tuskydev#mastodev
If you've ever tried to implement an OAuth Application for Mastodon, and butted into the “unknown client_id / application” error, where the Mastodon server has silently deleted your OAuth Application….
I'm adding new profile fields to #Smithereen, so I would like to ask the fediverse about what kinds of contact info one would expect to be able to add to their profile. So far I've seen:
Personal website/blog
Matrix
XMPP
Telegram
Signal
Phone number
Twitter
Email
I've not yet seen these in fediverse profiles but they are mainstream enough that won't hurt to add:
@grishka
I'm not sure Iif I've got the gist of what you are planning to do, but my understanding is that you want to add dedicated fields in the user's profile for their social contact info. If that's the case, then I wonder why jot letting the user to define the field names? Something similar to what mastodon does. The benefits are:
I'm just a humble country chicken admin, but I've been thinking a lot about the cost of the fediverse and how we can improve it for all of the instances... in a coop kind of way
The cost of handing all of the media is THE major problem for me atm.
@shlee@Tubsta@decryption almost all colo providers will charge the same for IX / transit traffic. You are effectively buying at a “blended rate”. Transit is now so cheap that unless you are doing more than 1 gig/s sustained it is not worth getting your own ASN and ip range. At the current trend I’d even suggest not bothering below 10 gig/s.
I’ve built a few ISPs and colo networks over the years, I’d be happy to sit down with you and run through the economics of transit , peering and the different price points where changes in network design makes sense.
So, #Smithereen no longer requires a username when signing up. You instead get assigned one automatically, of the form "idXXX" where XXX is the ID for your user record. You can change it later in settings if you wish. Current Mastodon versions handle this change no problem.
The username is only visible in two places:
The URL of your profile
When someone mentions you
So it's not very important. Definitely not important enough to be a required field when you register.
I saw a post today about another Mastodon API endpoint that is kind of in a zombie state (I looked into Featured Profiles awhile back).
This one is a “Mastodon Wrapped" end of year review.
On m.s. it's accessible but as expected doesn't return any data. Currently, the admin would have to jump to the console and run a task to populate the reports.
Like other "wrapped" end of year summaries, it's only available to the user.
@newsmast is the Social Media Feed (@socialmedia) just boosting everything under the mastodon hashtag?
It might be wise to filter out posts also tagged with #MastoDev and #MastoAPI since these are intended for developer audiences rather than the general public.
Just did a test, and I think we may be able to implement FedCM in Mastodon. It seems that you can actually create Doorkeeper Applications with a client_id that's a URL, rather than having it generate a unique client_id for you.
However, where it fails is that you don't get a unique client_id, so registering the same client again fails with a duplicate record error (maybe this is intentional?)
I guess FedCM client_id's don't have a client_secret at all to use…