Show Navigation
Notices by Mike Macgirvin (macgirvin)
-
@o0karen0o This isn't new. I'm pretty certain I've seen reports of remote hacks on infusion pumps going back ten years or so.
-
In 2010 I left Facebook and set out to build a decentralised alternative. What I found out along the way is that it wasn't just Facebook I was replacing. What we created was a privacy-respecting overlay network on top of the internet so we could replace the entire surveillance state with a system where you controlled access to your thoughts and ideas and shared it on a single sign-in decentralised network. In fact we built that, and it works great, but most people rejected it because they don't understand what that has to do with Facebook. Everything and nothing amigo. We've been living in this privacy respecting overlay internet for nearly a decade now and refuse to go back to the old ways. We've always hoped the internet itself would catch on and evolve to meet us halfway, but it seems to be devolving, so in retrospect the architectural design (as an overlay network) turned out to be the correct one.
-
@falgn0n As soon as they start supporting privacy and mobility and STOP permitting spam and harrassment by default. Until then, the answer is no. If federation with spammy and insecure protocols is something you think is important, Zap probably isn't for you.
-
@strypey @maiyannah
"Inter-operable" is a tall order, especially considering that interop opens you to spam and strips away a lot of your privacy. Your media is all forced public. Your content is mangled beyond recognition by primitive text-only and length-restricted platforms. It also completely destroys any chance to use nomadic identity.
It's no longer a benefit to your users but a liability and a threat to your network security and data integrity. Your users can always just use the popular project and say goodbye to yours (until they get burned by dickpics and harrassment or site shutdowns and come running back). Life is a series of choices and sometimes people make bad decisions. I'm OK with that. But just because they do doesn't mean I have to.
-
@lanodan I wrote the original Diaspora implementation for Friendica (and also Hubzilla). It's a decision I now regret. I also wrote the original AP implementation for Hubzilla (and was initially used by Friendica to build theirs) - a decision I likewise regret.
I'm now staying true to my core ideals. I want a social network without spam and without all this blocking bullshit and drama and with nomadic people and content so you can save yourself from bad (or inexperienced) admins and do-good censors promoting their own prejudice and intolerance.
And I have one. And I refuse to federate with yours, unless yours is based on and is fundamentally compatible with these core ideals.
And yours is not.
-
You have the right to a permanent internet identity which is not associated with what server you are currently using and cannot be taken away from you by anybody, ever.
You have the right to refuse/reject or possibly moderate comments on your posts by anybody you don't know.
You also have the right to not allow them to comment on your posts in the first place, until such time as they have earned your trust.
You have the right to show your photos and videos to anybody you desire and also NOT show them to anybody you desire.
If your software does not implement these rights, you have the right to fix it or replace it.
-
@drequivalent @kaniini Just this morning a number of fediverse sites went offline to protest a new EU law. In some cases there was no warning and a lot of people were pissed. Replace 'nomadic identity' with 'mirrored backups available 24/7'. That's the problem we're solving.
-
@kaniini @drequivalent
Yes, it's easy. It would take a half hour to support nomadic identity in any protocol stack. But you actually can't have your cake and eat it too. For nomadic communications to work, everybody using that protocol stack needs to support it, and that certainly isn't going to happen with AP.
I actually don't care about standardisation - I was dared to vote on it. AFAIC W3C endorsement would be the kiss of death for everything I've done for the last 40 years in decentralisation technology. But if somebody wants to scratch that itch and run with it, I'm not going to stop them - even though they're already at least a year behind what I'm currently working on.
-
Announce:
Zap 1.0RC
Zap is a social networking server implementing the Zot6 protocol. This is the first reference implementation of that protocol. The network is sparse at the moment with only a small handful of pioneers. Integration with legacy Zot applications (such as Hubzilla and Red) is scheduled for later in the year.
Osada 1.0RC
Osada is a social networking server implementing both ActivityPub and Zot6. It can communicate with both networks.
These projects represent tradeoffs between different social networking and social media features. Osada provides greater social reach, with a corresponding loss of privacy controls and account resilience (nomadic identity). Zap provides the full capabilities of Zot, which includes privacy controls, private media, and account resilience; with a corresponding lack of federation with networks that do not offer these features -- hence a much smaller and more intimate social graph.
Both projects and a handful of addons/apps are available now from https://framagit.org/macgirvin . These both use the LAMP stack and are licensed under the MIT license.
The Zot6 protocol is described at https://macgirvin.com/wiki/mike/Zot%2BVI/Home
-
@Laurelai @kaniini It's too late to save ActivityPub, but Zot was designed around permissions. You can give and take away permission to comment (or to do anything else) whenever you desire. If I was on Zot right now I could say "Right. You can't comment in my stream any more. It's my stream, not yours. End of discussion.". I could also say "Right. I want you to vanish." And you will. Nobody has infringed on your freedom, but you can no longer infringe on mine. People ridicule me for creating software that does this. Setting boundaries is what people do. If your software doesn't allow you to do this you need new software.
-
@KevinMarks @cwebber @sivy
Content Warnings should be an extension field. They never should have been used as a project-specific overload to an existing data element. I think you'll find that if this extension is offered that many projects will adopt it. Please don't re-use either name or summary for this.
I would encourage those interested in this topic to review the debate we had on putting such content warnings into email and USENET back in the late 80s and early 90s. There are like ten years of heated debate involving hundreds of people from many related disciplines that it would be a shame to repeat in its entirety. Eventually it was dropped because a majority consensus couldn't be reached and several vendors just started doing their own thing - so nothing has changed in 30 some-odd years. In a nutshell, the most popular expressions ended up centring on an enum field of attributes to explain the content warning. Light nudity, "graphic" nudity, sex, bestiality, drugs, alcohol, smoking, violence and death were some of the most frequently requested attributes. A free form field wasn't very popular because of translation issues and as we've seen a free form field is now being use to provide content warning for toaster settings or favourite colours and defeats the intended purpose.
There may even be an internet draft submission or two in the archives.
-
#osada is shaping up to be a pretty decent #activitypub client. We're still at least a week or two away from a public alpha but things are moving forward at a steady gallop. Groups, photos, videos, events, conversational (FB style) structure. Native WebDAV and federated single sign-on. A few other goodies are available from the "app store" (in our store everything is free). It also has a working permissions system and several privacy options because it's also a #zot6 client. I'm trying to make it compatible with the plethora of Twitter-style microblogs, but some of them have pretty brutal HTML filters. We'll see.
-
#osada heavy lifting is mostly done. Now we test. #activitypub #zot6
Mike Macgirvin
All Arkwood Pond Social content and data are available under the