Bumblefudge
Bumblefudge
(Discussed on today's SWIGCG call) +1 I think it's standard procedure to do what Ben's proposing in cases where document/code/schemata are accidentally more constrictive than (or don't match) spec requirements,...
I would also note that in the community extensions to the ActivityPub extensions to ActivityStreams, there is a fep called FEP-bad1 which includes previous versions of an edited object-- not...
stepping back a little from the proposed change itself, maybe we're getting into the fine-grained distinction between a low-level standard and a stack-sized *profile* of that standard? i.e., "to interop...
> 1. perhaps add a general case, that all transmissions must be encrypted to a certain level. fwiw i also love this as a separate and additional profile requirement, although...
@jaredhanson any update here? DM me on Discord, twitter, etc if a 1:1 meeting would help!
hey frens any progress here
Largely overtaken by events-- see #25, #217 (updating 25 substantially after months of work in the RPC WG with MetaMask and others), and #104 for namespacing RPC methods across multiple...
One quick fix would be to change the language from ``` The accounts returned as a result should match the requested `chainId`s and should be an array of CAIP-10 compliant...
what about the VC stuff in #169 ? Early reviewers have said they find the *directionality* very confusing (the method names and spec don't really make clear who calls whom),...
Just because you haven't seen them doesn't mean there aren't prototypes on private branches out there 😉