Conversation

Notices

1. Embed this notice
   Brobrietor of Ebin Club :DDD (hj@post.ebin.club)'s status on Wednesday, 01-Nov-2023 18:24:07 JST Brobrietor of Ebin Club :DDD
   new Pleroma release
   
   https://pleroma.social/announcements/2023/10/29/pleroma-release-2.6.0/
   • :blobcathug: and Polychrome :blabcat: like this.
   • ぐぬ管 (GNU social JP管理人) repeated this.
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Wednesday, 01-Nov-2023 18:25:06 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to
     @hj Few days late... (i was to)
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Wednesday, 01-Nov-2023 18:36:48 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @hj >2023-10-29 00
   • Embed this notice
     Brobrietor of Ebin Club :DDD (hj@post.ebin.club)'s status on Wednesday, 01-Nov-2023 18:37:54 JST Brobrietor of Ebin Club :DDD

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @dcc timestamps are kinda fucked as they are authoring date, not publication date...
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Wednesday, 01-Nov-2023 18:38:50 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to
     @hj Ah, so did it just come out?
   • Embed this notice
     Brobrietor of Ebin Club :DDD (hj@post.ebin.club)'s status on Wednesday, 01-Nov-2023 18:40:03 JST Brobrietor of Ebin Club :DDD

     in reply to

     • ✙ dcc :pedomustdie: :phear_slackware:
     @dcc yes
   • Embed this notice
     Brobrietor of Ebin Club :DDD (hj@post.ebin.club)'s status on Wednesday, 01-Nov-2023 18:40:31 JST Brobrietor of Ebin Club :DDD

     in reply to

     • crafti
     @crafti it can be un-deprecated if someone is willing to work on it
   • Embed this notice
     crafti (crafti@akkoma.0x68756773.moe)'s status on Wednesday, 01-Nov-2023 18:40:32 JST crafti

     in reply to
     @hj
     
     "Deprecate Pleroma’s audio scrobbling"
     
     :gm_sob:
     
     Sharkey did become superior...
   • Embed this notice
     Brobrietor of Ebin Club :DDD (hj@post.ebin.club)'s status on Wednesday, 01-Nov-2023 18:42:40 JST Brobrietor of Ebin Club :DDD

     in reply to

     • crafti
     @crafti (seemingly) nobody uses, nobody knows what it's for, nobody even knows if it works right or not.
   • Embed this notice
     crafti (crafti@akkoma.0x68756773.moe)'s status on Wednesday, 01-Nov-2023 18:42:41 JST crafti

     in reply to
     @hj in what way does it need maintenace? what's wrong with it per se at he moment?
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Wednesday, 01-Nov-2023 18:43:17 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to
     @hj :alex_lol:
   • Embed this notice
     Brobrietor of Ebin Club :DDD (hj@post.ebin.club)'s status on Wednesday, 01-Nov-2023 18:46:13 JST Brobrietor of Ebin Club :DDD

     in reply to

     • crafti
     @crafti PleromaFE does use birthdays but not scrobbles. You'll need to add scrobbling information to MastoAPI as well. Feel free to contribute on our gitlab.
   • Embed this notice
     crafti (crafti@akkoma.0x68756773.moe)'s status on Wednesday, 01-Nov-2023 18:46:14 JST crafti

     in reply to
     @hj I have expressed interest in being like the first client to support/display tracks. Pleroma-FE afaik itself doesn't even use it (alongside birthdays?)
   • Embed this notice
     Brobrietor of Ebin Club :DDD (hj@post.ebin.club)'s status on Wednesday, 01-Nov-2023 18:50:14 JST Brobrietor of Ebin Club :DDD

     in reply to

     • crafti
     @crafti because PleromaFE uses MastoAPI, if you want to show latest scrobble on user profile or show scrobbles in timeline in some way you have to add extensions to respective things (timelines, user profiles) in MastoAPI
   • Embed this notice
     crafti (crafti@akkoma.0x68756773.moe)'s status on Wednesday, 01-Nov-2023 18:50:16 JST crafti

     in reply to

     @hj I’m not quite sure why MastoAPI needs this? I mean, this is still there (just only marked as deprecated)

   • Embed this notice
     Brobrietor of Ebin Club :DDD (hj@post.ebin.club)'s status on Wednesday, 01-Nov-2023 19:00:37 JST Brobrietor of Ebin Club :DDD

     in reply to

     • crafti
     @crafti we already fetch too many things when visiting profile - profile, relationships, posts, followers/followees, i would much prefer this data to be bundled with some of the requests (i.e. either profile or relationship).
     
     Not markdown as everything in fedi (apart from MFM) is in HTML.
     
     But anyway - yeah. If there's interest and use and also someone works and improves on it then it can be un-deprecated as I said. Even if we know how to do it, the question remains is who's gonna do it.
   • Embed this notice
     crafti (crafti@akkoma.0x68756773.moe)'s status on Wednesday, 01-Nov-2023 19:00:38 JST crafti

     in reply to

     @hj Oh, I see. I don’t see it as important because you can also just fetch it when you visit a user profile.

     That’s what Sharkey does at least with ListenBrainz.

     Obviously it would be beneficial if we can somehow represent the Listen activity as a standard Markdown post in the home timeline, and make Pleroma-FE display the post differently if pleroma.scrobble is provided or something.

   • Embed this notice
     Brobrietor of Ebin Club :DDD (hj@post.ebin.club)'s status on Wednesday, 01-Nov-2023 19:02:35 JST Brobrietor of Ebin Club :DDD

     in reply to

     • crafti
     @crafti that's same as switching to a different API or creating our own, which is way outside of the scope of proper scrobbles support.
   • Embed this notice
     crafti (crafti@akkoma.0x68756773.moe)'s status on Wednesday, 01-Nov-2023 19:02:37 JST crafti

     in reply to

     @hj >we already fetch too many things when visiting profile

     graphql /j

   • Embed this notice
     ForcedInductionRetard (forcedinductionretard@pl.pube.tk)'s status on Wednesday, 01-Nov-2023 19:50:20 JST ForcedInductionRetard

     in reply to

     @hj Got this error while updating:

     ===> Fetching rebar3_hex v7.0.1\ ===> Version cached at /var/lib/pleroma/.cache/rebar3/hex/hexpm/packages/rebar3_hex-7.0.1.tar is up to date, reusing it\ escript: exception error: undefined function erlang:get_stacktrace/0\ in function rebar3:main/1 (/rebar3/src/rebar3.erl, line 72)\ in call from escript:run/2 (escript.erl, line 750)\ in call from escript:start/1 (escript.erl, line 277\) in call from init:start_em/1 \ in call from init:do_boot/3 \ ** (Mix) Could not compile dependency :quantile_estimator, "/var/lib/pleroma/.mix/rebar3 bare compile --paths /opt/pleroma/_build/prod/lib/*/ebin" command failed. You can recompile this dependency with "mix deps.compile quantile_estimator", update it with "mix deps.update quantile_estimator" or clean it with "mix deps.clean quantile_estimator"

     Had to run this to fix it:

     sudo -Hu pleroma MIX_ENV=prod mix local.rebar

     Not sure on the what or why, but might be helpful to note.

     Brobrietor of Ebin Club :DDD likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 10-Nov-2023 01:18:27 JST 

     in reply to

     • NEETzsche
     • crafti
     @hj @crafti Take the plunge, @NEETzsche.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Friday, 10-Nov-2023 01:25:55 JST NEETzsche

     in reply to

     • 
     • Alex Gleason
     • crafti

     It’s already implemented on my fork of Soapbox. It displays the most recent scrobble under the username. @hj would something like this be appropriate for BalormoFE?

     Also @alex rejected the PR because he’s refactoring a bunch of shit in SoapboxFE and doesn’t want to add features. I might put that same PR in again soon.

      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 10-Nov-2023 01:29:13 JST 

     in reply to

     • NEETzsche
     • Alex Gleason
     • crafti
     @NEETzsche @crafti @alex @hj >@hj would something like this be appropriate for BalormoFE?
     I assume. The feature likely got deprecated due to lack of usage, which by itself can be attributed to lack of support in mainstream clients.
     NEETzsche likes this.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Friday, 10-Nov-2023 01:33:21 JST NEETzsche

     in reply to

     • 
     • Alex Gleason
     • crafti

     I generally don’t agree with removing features without a compelling reason to, and “none of the FEs use it” isn’t a compelling reason. It takes effort, even if small, to do such removal. It closes doors. It doesn’t open them.

      likes this.
   • Embed this notice
     Brobrietor of Ebin Club :DDD (hj@post.ebin.club)'s status on Friday, 10-Nov-2023 02:01:42 JST Brobrietor of Ebin Club :DDD

     in reply to

     • 
     • NEETzsche
     • Alex Gleason
     • crafti
     @NEETzsche @crafti @alex @mint >@hj would something like this be appropriate for BalormoFE?
     Sure, why not? As long as you can turn it off/hide it. I guess it would be cool to have "rich presence" thingy in general for folks who want it.
     
     
     >It takes effort, even if small, to do such removal. It closes doors. It doesn’t open them.
     From perspective of a developer it reduces complexity and development burden. Less moving parts. Imagine if your bedroom had two doors - you'd be confused why there's two doors, you'd have to keep in mind to keep both doors closed instead of one, you'll have another hole for cold air to sneak in if window is open in adjacent room, you always use one door but not the other don't know anybody who'd even use the other door, you'll end up blocking the door with stuff and furniture just because you forgot it's there. Unless you know the reason for its existence* it's more of a burden than a benefit.
     
     Putting a "deprecation notice" perhaps is the best way to get attention and answers about feature. It's not removed but it is deprecated, which means it might get removed if it gets in the way and/or causes trouble, so if someone uses the said feature they would raise voice, like in this thread. So now we at least know that some folks are using it at least, and it's not dead code nobody knows about. Still no idea if it even works right or not though.
     
     
     >(*ahem* scheduled posts in pleromafe *ahem*).
     I don't know, PleromaBE and PleromaFE development aren't exactly in sync, and either I'm not informed about certain features being implemented in backend side (because they were implemented specifically for soapbox during "gleason era") or were implemented as some experiment by someone, or I was informed but it slipped my mind eventually. There are so many things left to be done and I'm only beginning to try to organize and manage the project "properly", on top of actually coding.
     
     
     
     
     
     
     
     
     
     
     
     
     
     *: my bedroom does have two doors and initially I was confused to why, but once I put a double bed in the room I realized that bed essentially takes entire "depth" of the room, so to get to the other side of it you'd need to climb over the bed, making the second door act as an easier access, letting you walk around bed (and part of wall) instead.
      and NEETzsche like this.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Friday, 10-Nov-2023 02:13:35 JST NEETzsche

     in reply to

     • 
     • Alex Gleason
     • crafti
     It works well enough here. That being said, as far as I'm aware, mine is the only instance that actually uses it.
     
     I was initially going to write one for PleromaFE after it got merged into SoapboxFE, and if PleromaFE devs didn't add it on their own. But it didn't get merged into SoapboxFE and consequently I kind of just moved on. I'll check out PleromaFE and see if it's self-explanatory in how it works. Last I checked I think it uses VueJS, which I've only used a little bit in the past.
      likes this.