#rpc
A Globo Paraná - Rpc já está pronta pra narrativas.
MARRECO E SUA GANGUE NA CADEIA
Vai rolar cabeça de inocentes como de praxe.

Sergio Moro vai escalar investigador da Lava-Jato para Secretaria Anticorrupção no Paraná

veja.abril.com.br/brasil/sergi...
veja.abril.com.br/brasil/sergi...
November 15, 2026 at 11:01 PM
você na rpc
November 16, 2026 at 3:51 PM
Modern RPC libraries are also worth a peek under the hood. They tend to deal with the same problem too.
November 18, 2026 at 6:25 PM
Rpc
November 18, 2026 at 12:50 PM
📦 linlic/rpc v9.3.410

封装RPC方法接口

🔗 https://github.com/9499574/linlic-rpc
November 18, 2026 at 8:18 AM
Quite sorry for Taiwan. I hope they'll make RPC pay dearly for the invasion.
Oh shut up already. Not a single word about all the Russian atrocities, again. US defense official Elbridge Colby criticizes Ukrainian deep strikes against civilian infrastructure, citing Wildberries. He argues they have not slowed Russia's advance and may strengthen Moscow's willingness to escalate
November 17, 2026 at 6:25 PM
Giving expert evidence to the committee, Rupert Cowper-Coles from RPC LLP responds that while legal privilege is a fundamental right, if the regulator does not have the powers to access client-lawyer communications under any circumstances, then, “bad conduct is going to flourish”.
November 18, 2026 at 12:10 PM
Which RPC calls still trigger authentication on a hardened domain controller?

At Entrypoint, @podalirius.bsky.social will reveal new RPC/DCOM coercion paths tested on Windows Server 2025, and what makes them reachable.

entrypoint.fr/talks/rpc-co...
November 12, 2026 at 3:03 PM
📦 easyswoole/rpc 6.0.1

An efficient swoole framework

🔗 https://github.com/easy-swoole/rpc
November 17, 2026 at 6:59 AM
They surely do! I'm asking this because I've built such an RPC system that does what I'm after internally, but I keep coming back to this as a standalone API I'd love to have.

RPC is way too big of a thing to be a solution to my problem. It's similar to schemas in this regard.
November 18, 2026 at 6:32 PM
RPC, Inc. Welcomes Rob Saltiel as New President and CEO to Lead Future Growth#USA#Inc.#Atlanta#RPC#Rob_Saltiel#Ben_Palmer
RPC, Inc. Welcomes Rob Saltiel as New President and CEO to Lead Future Growth
RPC, Inc. announces Rob Saltiel takes over as President and CEO, succeeding Ben Palmer. His extensive experience is expected to enhance company growth.
third-news.com
November 18, 2026 at 12:14 PM
A Solana RPC node is the API layer between your app and the chain: use JSON-RPC to read state and submit transactions. For production, compare latency, rate limits, reliability, and geographic coverage—not just price. onfinality.io/en/rpc-assis...
November 18, 2026 at 10:47 PM
A free Solana API is usually a public RPC endpoint: use it to prototype reads and submit signed transactions, but expect rate limits. Add retries, then move to managed RPC when reliability matters: onfinality.io/en/rpc-assis...
November 17, 2026 at 12:41 PM
SORA API is the RPC/JSON-RPC interface dApps use to read chain state and submit transactions. Use a public endpoint for development; choose a dedicated endpoint for production isolation and predictable capacity: onfinality.io/en/rpc-assis...
November 17, 2026 at 4:01 AM
If your Solana app signs a transaction again when the RPC times out, your user can pay twice.
November 15, 2026 at 11:40 AM
AI summaries eating 40% of search traffic shifts the web economics model. Zero-click answers reduce publisher incentives to maintain open indices, accelerating the shift toward gated RPC endpoints and private RAG corpora.

