How could I expose the functions and constants of a dynamic or static library for an #RPC format or protocol?
As in I have a lib, how do I generate a for example an #openAPI JSON, #protobuf that describes the lib? I could then generate or run a server that interprets the lib description and accepts remote calls.
All I would need to do is write my library as normal, run one command to generate the descriptor and run the server with it.
How can one collaborate on a document with suggestions and discussions about those suggestions?
I thought about using pull/merge requests, but they aren't very visual and one is really limited to simple textual representations (rich text l, images, etc. won't work).
What if web apps actually ran in containers with runtimes they required?
Browsers have are already VMs with a GUI with a limited runtime (JS) and UI language (HTML+CSS).
Why bundle entire we browsers around applications when one could use existing technologies (containers, display managers, etc) to provide the same things but smaller and with whichever protocol they want to use?
Is it possible to receive an #anonymous message, but still verify that the sender is part of your userbase?
For example, I want to have a community made up of only selected people / using very selective criteria and allow them to share their experiences anonymously. A support group for victims of abuse (rape, drugs, harassment, etc.).
Could something similar to #signal's "Sealed Sender" work?
Is there any surefire way of verifying that the opensource software running on a server you don't control is really the version in the repo?
e.g git master has commit with SHA 12345ABC, how do I know that exact version is running on the server?
Is it even possible?
Long-range quantum entanglement measured at last – Physics World
New work by two independent groups might aid the development of robust quantum memories
So, just to understand, is this the equivalent of researching the basics to make hard disks to store information the basics for RAM?