HN user
The telepathy tapes.
Don't want to give away too much but it has to do with non verbal autistic people with... Special abilities.
Non fiction, and they try to conduct tests to be as scientific as possible.
Framing the ledger as the problem seems strange. It's more accurately the solution. The problem being how you transfer value through the internet in a trusted manner.
Re: privacy though, there's many solutions. Single tailored chains for privacy, mixers, encrypted tokens, permissioned chains, etc.
In my experience, privacy, while important, is not something users actually care about enough to demand a solution for. Most web3 users today just want to degen and gamble, and they're okay with KYC to do so.
The vibe coder doesn't know what they don't know, so they rely on the LLM to make decisions.
The Software Engineer will know what decision to make even without looking at the code.
I have a telegram bot, and I used to have it read message in a group chat to detect the language, and if it wasn't English, it would use gpt5 nano to translate.
To save on inference, I had Claude create a lightweight typescript library to handle translations and detection. Now I get the previous functionality for 200mb~ ram versus paid API credits.
I also built a home assistant menu bar in osx, let's me easily monitor activity, toggle devices, view cameras, etc.
No it doesn't?
You can run stock, or any fork simply by providing the URL of the version you want to run.
Where exactly is the restriction?
every product manager fundamentally misunderstands that users just want a chat window for AI,
I would actually argue chat windows are terrible ui/ux for most cases and users. It does the opposite of `don't make me think`. Too much potential for user error.
Not saying there shouldn't be any LLM integration/features, just that it should be in the form of a button press or something (familiar ux), not the same chatgpt interface that all the early apps are trying to mimic for no good reason.
Vibe coding will simply be the new "no-code".
A tool for non technical people to build things within reason.
I don't know how you're trying to define vibe coding, but I would definitely put it as more of a pejorative/negative term.
I have 20+ years of coding experience, I use coding agents well, and I'm not a vibe coder.
I would also bet that vibe coding will never become good enough to replace me because the models will never have enough context window for an entire repo of a complex app. LLMs can output code for you, but coding is only part of the job.
Disagree, I think vibe coders should become synonymous with no-code and continue to be somewhat of a pejorative.
I don't like the term vibe engineer, but do agree there needs to be a term to signifiy the difference.
It's also possible in the future just being called a developer/engineer already implies you use coding agents and the people who do it "by hand" will not be the norm.
It's BM to plug your own stuff in someone's launch thread.
it depends on your usecase, but i tried both coolify and caprover.
ended up going with caprover because i can more quickly spin up a nodejs app on there with git hooks (so it builds on each commit to a specific branch).
both offer this functionality, there's just less friction on caprover. but coolify is probably more extensive.
it seems like a blockchain doesn't make sense for this use case.
given, most traffic will likely be from ai agents, does it make more sense to try to hack agents into using credit cards, having shared social security numbers, opening bank accounts, dealing with chargebacks and slow settlement?
or
does it make sense to use technology that is
- internet native - programmable - near instant - secure - permissionless
the volatility issues are resolved through the use of stablecoins.
To be fair, big screen has been around since the oculus DK2 days, so they had a lot of time to iterate.
But ya, apple should be more Dev friendly overall.
shouldn't it just take advantage of what's already there?
It's not a good idea to have any coding agent put unnecessary amounts of lines into the context window in order to understand your code base.
Performance of all llms drop drastically when the context window is filled or full. The purpose of being more specific with your prompts is that you spend a little bit more tokens up front to make the task a lot more efficient and more likely to result in success.
At least that's how it is today. We're probably a breakthrough or two away from the type of vibe coding experience non-coders want. Or it may never happen, and the developers who have coding knowledge will be the only ones to fully utilize coding agents and it will only become more powerful over time.
What is the incentive of someone to create an app and just pay for all the hosting involved?
Also, does everyone need to have their own domain name in order to have an identity cuz that seems like a non-starter.
No use case?
How are AI agents going to open up a credit card or bank account?
You think the government will grant them a SSN?
It's a good thing we have a Internet native, programmable money, that is permissionless, near instant, and already supports USD(c).
If he was, he wouldn't be shilling blockstream solutions.
Saw this same "product" astroturfed on Reddit.
Couple things.
- Didn't even know fb dating was a thing.
- people still use fb?
Easier said than done when standing up could cost you millions if not hundreds of millions of dollars.
Even if that's true today ( it's not ), it becomes less true over time as tools and models improve.
If you have someone who knows what they're doing with the latest and greatest coding agents it's just not comparable. You can have a Dev open up four or more terminals with multiple prompts running at the same time. A manual person just can't keep up.
Well, not really.
The protocol is pretty simple. Make a request and get back payment headers.
Sign the data, with the proper amounts. The signed transaction is sent to a facilitator. The facilitator validates the transaction, then broadcasts it onto the block chain. The payload is now sent to the agent or user.
The failure would be if an agent is unable to call a tool to perform it in the first place. The failure wouldn't be in the payment protocol.
In the early days of Bitcoin, I was able to send transactions programmatically. Built my own js library using json-rpc to communicate with a node.
Geohot live streamed himself broadcasting a transaction from scratch.
For that I respect his level of knowledge. Plus he built comma which is a product I use almost everyday.
Can you use your Qwen instance in CLIs like Claude code, codex, or whatever open source coding agent?
Or do you have to copy paste into LM studio?
So this wouldn't work in a web app, only a desktop app?
I guess that leaves electron and tauri?
Maybe today, but the more accessible and affordable they become, the more likely people can start offering "self hosted" options.
We're already seeing competitors of AWS but only targeting things like Qwen , deepseek, etc.
There's Enterprise customers who have compliance laws and literally want AI but cannot use any of the top models because everything has to be run on their own infrastructure.
Sorry to say, but skill issue.
Use MCP servers, specifically context 7.
This gets up to date docs as long as you include the library name on your prompt and ask to use context 7.
You did the equivalent of raw dogging gpt4(an old model) for recent news versus using an agent with web search tooling.
Funnily enough, the same scenario holds true for actual programmers vs vibe coders.
Even if you manage to prompt an app, you'll still have no idea how the system works.
in order for that lifetime companion, we'll need to make a leap in agentic memory.
how do you know memory won't be modular and avoid lock-in?
I can easily see a decentralized solution where the user owns the memory, and AIs need permission to access your data, which can be revoked.
You can't trust everyone will be polite or follow "standards".
However, you can incentivize good behavior. Let's say there's a scraping agent, you could make a x402 compatible endpoint and offer them a discount or something.
Kinda like piracy; if you offer a good, simple, cheap service people will pay for it versus go through the hassle of pirating.
how would I point to your API to use in a Mastra ai agent?