Conversation

Notices

1. Embed this notice
   Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Thursday, 03-Oct-2024 21:04:07 JST Jan Wildeboer 😷:krulorange:

   In the olden days, a FOSS (Free/Open Source Software) project typically had:

   - A source code repository
   - A web page with the documentation and links to downloads
   - At least one mailing list called announce, typically also one for users and one for contributors, all with public archives
   - An IRC channel to chat with other users and maybe also the developers

   Maybe it’s time to try that simple approach again? Everything open, everything accessible? 1/4

   • /home/leandroramos repeated this.
   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Thursday, 03-Oct-2024 21:04:11 JST Jan Wildeboer 😷:krulorange:

     in reply to

     In those olden days, we also had some helpful rules. One was that only things that can be referenced in code or mail archives actually exist. So when there was a long discussion on IRC, someone wrote down the outcome (or coded the patch) and made it accessible to all. This was an important rule to avoid excluding those that didn’t have the time/willingness/connectivity to spend hours on IRC. 2/4

     Haelwenn /элвэн/ :triskell: likes this.
     /home/leandroramos and Bø!rge repeated this.
   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Thursday, 03-Oct-2024 21:04:11 JST Jan Wildeboer 😷:krulorange:

     in reply to

     When I now see slack, discord, github etc everywhere as a requirement for participation, I know that we are exchanging a bit of comfort for the IMHO very high price of excluding a lot of potential contributors and giving a lot of data to proprietary companies without a real need for that. 3/4

   • Embed this notice
     /home/leandroramos (leandroramos@mastodon.social)'s status on Thursday, 03-Oct-2024 21:06:52 JST /home/leandroramos

     in reply to

     @jwildeboer I will never understand why some #freesoftware projects centralize conversations in things like Discord and Slack.

   • Embed this notice
     Daniël Franke 🏳️‍🌈 (ainmosni@berlin.social)'s status on Thursday, 03-Oct-2024 21:07:45 JST Daniël Franke 🏳️‍🌈

     in reply to

     @jwildeboer When I got more involved with the Kubernetes community, it was also my first encounter with Slack, and having the main communication channel of an open source project be proprietary always rubbed me the wrong way.

   • Embed this notice
     feld (feld@friedcheese.us)'s status on Thursday, 03-Oct-2024 22:50:38 JST feld

     in reply to
     @jwildeboer counterpoint: when you force people to use IRC, you're excluding a *LOT MORE* potential contributors because so many people do not like or want to learn IRC, especially younger folks. They want a nice app, rich chat features, and limited friction to sign up / connect.
     
     The IRC crowd is old now. A lot of investment needs to be made into making IRC "comfy" for people. I don't know how to solve this. I've worked on several teams where we used IRC and when new people came onboard they were absolutely horrified and confused about IRC. They did not like it and mostly abstained from using it.
   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Thursday, 03-Oct-2024 23:11:37 JST Jan Wildeboer 😷:krulorange:

     in reply to

     • feld

     @feld I don't even think of using IRC that much. I am describing what we did in the past and how all of that had one thing in common: being open and accessible. Compare that to having to have accounts on two or three external (proprietary) services *per project* you are interested in. THAT's my point.

     feld likes this.
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Thursday, 03-Oct-2024 23:13:38 JST feld

     in reply to
     @jwildeboer What is our best option to replace those services, though?
     
     I think we're basically looking at Gitter, Mattermost, and RocketChat with Gitter being the most open option (no enterprise/proprietary features // "open core" junk)
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Thursday, 03-Oct-2024 23:15:07 JST Sick Sun

     in reply to

     • feld
     @feld what about zulip
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Thursday, 03-Oct-2024 23:16:53 JST feld

     in reply to

     • Sick Sun
     @sun actually wait Zulip is the one I'm thinking of, not Gitter
     
     I was just evaluating all of these a week ago and only one seemed properly "open" and it was Zulip, the python one.
     
     https://zulip.com/for/open-source/
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Thursday, 03-Oct-2024 23:17:38 JST Sick Sun

     in reply to

     • feld
     @feld we're using zulip right now instead of having a discord and it's working pretty good, I think it even integrates with your own or someone else's jitsi meet
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Thursday, 03-Oct-2024 23:20:27 JST Sick Sun

     in reply to

     • feld
     @feld what were you evaluating them for
     
     I could give you access to my zulip
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Thursday, 03-Oct-2024 23:24:58 JST feld

     in reply to

     • Sick Sun
     @sun personal use for friends/family mostly but also wanted to know how good they were in comparison to Slack/Discord.
     
     I don't think they work very well for socializing because their features and design are just not aimed at that use case
     
     But Zulip specifically has a very good approach to containing chat discussions to around threads/topics and making it easy for someone like a project maintainer to keep a handle on things
     
     I think we should embrace it more, maybe even for Pleroma because IRC is likely one reason we don't get as much engagement plus people can't look back on previous discussions, are logged off when you reply, etc...
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Thursday, 03-Oct-2024 23:25:47 JST Sick Sun

     in reply to

     • feld
     @feld I wonder if it could be rigged so you could use your fedi account to auth to it.
     
     I am willing to host a pleroma zulip
     feld likes this.
   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Thursday, 03-Oct-2024 23:26:03 JST Jan Wildeboer 😷:krulorange:

     in reply to

     • feld

     @feld The very first question should always be: how much value do these services bring to your project and at what price? Devils advocate question: do we really need these tools or are they maybe a time and resource black hole? I for ne wouldn't even think of adding discord, matrix to my projects. Code, issues, releases via forgejo/codeberg/github , a homepage and maybe a mailing list would be enough for me. So I guess I am the wrong person to ask about alternatives ...

     feld likes this.
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Thursday, 03-Oct-2024 23:26:39 JST feld

     in reply to
     @jwildeboer that's how I've always felt too but the more I interact with younger technical folks the more I realize that I might as well be asking them to send me a fax 🥲
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Thursday, 03-Oct-2024 23:28:25 JST Sick Sun

     in reply to

     • Sick Sun
     • feld
     @feld I am reading right now about how to do multiple organizations, it looks like you need a subdomain per organization and a subdomain for auth
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Thursday, 03-Oct-2024 23:29:53 JST feld

     in reply to

     • Sick Sun
     @sun I think we could write our own OAuth module that would let the user login with their fedi account name and it can automatically OAuth to their server
     
     this shouldn't be crazy hard to do, let's investigate it further
     Sick Sun likes this.
   • Embed this notice
     :blank: (i@declin.eu)'s status on Thursday, 03-Oct-2024 23:31:31 JST :blank:

     in reply to

     • Sick Sun
     • feld
     @sun @feld custom auth via python-social-auth is pretty easy to add, but since there's no masto module yet, you'd have to add that class yourself like pleromas ejabberd guide
     
     https://python-social-auth.readthedocs.io/en/latest/backends/implementation.html#auth-apis
     Sick Sun likes this.
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Thursday, 03-Oct-2024 23:32:07 JST feld

     in reply to

     • :blank:
     • Sick Sun
     @i @sun this could actually be a really good thing for the Fediverse in general. If we built this maybe projects would start using Zulip as their main chat platform
     
     Anyone here good at Python? I could hack it together but it wouldn't be pretty. I'd throw money at a bounty for this if we can determine that what we want to build is 100% possible.
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Thursday, 03-Oct-2024 23:34:36 JST Sick Sun

     in reply to

     • :blank:
     • feld
     @feld @i I can't wait to hear about how it's not e2ee
   • Embed this notice
     Zergling_man (zergling_man@sacred.harpy.faith)'s status on Thursday, 03-Oct-2024 23:56:33 JST Zergling_man

     in reply to

     • :blank:
     • Sick Sun
     • feld
     @i @sun @feld I like how the example code is basically uesless because all of the important bits are hidden in the google whatever library.
     Also I like how it has an oauth2 thing in it anyway, but you still need to fiddle with it to generate client_ids so the custom thing probably works out easier.
     Sick Sun likes this.
   • Embed this notice
     vv221 (vv221@fediverse.dotslashplay.it)'s status on Friday, 04-Oct-2024 00:15:38 JST vv221

     in reply to
     Wait, we are no longer supposed to do that?
     
     (I dropped the website because it had too high of a maintenance cost, and never started a mailing list, but I have the public git repository (self-hosted) and the IRC channel)
     
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 04-Oct-2024 00:18:58 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • vv221
     @vv221 @jwildeboer Well it's also what I do, I haven't entirely done the mailing-list part for my own projects so far (although https://lists.sr.ht/~lanodan/public-inbox is a thing), maybe I should so people can see each others patches rather than just me.
     For announces… I kind of feel like rss/atom feeds are better for this purpose.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 04-Oct-2024 00:24:03 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • vv221
     @vv221 @jwildeboer Well even if they don't sign up, having a public archive can be interesting, specially as IRC isn't archived (although geeknode supports ChatHistory so connection cuts of less than a day aren't problematic).
   • Embed this notice
     vv221 (vv221@fediverse.dotslashplay.it)'s status on Friday, 04-Oct-2024 00:24:04 JST vv221

     in reply to

     • Haelwenn /элвэн/ :triskell:
     In my case I tend to think that my software is too much of a niche to get anyone interested enough to sign up to a mailing list, but at the same time would not have already joined our IRC channel. So I use the IRC channel for all announces.
     
     CC: @jwildeboer@social.wildeboer.net
     
   • Embed this notice
     vv221 (vv221@fediverse.dotslashplay.it)'s status on Friday, 04-Oct-2024 00:45:40 JST vv221

     in reply to
     I am all for the GitHub/gitlab/forgejo/codeberg based approach of managing issues, PRs, releases in "modern" ways.
     This is where I am probably more grumpy than you are, as I am currently moving away from this model. What triggered that is the realization that I ended up spending much more time moving issues around and writing in merge requests comments what should have gone in commit messages in the first place, than the time I spent on what I find really fun: improving/breaking my software!
     
     No longer considering the forge (self-hosted GitLab for me) as the central place magically freed up a lot of time that I can spend on the actual software development and maintenance instead.
     
     This is still an ongoing migration, as I have yet to find a good bugs/requests tracker to replace the issues system integrated in GitLab.
     
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Friday, 04-Oct-2024 00:45:41 JST Jan Wildeboer 😷:krulorange:

     in reply to

     Seeing how quite some commenters (want to?) take the wrong conclusions from my thread: I am all for the GitHub/gitlab/forgejo/codeberg based approach of managing issues, PRs, releases in "modern" ways. It made drive-by contributions so much easier! I am however not sure if discord et al are better for asynchronous communication and feel that mailing lists with public archives were a superior approach that we gave up on prematurely. HTH! 6/6

   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Friday, 04-Oct-2024 00:45:42 JST Jan Wildeboer 😷:krulorange:

     in reply to

     I am throwing this out here not to come over as a grumpy old man, yelling at the clouds. But because I guess many enthusiastic, young people simply never experienced the olden ways. Maybe they want to explore them a bit and see for themselves if there could be something viable in it for them. Especially wrt async communication. Is all! 5/6

   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Friday, 04-Oct-2024 00:45:43 JST Jan Wildeboer 😷:krulorange:

     in reply to

     Maybe this short thread makes you think a little bit about that. That would mean a lot to me! Run your projects in every way you want, I am not telling you to make changes. I merely hope that you start to think a bit about what's best to grow your community in an inclusive and open way, is all :) 4/6

   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Friday, 04-Oct-2024 00:46:38 JST anna

     in reply to

     • Luna :neofox_snug:
     • anna
     @jwildeboer @lunareclipse
     
     i've been in a dozen mailing lists (some with high thruput, gentoo-user and gentoo-devel with close to 2 to 3 dozens mails per day), and my ~/mail/Lists folder is 62M in size, which is nothing
     
     the it'll only be an issue with a mail provider if they charge you *per mail* instead of per storage which unless you're getting hundreds of mail a minute, is dumb
     
     lastly, sending patches to a mailing list without being subscribed to said list should be allowed, and is on sourcehut for example, if the patches list requires you *to be subscribed*, i'd understand the issue, but nothing stops a mailing list that accepts patches without a subscription, making it *more* convenient than a forge
     
     no making a new account on a small self-hosted forge to make a single pr or issue, you just, mail it from your already existing mail account
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Friday, 04-Oct-2024 00:46:40 JST anna

     in reply to

     • Luna :neofox_snug:
     • anna
     @lunareclipse @jwildeboer
     
     also, https://lore.kernel.org which is arguably the biggest mailing list out there, has a thread-like view too, if you click "nested" view instead of "flat"
     
     and it has an rss/atom feed so you can keep up with the list without being subscribed to the list
   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Friday, 04-Oct-2024 00:46:42 JST anna

     in reply to

     • Luna :neofox_snug:
     @lunareclipse @jwildeboer
     
     > but I have never seen anyone implement a way to read mailing lists like that
     
     https://docs.mailman3.org/projects/hyperkitty/en/latest/
     
     e.g.
     https://lists.fedoraproject.org/archives/
     https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/U5CFAJ2EULZPX46SHAJYU75USGUV7HSD/
   • Embed this notice
     Luna :neofox_snug: (lunareclipse@snug.moe)'s status on Friday, 04-Oct-2024 00:46:44 JST Luna :neofox_snug:

     in reply to

     @jwildeboer mailing lists and IRC channels are like the opposite of accessible
     
     to elaborate:
     
     IRC is unusable on mobile internet connections, or on multiple devices at once, doesn't keep any history and has none of the features you would expect from a chat protocol in 2024 (yes bouncers exist but they are extremely convoluted to set up and often assume you have some arcane knowledge on how IRC works that doesn't seem to be actually documented anywhere)
     
     Mailing lists clutter your inbox with tons of discussion you don't care about and are very difficult to read especially when a thread splits into multiple branches.
     The best way I've seen of solving it is to display threads like Reddit or Misskey does, but I have never seen anyone implement a way to read mailing lists like that. Most forum software just ignores the problem by not supporting any way of "forking" a discussion, which results in terrible, impossible to follow threads where every other post quotes some previous post related to a different topic (see XDA-developers).
     Also my email provider would ask me to pay up for the volume of received email if I joined a few mailing lists each receiving dozens of messages a day.
     
     If a project requires me to join a mailing list to contribute I will simply not contribute to the project. Git forges exist for a reason, they provide really good UX for merge requests and issue tracking.

   • Embed this notice
     vv221 (vv221@fediverse.dotslashplay.it)'s status on Friday, 04-Oct-2024 00:48:02 JST vv221

     in reply to

     • Grant
     Come work with me, I’m happy to get contributions as some lines put on whatever paste is around ;)
     
     I make sure that contributors are never forced to use git, even if I use it (and love it) myself. I even had contributors sharing pieces of code or whole files as attachments in issue comments on our GitLab instance.
     
     CC: @jwildeboer@social.wildeboer.net
     
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Grant (iamsomegrant@twit.social)'s status on Friday, 04-Oct-2024 00:48:04 JST Grant

     in reply to

     @jwildeboer Some time ago I created a feature for a popular code editor. I thought it would be helpful to others so I posted the code on the 'issues' thread. But actually, I should make a pull request and a fork and feature..merge.. I don't know. It's 6 lines of code, take it or leave it. I know "Pull request" is probably a matter of course if you're already a frequent open source contributor, but it'd be nice to dip my toes in the water without pushing me into the deep end.

   • Embed this notice
     feld (feld@friedcheese.us)'s status on Friday, 04-Oct-2024 03:49:04 JST feld

     in reply to

     • Anthk
     @anthk these are good points but the average person doesn't care. It works today, it has features they like: that's good enough. They're not worried about proprietary clients and they're not worried about the service disappearing tomorrow and losing their data. All they want is for it to be easy to use.
   • Embed this notice
     Anthk (anthk@paquita.masto.host)'s status on Friday, 04-Oct-2024 03:49:06 JST Anthk

     in reply to

     • feld

     @feld @jwildeboer IRC or XMPP won't change the API. Discord can be useless tomorrow. And you need a propietary client to join.

   • Embed this notice
     feld (feld@friedcheese.us)'s status on Saturday, 05-Oct-2024 00:49:20 JST feld

     in reply to

     • :blank:
     • Sick Sun
     @i @sun I can't view this video at the moment but I am excite!!! :dogcited:
   • Embed this notice
     :blank: (i@declin.eu)'s status on Saturday, 05-Oct-2024 00:49:22 JST :blank:

     in reply to

     • :blank:
     • Sick Sun
     • feld
     @feld @sun 99 problems of https://256.lt/zulip.py later, and the credential harvester poc.256.lt works
     Sick Sun likes this.
   • Embed this notice
     :blank: (i@declin.eu)'s status on Saturday, 05-Oct-2024 00:49:23 JST :blank:

     in reply to

     • Sick Sun
     • feld
     @feld @sun seems like that's not an option without a fork, best option after a couple of hours or staring at docs/code/issues, is setting up their /accounts/login/jwt/ flow on the backend of another web app
     
     https://github.com/zulip/zulip/issues/24278#issuecomment-1865424813
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Saturday, 05-Oct-2024 00:54:29 JST feld

     in reply to

     • :blank:
     • Sick Sun
     @i @sun holy shit dude it works!!! I had to click the registration button after it said my account didn't exist but otherwise it was pretty seamless
   • Embed this notice
     :blank: (i@declin.eu)'s status on Saturday, 05-Oct-2024 00:59:15 JST :blank:

     in reply to

     • Sick Sun
     • feld
     @feld @sun have a gif instead then, hardest part was figuring out that the subdomain in my setup wasn't "zulip" but "" in the JWT settings as far as zulip was rightfully concerned
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Saturday, 05-Oct-2024 01:28:15 JST feld

     in reply to

     • þernia
     • :blank:
     • Sick Sun
     @pernia @i @sun This covers it pretty well
     
     https://zulip.com/why-zulip/
   • Embed this notice
     þernia (pernia@cum.salon)'s status on Saturday, 05-Oct-2024 01:28:16 JST þernia

     in reply to

     • :blank:
     • Sick Sun
     • feld
     @i @feld @sun how does the topic thing work? How does it know if something is a conversation?
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Saturday, 05-Oct-2024 01:29:31 JST feld

     in reply to

     • :blank:
     • Sick Sun
     @i @sun Also does this provide the capability for users to register an account // not be forced to use a fedi account?
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Saturday, 05-Oct-2024 01:31:59 JST feld

     in reply to

     • :blank:
     • Sick Sun
     • feld
     @i @sun I think there's still one more piece missing because from the app it doesn't know about this SSO
     
     On servers with GitHub etc enabled there are more buttons showing up here
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Saturday, 05-Oct-2024 01:37:03 JST feld

     in reply to

     • :blank:
     • Sick Sun
     @i @sun Hmm so it's not possible to expose a button that links to a page with the field where you put your fedi account name in?
   • Embed this notice
     :blank: (i@declin.eu)'s status on Saturday, 05-Oct-2024 01:37:04 JST :blank:

     in reply to

     • Sick Sun
     • feld
     @feld @sun because the JWT flow is not actually a proper SSO module like the rest, but an authentication skip
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Sunday, 06-Oct-2024 00:21:08 JST Sick Sun

     in reply to

     • :blank:
     • feld
     @i @feld Okay, I made some changes to it so it doesn't have as many steps:
     
     https://git.shipoclu.com/moon/zulip-fediverse-auth/src/branch/master/auth.py
     
     Still working out some bugs. There are actually two emails associated with an account and for some reason one of them was assigned to the zulip server itself when I registered. Will get it figured out eventually. Also switched shelve over to sqlite.
     feld likes this.
   • Embed this notice
     :blank: (i@declin.eu)'s status on Sunday, 06-Oct-2024 00:21:09 JST :blank:

     in reply to

     • :blank:
     • Sick Sun
     • feld
     @feld @sun a subprocess works too, after setting a password this way, you can log in the mobile app with a normal password putting in the nick@name.tld
   • Embed this notice
     :blank: (i@declin.eu)'s status on Sunday, 06-Oct-2024 00:21:10 JST :blank:

     in reply to

     • :blank:
     • Sick Sun
     • feld
     @feld @sun you could setup a bot that resets passwords without emailing them, and have people log in that way though
   • Embed this notice
     :blank: (i@declin.eu)'s status on Sunday, 06-Oct-2024 00:21:11 JST :blank:

     in reply to

     • Sick Sun
     • feld
     @feld @sun that's what poc.256.lt is, it's just that their mobile app doesn't let you transfer the session from the web to the app
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Sunday, 06-Oct-2024 00:21:40 JST Sick Sun

     in reply to

     • :blank:
     • Sick Sun
     • feld
     @i @feld I also switched it to use gunicorn because I could never get wsgiserver to work right, it always hanged on reading the form data from the request.
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Sunday, 06-Oct-2024 00:23:20 JST feld

     in reply to

     • :blank:
     • Sick Sun
     @sun @i You guys rule, this is so exciting. I am looking forward to us writing up a really nice blog post about Fediverse spearheading the self-hosted chat / discussion alternative using Zulip instead of Discord/Slack
     Sick Sun likes this.
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Sunday, 06-Oct-2024 00:24:37 JST Sick Sun

     in reply to

     • :blank:
     • feld
     @feld @i This was remarkably easy to get working after "i" wrote the bulk of the code for us. Yes I can write everything down I added.
     feld likes this.
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Sunday, 06-Oct-2024 00:29:01 JST Sick Sun

     in reply to

     • :blank:
     • feld
     @feld @i Is there a pleroma oauth scope that only reads the profile information of an account? That would be better than one that gives blanket read permission.
   • Embed this notice
     :blank: (i@declin.eu)'s status on Sunday, 06-Oct-2024 01:30:46 JST :blank:

     in reply to

     • Sick Sun
     • feld
     @sun @feld requesting a more granular oauth scope like read:accounts might work
     Sick Sun likes this.
   • Embed this notice
     ロミンちゃん (romin@shitposter.world)'s status on Sunday, 06-Oct-2024 01:31:41 JST ロミンちゃん

     in reply to

     • :blank:
     • Sick Sun
     • feld
     @sun @feld @i `read:accounts` probably
     Sick Sun likes this.