realPubkey

This is possible with RxDB, you can sync from browser to google drive or ms onedrive

A big limitation for skills (or agents using browsers) is that the LLM is working against raw html/DOM/pixels. The new WebMCP API solves this: apps register schema-validated tools via navigator.modelContext, so the agent has structured JSON to work with and can be way more reliable.

WebMCP is currently being incubated in W3C [1], so if it lands as a proper browser standard, this becomes a endpoint every website can expose.

I think browser agents/skills+WebMCP might actually be the killer app for local-first apps [2]. Remote APIs need hand-crafted endpoints for every possible agent action. A local DB exposed via WebMCP gives the agent generic operations (query, insert, upsert, delete) it can freely compose multiple steps of read and writes, at zero latency, offline-capable. The agent operates directly on a data model rather than orchestrating UI interactions, which is what makes complex things actually reliable.

For example the user can ask "Archive all emails I haven't opened in 30 days except from these 3 senders" and the agent then locally runs the nosql query and updates.

- [1] https://webmachinelearning.github.io/webmcp/

- [2] https://rxdb.info/webmcp.html

The last days I built the WebMCP plugin for the RxDB database [1]

The goal is to let agents interact with apps through explicit tools instead of DOM scraping or visual navigation. This works nicely because agents can run operations directly on the local-first data the UI already uses.

[1] https://rxdb.info/webmcp.html

This is likely done with the WebLocks API

By buildings small things, you will find ideas for bigger things that people actually need.

Yes most servers support websockets. But unfortunately most proxies and firewalls do not, especially in big company networks. Suggesting my users to use SSEs for my database replication stream solved most of their problems. Also setting up a SSE endpoint is like 5 lines of code. WebSockets instead require much more and you also have to do things like pings etc to ensure that it automatically reconnects. SEEs with the JavaScript EventSource API have all you need build in:

https://rxdb.info/articles/websockets-sse-polling-webrtc-web...

No. The title is the title, not the context. If people do not read the first 5 sentences of the introduction, you cannot help anyway.

Imagine what you could dream about if you stopped THC.

You have to quit THC for at least two weeks until you start dreaming again.

Wow. This should be fixed. Which browser/OS are you using? Are you in dark mode?

Half-life of DNS bondings is about 10k years.

Same experience for me but with west africa.

Most of the time you should not even check for the runtime. Instead you should check for the specific feature support that you want to use.

Looks great. How does it behave on conflicts when 2 offline users write to the same rows and then go online?

When they reach lower temperatures like 900C, we could finally replace the inefficent hot water turbines in coal power stations.

Which books are they banning?

Not true.

I use it in production so i can crawl instagram (and others) without paying for proxies. Tor is single threaded so I have 6 docker containers that run tor proxies to get more bandwith out of it. The best thing about tor is that you set it up once and it will work forever for free.

Is there any hidden information?

These "propaganda" makers will tell you straight into the face. It is upon you to not watch their content or buy their products.

Author here. The article is mostly about web apps. How would your signaling server emit new connection updates to clients in the scenario you describe?

But it seems that the balls speed increases with a bigger are.

Also the lookup time for files is too slow to use it on anything user facing.

Rel https://rxdb.info/replication.html

The problem with couchdb is that it does one request per document which makes the protocol slow for browser based applications also it has no http2 support. Also storing the full rev tree of the documents is what makes pouchdb slow. This is why RxDB moved away from pouchdb/couchdb to a replication which works on bulk operation and resolves conflicts directly when they happen, not afterwards.

Just close the issue section. Then you only have to review the PRs where CI is green.

30% of stuff on your "usefull" datacenters is just porn. Then we have 30% gaming servers and so on. Who are you to decide that this is more important as digital currency?

https://www.bbc.com/news/technology-23030090