Untitled attachment

Notices where this attachment appears

1. Embed this notice
    (mint@ryona.agency)'s status on Friday, 23-Aug-2024 09:05:25 JST 

   in reply to
   @feld Something like that. Wonder if there's any further demand for preemptive activity filtering before ever resolving the pubkeys (resulting in actor getting fetched), if so it should be expanded into proper facility.
   https://git.pleroma.social/mint/pleroma/-/commit/1fbe696c011fea497828fb16f0fd73bc1cfeff6e
   Haven't made any tests yet, partially because I'm not sure how to handle them, partially because rebar throws some cryptic error on my workstation when compiling syslogger.
2. Embed this notice
   NEETzsche (neetzsche@iddqd.social)'s status on Friday, 15-Dec-2023 07:54:42 JST NEETzsche

   in reply to

   I know I just said that I wouldn't work with them, but as a gesture of good will I will submit fixing their federation: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4000

   It lists where I got the information from, who wrote the original commit, and why it's important per ActivityPub standards. They can click merge or they can let their shit stay broken lol

3. Embed this notice
   NEETzsche (neetzsche@iddqd.social)'s status on Friday, 01-Dec-2023 01:06:30 JST NEETzsche

   @hj I got rid of the favicon shit from this one: https://git.pleroma.social/pleroma/pleroma-fe/-/merge_requests/1872

   It just creates a link to externalLink when one is available. If you want it to behave in some other way when it comes to externalLinks, just tell me. I’m not going to argue with you at all on this topic and I’m just going to work toward your specification, so just make it clear what you want.

4. Embed this notice
   NEETzsche (neetzsche@iddqd.social)'s status on Wednesday, 29-Nov-2023 18:47:57 JST NEETzsche

   in reply to

   If you scroll up I made an argument for writing out a spec sheet for the fields you merged some years ago in the interest of interoperability (taking advantage of Elixir’s polymorphism), but it’s not really pertinent to the outstanding MR: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3977

   The outstanding MR is about adding a user-defined url to the scrobbles endpoint, which allows you to do things like this in the FE. (If you click the YouTube link it takes you to the YouTube video)

5. Embed this notice
   NEETzsche (neetzsche@iddqd.social)'s status on Monday, 13-Nov-2023 06:18:46 JST NEETzsche

   in reply to

   It’s in the main repo. https://git.pleroma.social/pleroma/pleroma-fe

   Does the main repo have custom emoji reacts? I think it does.

6. Embed this notice
   NEETzsche (neetzsche@iddqd.social)'s status on Saturday, 11-Nov-2023 12:58:14 JST NEETzsche

   in reply to

   I think adding ListenBrainz and/or Maloja support would be phenomenal, but for me it’s one step at a time. Right now I have an open PR into PleromaBE to make it so that the account/pleroma section in the AccountView JSON has a scrobbles entry, which is an array of the most recent five scrobbles, if any. You can see that PR here: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3975

   I’m doing this because as it stands, my implementation in the FE requires hitting the endpoint, and in order to make it avoid absolutely inundating it, I have to throttle it. This would obviate that completely and allow me to just look at the returned account data normally, as with most of the rest of the API.

   So far Lanodan seems reluctant to add it, saying that Listen is in itself a “hack” that first (he stresses that word) must be redone. Basically, the complaints about scrobbling are that they aren’t supported by FEs, but then efforts to support it get rebuffed.