rpmsg-lite
protocol
| rpmsg-lite | protocol | |
|---|---|---|
| 1 | 13 | |
| 211 | 1,789 | |
| 1.4% | 3.0% | |
| 4.0 | 6.1 | |
| 2 days ago | about 1 month ago | |
| C | JavaScript | |
| BSD 3-clause "New" or "Revised" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rpmsg-lite
-
Best Way to Make a Simple PC Based GUI that Controls an STM32
I've heard of people using firmata or https://msgpack.org or https://github.com/NXPmicro/rpmsg-lite or cbor ...
protocol
- Scaling Farcaster
- Farcaster is a protocol for building decentralized social apps
-
Centralization Possibilities
We have already have a clear stack. there's Gitcoin Passport for sybil resistance, git (and wrappers like Radicle) for version control, Lit PKPs & Gelato for account abstraction, Farcaster/Orbis/Lens for social architecture, OpenStreetMaps for geographic markets, OPStack, etc.
-
Nostr.how – A Complete Guide to Nostr
These services exist outside of the protocol and depend on a few centralized and trusted authorities.
Another solution that is arguably more resistant to capture and censorship would be to use a blockchain to manage user name aliases - like Farcaster is doing with fnames.[1]
[1] https://github.com/farcasterxyz/protocol#22-farcaster-names
- Thoughts on building Web3 social platforms?
-
Telegram has stolen my channel's username to sell it on auction
one XMPP server gets big and usernames get squatted and dealt with at the discretion of the server admin.
Only solution is something like how Farcaster does it
https://github.com/farcasterxyz/protocol#3-identity
- Farcaster Protocol
-
Mastodon.technology Is Shutting Down
That's sad to hear, but it makes total sense to shut down the server given its sensitive data, rather than hand it off to another person.
Mastodon/ActivityPub is a poor fit for a social network IMHO.
- Accounts should not be tied a single server and their continued maintenance.
- Private data and DMs should be end-to-end encrypted rather than entrusted with a single administrator.
- People don't want to self-host.
The core problem of a lot of social networks comes down to name aliasing, and who controls the name registry. In the case of nostr[1] this is not a problem because everything is using public keys. Another protocol is Farcaster[2] which plans to use a smart contract to maintain a name registry without requiring a single controller.
[1] https://github.com/nostr-protocol/nostr
[2] https://github.com/farcasterxyz/protocol
- Farcaster: A sufficiently decentralized social network
What are some alternatives?
Protobuf - Protocol Buffers - Google's data interchange format
soapbox - Software for the next generation of social media.