Oh nice, @erincandescent is here :)
Erin is the person who transformed the Pump API into the first draft of what became ActivityPub. ActivityPub wouldn't have happened without her hard work!
Oh nice, @erincandescent is here :)
Erin is the person who transformed the Pump API into the first draft of what became ActivityPub. ActivityPub wouldn't have happened without her hard work!
Here is a tiny warthog for your troubles, fellow tooters.
If you use Debian: you're got getting the recent Intel CPU bugfixes because Intel updated the firmware package's license to state that it's not redistributable.
If use Linux other than Debian and have the bugfixes: ask your maintainers why they're distributing software they're not legally allowed to.
And in any case: next time you purchase a CPU, evaluate whether AMD might be a better choice than Intel.
rargh
wish I had time to play with WASM stuff
@meejah @jalcine I've never used Keybase tbh... I'm kinda irked by them. But it seems like they're taking a hybrid centralized + WoT model IIUC.
@nocontextspongebob lewd
@loke @jalcine The thing is that in a petname system, *many entities* can be authorities, including DNS or a third party.. or the people you know! Nobody has a monopoly. You could even trust a system like Twitter's or Keybase's, but they won't hold a monopoly on trust. See also: https://octodon.social/@cwebber/100583404230526661
@loke @jalcine The thing is that in a petname system, *many entities* can be authorities, including DNS or a third party.. or the people you know! Nobody has a monopoly. You could even trust a system like Twitter's or Keybase's, but they won't hold a monopoly on trust. See also: https://octodon.social/@cwebber/100583404230526661
@wakest @pfefferle Hm.. not sure
@cwebber if i want bread in a can i'll drink a guinness
@jalcine Again, the primary challenge here is that it requires client buy-in. But this is feasible, and even with a system where clients synchronize: make a contacts list application that multiple applications know how to talk to.
@jalcine Again, the primary challenge here is that it requires client buy-in. But this is feasible, and even with a system where clients synchronize: make a contacts list application that multiple applications know how to talk to.
@jalcine
Also of note that your petname does not have to be the same as the edge name you share. Eg, there is no global "Mom", but you may have your own Mom, but may recommend her to others as something else, eg "you => Jane Smith"
- "Follow" activities are already much like establishing a web of trust anyway.
- What if at the stage of following, we allowed you to select your own local petname for the person, and optionally share that name with the set of people you've granted the capability to read your contact-recommendations?
- So if you know "Gargron" but want to get to me, if you see "Gargron => Chris Webber" you can be reasonably sure that's me because you know we've worked together
@jalcine
- More connections in the network reinforce things. So if you also know nightpool, and you see nightpool => cwebber points to the same resource as Gargron => Chris Webber, you can be reasonably sure that's me.
- You can also absorb other naming hubs as petnames which provide edge names. So, add dns as a petname, now you can do "dns => dustycloud.org" to likewise get to me
@jalcine So "web of trust" has gotten a bad rap because most people associate "web of trust" with PGP's hyper-nerds-only model. And keep in mind, we need to survive a system where there isn't a global "one true name" for every person. Ie, you shouldn't confuse me with Chris Webber the basketball player, but neither myself nor the basketball player should be able to establish a monopoly on that name. But the petnames system described in https://github.com/cwebber/rebooting-the-web-of-trust-spring2018/blob/petnames/draft-documents/making-dids-invisible-with-petnames.md is designed for this:
@jalcine
Also of note that your petname does not have to be the same as the edge name you share. Eg, there is no global "Mom", but you may have your own Mom, but may recommend her to others as something else, eg "you => Jane Smith"
@jalcine
- More connections in the network reinforce things. So if you also know nightpool, and you see nightpool => cwebber points to the same resource as Gargron => Chris Webber, you can be reasonably sure that's me.
- You can also absorb other naming hubs as petnames which provide edge names. So, add dns as a petname, now you can do "dns => dustycloud.org" to likewise get to me
- "Follow" activities are already much like establishing a web of trust anyway.
- What if at the stage of following, we allowed you to select your own local petname for the person, and optionally share that name with the set of people you've granted the capability to read your contact-recommendations?
- So if you know "Gargron" but want to get to me, if you see "Gargron => Chris Webber" you can be reasonably sure that's me because you know we've worked together
Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.
All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.