Comment on Unified Fediverse App - a browser solution?
lime@feddit.nu 2 weeks agoWhy don’t the highest use rate clients for Fediverse services look like standard browsers?
they don’t? i feel like they pretty much do, considering they’re all web pages.
do you have a central log of notifications you can access via your desktop?
every desktop environment i’ve used in the past 10 years has this, it’s basically been the default from windows 8 forward. GNOME puts them front and center in a dropdown in the middle, windows and deepin has a sidebar, KDE pops out a whole window for them.
basically the crux of it is what you want to do with your notifications. for me, a notification is an indicator that someone wants something, so the action it should perform is bring me to whoever it is. if that’s all you need, then you’re already there because every client i’ve used already has notification settings that allow you to filter stuff.
the reason i’m asking questions is that you’re all over the stack here. you’re talking about a user chrome, then you’re talking about consolidating messages, then about notification filters. i think it can all coalesce into something if you start from the capabilities of activitypub itself. it’s basically a messaging system at its core, with clients all deciding how to handle the contents of each message. i’ve long thought that neither twitterlikes or redditlikes actually play to the strength of the protocol, and that activitypub needs some sort of killer app to really shine. if you think you have something, you should let it form into a coherent idea and present it.
Coopr8@kbin.earth 2 weeks ago
I'm going to have to dive into push notification handling, I basically minimize the use of push notifications at my desktop level to only push work related content, and use the notification system of the clients to handle the "recreational" content which leaves me checking lots of platforms separately.
It makes sense that there should be the ability to create separate profiles with different filters and behaviors at the push notification manager level, I just haven't thought to look into it before.
Regarding killer apps for ActivityPub, and unified clients, I have a second idea which I didn't want to cloud this thread with that seems somewhat inevitable that will require a central portal with access to all services (and accounts?). That is a single publishing UI where the user creates/uploads any piece of content and then it suggests what venue/service/account to publish it on and related add-ons like hash tags, etc. With the Fediverse the APIs are open and multiplatform publishing clients (like FediPlan) already exist, so a level of light ML/AI for publication seems inevitable.
The next level of this, and what could be a "Killer App" is spontaneously generated affinity grouping via content aware publishing, meaning that the publishing client not only suggests where the posts should go, but also has a metalayer where the publishing clients instances "gossip" about the content being published and then create brand new "spontaneous" venues to publish that content in alongside other similar content being published by other users. Suddenly your text post about a super-niche interest or problem is pooled with posts by other users on the same topic, and bam you have a relevant discussion group of commenters/posters.
Problems of course arrise from this re:advertisers/promoters as well as unsavory/harmful mutual interests, but to be honest I think this is more of an inevitability than a possibility, so getting ahead to architect it in a way that minimizes potential abuse before the corpos get on it is probably a good idea.
lime@feddit.nu 2 weeks ago
hm, i think there’s some confusion regarding AP here. there’s no “deciding where things should go”; every frontend can “see” every type of post, even if the format is off. what you’re describing by is essentially how it already works, no multiple accounts needed. the frontend just needs to decide how to handle it. for lemmy-to-masto the handling is pretty basic, you can see it by going to a mastodon server and searching for your lemmy account (formatted as @yourname@yoursite.blah).
for the “gossip” thing, every server already publishes every new thing. it’s up to other servers to decide how to handle it.
regarding the automated tagging system, i actually had a similar idea recently. i think a big flaw with lemmy/mbin/piefed is the keeping of communities from reddit; if the already extant tags were used instead, the cross-posting problem would go away completely since comments would be attached to posts rather than communities.
anyway: it would not be difficult to just use words in a post to assign it tags, but i question the usefulness of doing that. some sort of analysis would help, as you say, but then we’re introducing nondeterministic behaviour. there is definitely a discoverability problem on fedi, and something like this could definitely help with some polish.
Coopr8@kbin.earth 2 weeks ago
Regarding "where content should go", I mean like which community to post a lemmy post in, or which account to post to if a person manages multiple topical accounts (or accounts in different instances specialized for specific services), or whether to format it for loops vs peertube for video, etc.
Gossip wise, I'm imagining compressed data posted in a format only intended to be ready by the automation systems which happens before the suggestions are made, so that the suggestions can include dynamicly grouping content before publication by appending the relevant metadata/format (like posting in a lemmy community).
lime@feddit.nu 2 weeks ago
the formatting is up to the client that displays the content, interestingly enough. AP just has a “message type” fields and different clients care about different types.
i’m not really sure what that gossip method achieves. surely if it’s just post metadata we’re talking a hundred bytes at most. running it separate from the main feed seems like it would just bork every single AP client that tries to use content published by this hypothetical one.