underscorner

are there any plan to integrate lemmybb as optional web interface ?

@nutomic@lemmy.ml

It has support for partitioning but I had some issues with myMPD at least not handling them well. Each partition is a virtual player / output

mmm, ok, i'll give it a try. For personal use i'm fine driving everything with malp. I was thinking about giving a couple of people the ability to remote play what they want.

MALP gets its artwork dynamically from MusicBrainz or some other service. Same for myMPD. I don’t really bother with managing that locally

for album art malp honour the one embedded in id3 tags. As for artist i keep them blank because if there is an error or two groups with the same name, or a not so known local groups, in malp end up being wrong which i hate.

this one too, for in-house hifi managing, is really great. I never used myMPD though, i'm using the basic http streaming feature and keep controlling from malp / vpn eventually.

Couple of questions for @ptz@dubvee.org

• can myMPD manage different users choosing to play different stuff at the same time ?

• did you manage to have artist images on MALP at your control ? That only fanart is often wrong/inaccurate so i keep them off

oh, cool... you're right. i thought wrong because i tried to send a message from pleroma and from mastodon to @underscorner@feddit.it and didn't get anywhere.

maybe it works just between lemmy accounts, across the many instance.

I don't think we have such a concept in lemmy. I can follow my lemmy user from mastodon (actually pleroma) but if I try to send a DM from there, nothing came to my lemmy attention.

Let's put it this way, an i'm mainly speaking about lemmy itself. A client should remember which post and comment you read already and mark them differently (greyed maybe). If you are watching a community, or an aggregation of communities, unread post and post with unread comments go first, of course.

If you read all the comments the original post should appear after the others, and greyed, but if you expand the thread, you should be able to reply to whatever greyed comments. If a new comment appear on an old post, maybe after a week, you should notice it because the original post is not greyed anymore and back to the highest positions, maybe with a number indicator, something like "3 new message below". If you expand it, you should clearly distinguish the new leaves because they're not greyed.

I mean, it's not science fiction, it's how usenet clients did it in the '90s

also, one thing that drive me mad (aside the difference between an original post and a comment that are treated differently) is that i basically have two options

• to see all messages
• to hide read messages, but this will hide also MY messages

i was very close to rewrite and to send again the request above because of not seeing it anymore anymore and not having a feedback like "ok! sent! published!"

hello, being an user on the same instance, i just gave an eye to federated. Federated means that someone on pixelfed.uno follow those kind of remote accounts. As they are external users and respect Content Warning i don't see any way the instance can do something.

But you can block for single user