80
  • Edited

carl

I mean - you can wait as long as you want to adopt an opt-in feature right? Just wait until it's more mature if that's your sentiment. I'm interested in this feature. I'm interested in the sentiments of Kagi subscribers, and I'd be happy to help dig in and help refine in whatever way I can.

I... Carl I was going to skip over the second paragraph, but it just isn't very .. nice. I can relate to your frustration very well, but one person's activists are another's friends. This is rude and defeatist. Play nice.

I do like the lens idea. It would be amazing if lens (or something like it) had some basic analytical tools. (does it?).
That being said, I'd prioritize search context. Just even right up next to the other site intel. Give me user rankings, maybe a group-by. Happy days.

    • Edited

    carl

    Yeah i wasn't even going to click on the domain insights link, because within this context i honestly don't care what it says. Scrolling the top 10 or 20 sites of each of category quickly informs me that those choices are very well aligned with my own. Perhaps I have found my niche. The "censorship engine" so to speak works. I would like to be able to collaborate with these fine folks within a search context.

    I will tell you though, you may have a future in marketing - Kagi: "has values that are different from most" search engines. I love it.

    Just to be crystal clear: what I want is a collaborative capability. The current composition of the user base is an irrelevant but welcome surprise.

      maurs I mean - you can wait as long as you want to adopt an opt-in feature right? Just wait until it's more mature if that's your sentiment. I'm interested in this feature. I'm interested in the sentiments of Kagi subscribers, and I'd be happy to help dig in and help refine in whatever way I can.

      Yes, but if it's implemented right now it might have unwished for consequences, due to the unbalanced user base. It will determine what kind of customers will be attracted to Kagi and what kind of customers will avoid Kagi. Because word on the web will be "This search engine is great because you can block and pin results, by the way there's also communal results ranking"

      Then they check out Kagi and the communal rankings and see that among the blocked websites are Facebook, Instagram, Twitter, Amazon and LinkedIn. Making Kagi useless for almost everybody except a small subset of people.

      I block Twitter myself, but I don't think most people will want such an important platform blocked from their search results. Rather they will consider Kagi to be broken as a search engine. Even if they themselves have turned on communal rankings, because that's what everybody online said was so great about Kagi...

      Any new online project will attract a disproportional amount of activists, including Kagi. I'm not referring to you, btw. I really think it's better to wait until the user base has grown and became more broad before implementing these things. As for the political leaning: there are hundreds of countries in the world, the aggregate rankings as of today would mostly cater to people who are aligned with one particular political party in one particular nation. That would be limiting for Kagi, who aims to cater to an international crowd.

        I think the difference is that if the tool is built to learn what I would like, not just assume I am like the rest of Kagi users, this problem should not manifest. Now, users who are substantially dissimilar from the Kagi norm (if that’s even a thing, notice lots of sites are commonly boosted and commonly blocked) will benefit less because of lower statistics. Is that a huge problem? I don’t think so: as proposed above, it seems that substantial value could be derived by leveraging the usage of a single high volume user on their own results.

        There could be an issue with a self-bubble in that case, but we can already do that with manual tools.

          • Edited

          carl

          I sense a lot of... fear of the future/unknown/internet-populus floating around this conversation, and I think it's driving a lot of assumptions.

          I agree that there are a lot of branding and bias management issues surrounding this concept. My opinion is that with some creativity and a well honed perspective, a lot of the perceived blockers can be used as advantages. If they are no longer treated as blockers, then progress can be made, rather than wait-and-seeing the feature to completion.

          For Example: I don't assume that the terminus of this feature will not support multiple pools of site rankings that a user can create their own consortium from. A user may be able to select from a menu of sentiment pools, or be matched to a pool(s). I have no idea what this would look like, but i have several ideas surrounding the concept.

          I loathe to mention it, but just think about reddit within this collaborative social search context. They have many many maaaaany self selected groups based around the core concept of up/down votes.

          I will admit that I hand-wave away the activist element, and it may be bigger than I realize. My assumption is that features of this nature should be architected in such a way that is tamper-resistant. Given the kind-of non-single-kagi-user-pool thoughts I've been chewing on lately, I also suspect that a majority subset these 'activists' are just maybe the angry-pitchfork-rabble sentiment group. Ok .. welcome - knock yourselves out. here's how you socialize about where to throw pitchforks... so to speak. (or perhaps more accurately, here's what pitchfork-wielders up/down doot most 😂 )

          As far as timing goes... I also have a different opinion. One could also say that the small tight knit nature of the current user pool lends itself to 'simple iterative' feature delivery at a time when growing-pains might be less impactful. Perhaps this feature will have refined to the point that it's ready to support the diversity of the internet, before said diversity shows up at the front gate. The small nature of the user group might be an advantage from this perspective.

          calm-tea6189

          I think that this is an extremely relevant perspective in this context, and I thank you for sharing it.

          I'm not sure if a feature like this can ever be advanced enought to "just work" in the background without even realizing, but I think maybe. There are definitely degrees-of-feasibilty between manual and magic through, and I think that it's very possible that 'really-intuitive' is deliverable.

            To summarize this thread, would a simple to use option be to be able to enable 'wisdom of the crowds' basically downranking sites that other users have downranked automatically. This would work well for spam, the tricky part is political content (left vs right for example as this is personal preference that we wouldn't be able to tell).

              Vlad

              I like the summary, but I have one suggestion. You called out downrank specifically, and I think that there might be danger/additional cosideration to be made if this was intentional.

              I intuit many fewer 'social dragons' with an upvote-only solution. Upvote/Downvote functionality is a litle more challenging but perhaps balanced. Downvote only is perhaps an angry-mob-summoner for a few reasons.

              I like "wisdom of the crowds" - I think it's a good perspective.

              • Edited

              Vlad

              I wince a bit when the conversation shifts to managing negative impacts around politics and user bias. My personal strategy for socially charged features such as this, is to maintain awareness and rigorously architect a solution that bias-free enough that there's not really anything in the delivery pipeline to point at as evil or unfair.

              examples: (i'm just exploring possible foibles, not suggesting implementation here)

              1: I choose "users who love github" as a sentiment pool to enable. I review the upvote-only list and see that stack exchange and some others are also prioritized. Why isn't devdocs.io listed? dunno, maybe i should upvote it and get others checking it out!

              2: I choose "users who love github" as a sentiment pool to enable. I review the upvote/dowvote list and become offended that devdocs.io is deprioritized. the nerve of these kagi users, would do such a thing. I'm upvoting it.

              3: I can't wrap my head around what a downvote-only capability would look like - insert downvote-only scenario here. why is devdocs.io deprioritized? this is ludicrous. it's just a reference agregator. I might just go chew someone out on kagifeedback. this is unacceptable.

              I chose to use the "Users who also love" sort of paradigm very intentionally earlier in the thread. It's hard to target percieved political bias when the dimensions of grouping have nothing to do with politics. Sure there would be biases within user's shared sentiments, but they might be bucketized in a way that diminishes that impact perceptually and functionally.

                Vlad Just be aware that such communal rankings can be what defines Kagi, which is in a sensitive state of growth.

                I'd like to toot my own horn again, and beat my dead horse for my "Super Lenses" suggestion: https://kagifeedback.org/d/5051-suggestion-super-lenses-portals

                It would enable people to subscribe to rankings and avoid associating Kagi strictly with one political party, one nation and one distro (Arch Linux).

                  This is dangerously close to making Kagi the next Reddit. We assume that all users have same search behaviour instead of “personalised” ranking. The strength is my Kagi is MY Kagi. I pay for it because the rankings are what I prefer, not what others do.

                  Google already does this based on other users behaviour. They float ads that you are likely to click if you searched X because they know more users that look for X will be tempted to click an ad.

                  When Kagi grows, bots might take over (paying for accounts won’t be an issue) because you can deploy bots to keep floating certain webpages or sources as “crowd prefered”.

                  Why would anyone go to those lengths? Because if Kagi is the future of search, it will not be liked by sites that make money by serving ads to more people. So to get more people to click on that site is by floating it back to the top. Right now it doesn’t even exist on my search list but what will stop this happening?

                  Also “personalised search” is my Kagi USP.

                    • Edited

                    marcel001122

                    I agree about reddit, and feel like Reddit is kind of a cesspool with a handfull of decent subreddits floating at the top nowadays. I don't want that, but I think that an up/down vote option is a far cry from user submitted and commented links.

                    Try to keep in mind that kagi's user base is not a captive audience, and I don't think it will be treated as one in the future. Kagi is also (hopefully) not sneaky and will not scheme against the user. This defangs the ad revenue generators a bit, and also disincentivizes bot voters quite a bit. This changes my own view on the overall situation.

                    Kagi (bless them) kinda upsets a lot of the current predatory business models when they behave as a faithful actor, rather than a two-faced adversary.

                      Being able to create shareable and modular lists of adjustments to your rankings would be nice for crowdsourcing the labor of curating results.

                      This builds off my "bug" report and this feature suggestion about marking sites as AI generated together with my experience using Bluesky's Moderation Lists

                      Note: I know there's Lenses which can be shared, but their functionality is really meant for, as the name implies, very specific and repeated search situations.

                      Ranking Lists would be groups of adjustments that could be subscribed to and merged into your existing rankings (where your "global" adjustments take priority). This way if it would be possible for people to say highlight a collection of high quality blogs or provide a good starter kit for addressing SEO mills about a topic they follow (programming is obvious, but it easily applies to gardening, cooking, and hobbies generally).

                      When making an adjustment on the popover there would be a way of adding it to a list (graphic design is, in fact, not a huge passion)

                      A ranking adjustment could be on multiple lists, but (and I recognize this might be controversial to some people) the adjustment itself would be global to your account. If you're deeming a website useful or not in general it's context shouldn't matter. That's where Lenses would come into play.

                      Because of that I could see the current Personalized Results settings page continuing to exist but having a way of seeing the lists a domain is on (maybe the same list selection interface as the popover), plus an additional detail page for managing/viewing lists individually. More or less replicating what Bluesky has going on.

                      Some design thoughts:

                      • There would need to be a visualization indicating if a modification you've made overwrites something on a list or if a domain was added by a list and not by you
                      • Conflicts between lists (since it's not just "here's a list, take one specific action" as with Bluesky) would need to be addressed
                      • It may make sense to limit lists to Raise and Lower with no Pins or Blocks or making accepting those an option, similar to how Bluesky has Mute or Block subscription types

                      I'm sure there's a world of technical reasons this would be difficult to implement in the backend, but I think it would be a great addition to the platform!

                      P.S. the Personal Results settings page uses a Select for the selected adjustment, but the Domain Leaderboard lets you choose using a Radio Button Group

                      • Luis replied to this.
                        7 days later

                        dysiode thanks for the detailed explanation. I believe the problem you're addressing is the same discussed in this thread - https://kagifeedback.org/d/4502-opt-in-collaborative-shared-result-ranking ; I'llmerge them unless I misunderstood something (?)

                        I like this explicit approach of shareable lists. This is a topic we're going to spend some time analysing and defining next steps. We'll keep the main thread updated.

                        Merged 2 posts from Sharable Ranking Adjustment Lists .
                          16 days later

                          This is a pivotal feature and Bluesky is showing/leading the way. Their approach is a good proof that users are sensible to ranking algorithms & will use them.
                          This helps Kagi provide more value & personnalisation without associating itself with an idea or another.
                          Getting the ball rolling on "Custom Lenses SDK" early on will add another dimension to Kagi, I guess a good part of the userbase is tech literate but building a strong dev community & open source ranking algorithms must take a little time !

                            10 days later
                            • Edited

                            It's interesting to see the comparison with the Bluesky collaborative ranking tools. This is a critical feature of decentralized social media: block lists, promote lists, etc. Same with adblockers... domain reputation is everything. uBlock Origin is only as good as its block lists. It would be amazing if Kagi to published these kinds of lists.

                            It would be something like a Private Tracker: it's a database curated by and for a defined, trusted population. In this case, people who care enough about search quality to pay for Kagi. Kagi would need to be very thoughtful about how to receive trusted feedback from users without reducing privacy. Privacy Pass might be a valuable foundation for this.

                            Lets see if I can state this as clear user stories...

                            As a Kagi Subscriber, I want Kagi's high-quality signals about publisher quality & relevance available on other platforms. When Kagi thinks a domain is used for spam or other malfeasance, I want my adblocker to block that domain. When Kagi thinks a user on a decentralized social media platform is fake account, spammer, or otherwise fraudulent, I want that user to be automatically blocked from my feeds on that platform.

                            As a Kagi Subscriber and decentralized social media user, I am willing to share my personal moderation decisions pseudonymously with Kagi in return for access to blocker feeds/moderation lists. I don't want Kagi to build a database of my social media behavior explicitly tied to my account, but I'm comfortable sending a stream of block/unfollow/report events tied to a stable ID that is not otherwise linked to my Kagi account. I expect that Kagi will use this identifying information exclusively to prevent abuse of the reporting service.

                            As a Kagi Subscriber, I want the ability to search social media at scale, including the long tail of decentralized social media instances. I expect these searches to be ranked based on high-quality signals. Users who share links to low-reputation domains or are frequently blocked by other Kagi users should be downranked.

                              6 days later

                              pbronez I'm not a decentralised social media user but I do observe what goes on on them, and frankly the community blocklists seem to be a total shitfest, if you'll excuse my language. I've seen competing blocklists, rivalry between blocklist maintainers, said warring maintainers adding each other and anyone who reacts with their rival to blocklists, etc.
                              The amount of people out of Kagi's 40k users who are going to not only have an account on decentralised social media, actively curate a blocklist (e.g. I'm on X and don't block anyone, even accounts I find annoying/distasteful), AND are willing to connect their SM to Kagi I'm willing to bet is less than 100. Remember the 90/9/1 rule?
                              Simply put, I don't want my search results influenced by a tiny group of users of (not to be offensive) completely unknown biases, community drama, mental stability, etc. Of course one can then say that I don't have to enable this feature, but then why build it? I'm sure many people feel the same way, Kagi is billed as an unbiased, you-first search engine after all. I'd rather see dev time that would be spent on this going towards improving search in other ways.

                                Feature: The ability for users to flag a search result as AI slop, or clickbait.

                                Outcome: Improve search result quality.

                                User Side:
                                Users could click the three dot menu next to a search result and instead of hiding a result, they could flag a search result as AI slop/Clickbait. Flagged websites would then be hidden from a user's search results in perpetuity.

                                Function:
                                To offload workload from Kagi devs, flagged sites could sent to a community review portal. Individual members could review a site and, if a site meets a certain threshold, it gets filtered into admin/dev portal for final processing. An incentive system could be utilized to attract and retain community volunteers, like flair, badges or discounts.

                                Complications:
                                The most privacy-focused way that this could work is that just the page is displayed for review. The best way that this could work is to display the flagged site plus the search query, though this could be used for possible user identification.

                                Notes:
                                A resolution system should also be added by site owners who wish to dispute an AI Slop/Clickbait label. The dispute process could function the same as the takedown process (Community > Dev > Action)

                                6 days later

                                It would be nice to be able to turn this off, and/or to be able to set exceptions.