Extended role permissions for timeline control
What feature would you like implemented? (Please give us a brief description of what you'd like.)
I would like to add some more role permissions to Sharkey, I will make follow up issues for other ones but I am going to group them depending on what category. The role permissions I have in mind are "local media" and "bubble media".
Why should we add this feature? (Please give us a brief description of why your feature is important.)
As I am now the lead administrator of transfem.social, I would like the ability to customize "clutter" on the user interface. I do not particularly like the local media timeline, nor the bubble media timeline. I feel as though it is confusing to new users, and I want to be able to configure my instance to go back to the old timeline layout.
Here is the "old timeline" layout
Here is the "new timeline" layout
Prior to these changes, the preferred way for "media timeline" was to select "Only notes with files". I also feel as though it is kind of creepy to allow for that sort of selection willy nilly, so I'd like to restrict it to only moderation. I believe the best way to implement such controls would be via the existing role permission system, that way people deploying sharkey who wish to use the media timelines can still be able to and I am not being a party pooper.
Version (What version of Sharkey is your instance running? You can find this by clicking your instance's logo at the top left and then clicking instance information.)
2024.6.0-transfem (although we are going to try to migrate off of a custom fork)
Instance (What instance of Sharkey are you using?)
Contribution Guidelines By submitting this issue, you agree to follow our Contribution Guidelines
- I agree to follow this project's Contribution Guidelines
- I have searched the issue tracker for similar requests, and this is not a duplicate.
Activity
Okay, well that answers the question of "what does our custom fork even do?". Apparently, implement features I want to remove. I still think that it would be nice to have a permission for the "Only notes with attached files", as I still maintain my stance of that being "really creepy". People post all sorts of things: memes, selfies, screenshots of intimate conversations, pictures of interesting plants. In the current day, with the countless amount of AI scraping and mass data harvesting (to feed into law enforcement and AI datasets)... I would prefer if we did not hand them a large media set on a silver platter. (I believe we have image galleries? I have not played with that yet for people interested in consuming a large amount of image posts)
Edited by Amber Null-
I do agree on the "only notes with attached files" thing the current issue is that it is completely integrate on client-side only like most of the timeline features so it might take a bit of tinkering to figure out I might look into it after finishing the whole Stripe stuff after 2024.8 is merged and released.
(I believe we have image galleries? I have not played with that yet for people interested in consuming a large amount of image posts)
I actually have never seen anyone use galleries yet but I think that mainly has to do with the fact that it is never explained by Misskey
Edited by Marie Yeah, I have questions regarding "flash" and "galleries". I don't know if you've been on fedi but I've been working off and on making a C# API wrapper for misskey (based on transfem.social's current version of sharkey since i use the api doc there) - https://github.com/Cardboard-Net/Cardboard.Net and I have found some very interesting things in the API. Stuff that confuses me (like "flash") and galleries. When I get to them I'll try to do some toying around to see what they actually are, and what we can do with them. Another disappointment of mine is the oauth2 app stuff... it's actually really sad that doesn't get as much attention. There's no ui for creating an oauth2 app, or registering one as far as I can see. It's been there for quite some time now, as Syuilo uses it in https://github.com/syuilo/Misq/tree/master which is about 8 years old at this point.
The way that I thought everyone made misskey bots and other things that tied into the account, was through the "api token" menu. To find out that there is actually a much more feature rich portion of the api, in which you can define scopes (even view the scopes you have been assigned - something I have been unable to figure out with the more primitive in comparison api key thing). I really wonder why they left it in the dust. Genuinely, why? I can only theorize that AIScript took precedence, people were more interested in making plugins instead of app integrations, but at the same time... AIScript is still heavily limited in what it can accomplish as opposed to an app integration.
-
There's no ui for creating an oauth2 app, or registering one as far as I can see. It's been there for quite some time now, as Syuilo uses it in https://github.com/syuilo/Misq/tree/master which is about 8 years old at this point.
This is sadly where misskey falls short instead of an UI to make an app you quite frankly just request the registration of an App their Doc have an entire page explaining how to use the OAuth2 https://misskey-hub.net/en/docs/for-developers/api/token/oauth/
This also includes a link to all Permissions that can be assigned
Sadly though with the way that we originally wanted to support Mastodon the entire OAuth server got messed up so it is not at all up to date with misskey's current proper OAuth2 server based on specs If we wanted to correctly support OAuth2 currently we would need to currently rip out the mastodon half-ass support and then eventually work on properly adding support for Mastodon API like was planned already for a long time.
Edited by Marie Yes, that's what got me too. I had stumbled upon the permission list expecting that there was an endpoint I could submit my token (or make a request with it as my bearer token to get back a list of permissions). I'd say that now things are changing (hopefully for the better) now would be the time to revisit old plans and start working on them. A common complaint is the lack of proper mastodon api support, alienating people who would prefer to use third party apps such as Tusker. It's one of the things that makes people look at iceshrimp.NET (I was very happy to find first class mastoapi support). As someone who has been down some of the deeper ends of the api...
Exhibit A: https://transfem.social/notes/9xrjqh68sml0008e
Exhibit B: https://transfem.social/notes/9xrlf0r6r3c500c1
Exhibit C: https://transfem.social/notes/9xrmvmtgoc2n01x3 (and relevant issue - #640 (closed))
Exhibit D: https://transfem.social/notes/9xqjrhoirvk1015b
It can be um. Annoying to say the least.
