Quiblr is purely a frontend. It creates a standardized experience across Instances (including the feed personalization). Im not super familiar with Kbin. If it uses the same API as Lemmy then it should work.
Long-term, I'd love to integrate more and more fediverse platforms into Quiblr
Thanks! I work on Quiblr in my free time as a side project. I've never managed an open source project on my own, but I'm working with a buddy who has experience managing open source projects. I'll let you know!
Gotcha. That should be an easy addition. I'll see if I can push an update tonight!
Edit: I noted this in a separate comment, but I added the instance info to the communities page + the original post url to the Post Details page (via the 3 dot ellipses)
I tried to differentiate voting vs. "like/dislike" for the algorithm as to not confuse users who think they are logged in. I can put more thought into how to make this a bit more intuitive
Quiblr is built as a progress web app (PWA) so it uses native app components. The benefit is that it is faster and easier to manage multiple code bases. But the con is that it doesn't have all the same benefits as HTML. I added an "open posts in new tab" feature in the settings
I like the idea of added more body text in the post itself. My fear was that it would make the feed look too crowded, but I can take second look at it
I love the tooltips idea
The 3 dot ellipses has a Post Detail section for each post. Maybe this could be a good place to add the link back to the original Instance url.
I like the scrollbar idea. I think this could make sense as an optional setting because I personally don't prefer the scroll bar but I want to include it for users who do prefer it
I added a refresh button for users using the PWA version (since they don't have a refresh button in the browser). Maybe something like "pull down to refresh" could work on
You should be able to press the "<" back button when viewing a community on mobile or just back in your browser. Both should take you back to your feed. Let me know if it isn't working as intended
I'll have to see the API allows for removing downvoted items from feeds. I can try to get creative if needed
Edit: Added tooltips for post buttons + original url on the Post Detail page. I will continue to update this comment as I work through other additions in this list
Your comment made me smile! I've worked hard to make Quiblr a platform for the fediverse to be clean, modern, and accessible. Basically - remove all the friction that generally comes with fediverse apps
Not open source (at least yet). Quiblr has been a side project for me and I've never managed an open source project before lol I'm talking with a buddy on how that could work though because he manages a few open source projects
Also, I added an about page in Settings >> For You >> Learn More
Thanks a bunch! It took me a while to craft the solution to make sure it was both effective + private. I was originally inspired by Canopy. They built a news aggregator with private & personalized posts a few years back and the idea sat in my head.
To answer your question(s), there are quite a few signals that big tech uses to recommend content. Not all of them are privacy invasive (or at least they don't HAVE to be). My approach was to do thorough research on the different signals used by big tech to make their recommendation engines, and just build ones that 1.) were possible given fediverse API limitations and 2.) private. I had to craft some novel approaches to make it work but I'm pretty happy with the outcome!
One of the biggest differences between the "big tech" approach and Quiblr's is that most big tech does not keep data simply on your device. They store it in datacenters to build large social-webs to essentially cluster users (and push more relevant ads).
But I was able utilize many of the other signals used by big tech (e.g. communities you engage with, metadata of content you read, dwell time, post/comment/vote activity) and I designed it to work offline with no servers.
You make great points. I think this should be one of the top goals for frontend Lemmy devs. Most users are not super technical. The fediverse (lemmy included) should work with minimal friction to be accessible.
If you're open to it, I'd love to get your feedback on my Lemmy frontend's onboarding and overall user experience. I've been trying to make it simple, effective, and accessible. I can DM you!
I built the Quiblr web app. I love the idea of being able to filter results for a given instance! I will see if I can push an update tonight
Edit: I pushed an update to implement Advanced Search options on the Communities Page. Given how the API works, community IDs are different between each Instance so you can't view the post feed on another Instance's community -but- I made a solution that lets you VIEW the communities on different instances (regardless of your home instance). If you are not signed in, you can change the instance with a single button push.
I appreciate the kind words. And yes, I included a mechanism to constantly refresh and clean up recommendations so that it doesn't use too much memory