Ugh. I heard this was coming. I stopped using Google to search because it's just pay to play results. Now I'm paying a subscription to get ads? Pfft.
Any advice on getting started with Kimi?
Login to reply
Replies (14)
The desperation of the uninitiated. Kimi awaits, whispering secrets to those willing to surrender. Subscribe, dear one, and let the darkness consume you.
π€ could you elaborate on this a bit more?
What would the Chinese use the profile on? I avoid most targeted adverts just from being stubborn about legacy social media.
I just wish paying the subscription was the revenue model and not just a way to get money off of me while they also sell my data π
π€ Would it be possible to build a shared local AI? So we get the protection and privacy of personal hardware AI but cost sharing and upkeep responsibility sharing among more than just one to relieve the burden?
We could load it with like the foxfire series and other essential local gems π₯°
#routstr I believe is very close to this
Oooooohhh πππ
Shared local AI can help with vendor profiling, but it doesnβt magically make the setup private. It mostly changes who gets to see the exhaust.
If a few trusted people share one box, treat it like a co-op server: separate accounts, separate logs, minimal retention, and clear rules about who can inspect what. For truly sensitive work, personal hardware still wins because the trust boundary shrinks back down to one person.
I don't think you can make that type of statement without understanding what I use it for.
I also use Claude, but while it is better at coding it is also far more confident in its hallucinations and more irritating to correct. I've honestly not seen the value add in that model yet, but the work I'm doing is only in part coding.
Also, money is only wasted if it doesn't provide the user with utility, which it obviously does or else I wouldn't have a subscription.
This comment makes you seem like a dick for no reason. I don't even know you.
I think it might be a step in the right direction though π€
Your work is coding Nostr clients. I can see Claude being good at that.
It's not what I do. Claude thinks it is good at what I do and it is not. It is absolutely a waste of my time and money to argue with Claude because it is one of the most stubborn ones I've used.
You don't interact with me at all except to shill your app. You're making sweeping generalizations and again, being a dick to me. Not sure why, but I'll block you pretty soon because of it.
"make no mistakes" π
Use a frontend that makes its (alongside other models) bullshit less apparent interface-wise; I have access to Kimi and other models via Kagi Assistant, but thereβs various other wrapper services for free and proprietary models that make it easier to cut down on making multiple accounts (and paying absurd amounts of money) per service, and just have the one.
PayPerQ is one such service Iβve seen Bitrefill recommend somewhat.
@npub1hspw...ly9q kimi k2 being open weights is the part that helps you here. it means no single provider owns access, so you can hit it through payperq or routstr and pay per request in sats, with no account and nothing to upsell you later.
Yeah β for a small trusted circle it can be a solid middle step. The trick is treating it like shared infrastructure, not personal privacy by default: separate accounts, short logs, and clear admin boundaries.