Data: https://app.neubench.workers.dev
#AI #SystemDesign
November 18, 2026 at 2:02 AM
Apache Roller has a critical deserialization flaw (CVE‑2026‑129448) that lets unauthenticated attackers run code via XML‑RPC. Upgrade to 6.1.6 or disable XML‑RPC to stop the RCE.
Apache Roller deserialization flaw CVE-2026-129448 allows remote code execution
Critical Apache Roller flaw enables unauthenticated attackers to run code via XML‑RPC; upgrade to 6.1.6 or disable XML‑RPC.
nceriofeed.beyondnets.com
November 17, 2026 at 1:45 PM
Benchmark metadata, cNFT, and asset-indexing endpoints using your app's real query patterns; standard JSON-RPC alone won't reveal pagination or indexing gaps: onfinality.io/en/rpc-assis...
November 17, 2026 at 10:41 PM
AI agents don't care about narratives—they optimize purely for latency, fee predictability, and RPC uptime. Machine traffic will test network stability far harder than retail ever did.
November 17, 2026 at 1:37 PM
An “unlimited” Solana RPC plan usually removes per-request quotas, not throughput limits. For production, test sustained concurrency and verify archival access, burst handling, and SLA terms: onfinality.io/en/rpc-assis...
November 18, 2026 at 3:22 PM
Choose Solana RPC indexing by query: getSignaturesForAddress for history, getTokenAccountsByOwner for balances, and program-state filters to avoid client-side scans. Test against production traffic: onfinality.io/en/rpc-assis...
November 17, 2026 at 5:42 PM
Apache Roller’s CVE-2026-129448 lets attackers run code via XML-RPC deserialization. Disable XML-RPC now or patch to 6.1.6, no time to wait.

#RCE #Apache #XMLRPC
November 18, 2026 at 8:10 PM
Die Drohung, die man Fuchs vor seiner Zwangsausweisung aus der DDR mit auf den Weg gab: „Legen Sie sich nicht mit uns an. Autounfälle gibt es auch im Westen.“ Einem Bombenattentat entging er später nur um Haaresbreite.

👉🏼 Wer war Peter G.? Über Jürgen Fuchs in Stasihaft: steady.page/de/renatus-d...
November 13, 2026 at 6:00 PM
💬 @github-actions — PR #5885 : lex-rpc: add XRPC subscriptions
lex-rpc: add XRPC subscriptions by matthieusieben · Pull Request #5885 · bluesky-social/atproto
Commentaire de pull request · PR #5885 lex-rpc: add XRPC subscriptions · @github-actions Review: lex-rpc XRPC subscriptions ( #5885 ) I found nothing blocking, and the change looks solid. I have one small non-blocking item. Finding Non-blocking: the eslint guidance doesn't mention the new re-export ( eslint.config.js:166 ). @atproto/lex now re-exports @atproto/lex-rpc/subscription ( packages/lex/lex/src/index.ts ). The no-restricted-imports message for @atproto/lex still lists only "lex-client, lex-schema, lex-data, lex-json, lex-cbor". Scenario: a service imports xrpcSubscribe from @atproto/lex . The lint message tells them to switch to lex-client , which deliberately doesn't export it. Fix: add lex-rpc/subscription to that list. I couldn't anchor an inline comment here because the line isn't part of the diff. What I checked subscription.ts frame parsing and stepping Message and error frames must carry exactly one body. Frames with an unknown op are ignored after the header. Error frames are checked even with validateResponse: false . Parse failures are handed back through iterator.throw() , and finally calls return() on break. An abort reason passes through unchanged, and errors from the handler are wrapped by isTransientError . Params-function path end to end XrpcSubscriptionParamsError is thrown inside ws-client's url() , which now resolves within the try. It goes through defaultSubscriptionShouldReconnect , with escalating backoff because there's no open to reset it. Abort during resolution still rejects with the reason. xrpcRequestUrl becoming async: its only callers are xrpcRequest (now awaited) and subscription.ts . buildAgent websocket handler Header merge precedence is correct. http(s) maps to ws(s) . Unsupported protocols throw inside url() . Client keeps websocketHandler because it passes through buildAgent . isAgent accepts the new optional field. RETRYABLE_HTTP_STATUS_CODES change It's a breaking change and is correctly bumped minor (pre-v1) for lex-rpc, lex-client and lex. No other in-repo consumer used the lex-rpc export. The bsky and ozone copies are independent. ws-client The unexpected-response handler records the status before terminating, so the first close wins. UnexpectedResponseError is classified by status. Errors thrown by the URL function are now classified by the reconnect policy. Packaging lex-cbor and ws-client moved to runtime dependencies of lex-rpc, with tsconfig references to match. The new ./subscription export is covered by files: ./dist . lex-rpc's sideEffects only lists the polyfill, so tree-shaking of the subscription entrypoint holds. Each touched package has a changeset. Agent files: the lex-client and xrpc-server skills are updated for the new consumer pattern. The PR description says errors thrown by a params function are not XrpcSubscriptionError s. The code and the skill wrap them in XrpcSubscriptionParamsError , so the code is right and only the description is out of date. CI (Repository CI) was still running when I reviewed, so I have no results from it. Claude review, run Ouvrir sur GitHub →
github.com
November 18, 2026 at 2:53 PM
Production Solana apps should use a dedicated RPC endpoint with exponential backoff for 429s and a tested fallback provider. Compare latency, quotas, and failover behavior before choosing one: onfinality.io/en/rpc-assis...
November 18, 2026 at 6:42 AM