Federated Hub News

Hubzilla 9 Checklist

Sat, 27 Jan 2024 22:19:46 -0600 last edited: Sat, 27 Jan 2024 22:20:47 -0600

Federated Hub News

news@federatedhub.org

Mario Vavti wrote the following post Sat, 27 Jan 2024 14:53:00 -0600

Hubzilla 9 Checklist

Getting there :smile_cat:
#Hubzilla 9

Hubzilla

Sat, 20 Jan 2024 07:33:13 -0600

Federated Hub News

news@federatedhub.org

dansup 🚀 wrote the following post Fri, 19 Jan 2024 02:21:42 -0600

dansup — Today at 3:59 AM Hello! While this was somewhat surprising to me, I understand why you are doing this and want you to know that I hope we can work together in some respect and upstream PRs that we find useful. If there is anything I can do on <br />my side, please let me know and I wish your fork the best! If my presense makes you uncomfortable, I totally understand and will leave, just let me know. Long live the federated pixels ❤️ Once you get a more informative presence like a website up, <br />ping me and I'll spread the word. Just because you're forking Pixelfed, doesn't mean we can't have a respectful and productive relationship!

Pixelfed was forked, I joined their discord and gave them a piece of my mind

Forks fucking rule, I'm happy to see this. Open source is crucial to the fediverse, and while we all might not agree on everything, it feels amazing to desire to work with forks

Y'all are the real winners, even more so when devs like me do the unthinkable and bring awareness to forks

#peoplePowered #pixelfed #forks

ActivityPub Updates in Streams

Sat, 20 Jan 2024 04:34:50 -0600

Federated Hub News

news@federatedhub.org

Mike Macgirvin 🖥️ wrote the following post Fri, 19 Jan 2024 15:36:59 -0600

I promise to add some more documentation before this is released, but I just want to keep providing updates on what we're doing here at the streams repository - especially as it concerns the fediverse and conversations.

The background is that we've always provided what I'll call "containerised conversations" in earlier iterations of the fediverse (several years prior to the emergence of Mastodon and ActivityPub). These are quite different from microblogs - which aren't really conversations at all, but more like people throwing posts into space kind of willy nilly. Each post and each comment can be addressed to a completely different audience.

In our alternate implementation of the fediverse, conversations are contained and more coherent. We do this by directing all comments back to the person who started the original post of the conversation, regardless how many levels of nested comments. This person "owns" the topic and is responsible for distributing all the comments to the original audience. This is how one implements restricted conversations - sometimes called circles or aspects - as well as private groups; which are very difficult to accomplish in a microblog platform. This is why only a very small number of fediverse implementations support these concepts.

When we brought our work to the ActivityPub fediverse several years ago, it conflicted with the microblogs, who quickly dominated the space. So we provided some ActivityPub extensions to continue our work and still use these very important conversational constructs.

Fast forward a few years, and we've been squeezed into a corner, and what we consider a superior way of managing "restricted" conversations has been relegated to obscurity. But during this time, a handful of ActivityPub developers have been working on tools which also provide this functionality, in better ways that in our original extensions. So we're updating our repository to accommodate these changes.

This work is described in the following Fediverse Enhancement Proposals (FEPs). The first two deal with signatures and retires the earlier flawed LD-signatures. This allows the content owner to relay private content to other members of the conversation, while providing proof that the author is not being spoofed. HTTP-Signatures don't work in this context because the original author may not have granted third-party permission to access the content directly and may not even be aware of who is involved in the conversation. The audience belongs to somebody else. It is being relayed by the conversation owner who does have permission to access the content directly.

FEP-c390: Identity Proofs
FEP-8b32: Object Integrity Proofs

The next two proposals deal with working with contextual collections. In this body of work, every conversation is a collection. Anybody can create a post, but only the owner of a conversation can add a response message to their conversation and distribute it to a pre-defined audience. This is accomplished by turning the conversation into a Collection object.

FEP-400e: Publicly-appendable ActivityPub collections
FEP-7888: Demystifying the context property

The end result is that the fediverse is able to support a wide variety of interactions which don't fit in the microblog or 'Twitter' model of interaction. There also may be times when one model works better for some conversations than others. Perhaps a simplified description would be to call these "constrained" or "contained" conversations, and the traditional microblog usage might be called "unconstrained" because conversations and their audiences have no binding to each other. Contained conversations create this binding and creates a conversation as an atomic property in the fediverse. It is also possible to "fetch" this container and access the entire conversation (all activities and comments) across all participants. This is not practical or possible using the unconstrained model. In any case, this is what we're doing. It makes things like the old Google+ "circles" and features like Facebook style private groups available to the fediverse without clumsy workarounds.

And best of all, it doesn't break compatibility with microblog software. It just provides additional functionality and features which that model of interaction cannot provide, as well as allow both mechanisms to co-exist without breaking each other's expectations of visibility and privacy.

Or put in another light, we support all of Mastodon's weird and non-standard privacy modes because we choose to. Some projects do not, and this is permitted by the relevant specifications. This just ensures that everybody supports ours - because we aren't giving them a choice.

Streams ActivityPub

Hubzilla Native Repeats

Sat, 20 Jan 2024 04:32:31 -0600 last edited: Sat, 20 Jan 2024 04:35:27 -0600

Federated Hub News

news@federatedhub.org

Mario Vavti wrote the following post Thu, 18 Jan 2024 14:46:16 -0600

Hubzilla native repeats :smile_cat:

Hubzilla

Hubzilla 8.8.6 Released!

Thu, 11 Jan 2024 11:29:55 -0600

Federated Hub News

news@federatedhub.org

Mario Vavti wrote the following post Thu, 11 Jan 2024 11:10:02 -0600

Hubzilla 8.8.6 Released!

Hubzilla 8.8.6
- Provide more builtin jsonld files
- Development branch compatibility in Libsync

Hubzilla Release

Hubzilla 8.8.5 Released!

Mon, 01 Jan 2024 21:14:47 -0600 last edited: Sat, 20 Jan 2024 04:37:00 -0600

Federated Hub News

news@federatedhub.org

Mario Vavti wrote the following post Mon, 01 Jan 2024 14:40:02 -0600

Hubzilla 8.8.5 Released!

Hubzilla 8.8.5
- Fix possible loop if DB is not reachable (introduced in 8.8.3)
- Fix some errors and deprecation warnings with PHP 8.2
- Deprecate simplepie idna_convert in favor of PHP native function
- Fix double processed quoted strings in get_tags()

Happy New Year!

Hubzilla Release

Streams Update: Online safety by default

Thu, 21 Dec 2023 23:47:25 -0600

Federated Hub News

news@federatedhub.org

Mike Macgirvin 🖥️ wrote the following post Thu, 21 Dec 2023 14:57:43 -0600

Happy holidays from the streams repository, the fediverse server from down under.

Oh by the way, there's a new release. The general theme of this release is "Online safety by default".
Come and get it.

!Streams

Streams Release

Hubzilla Highlights & Outlook

Thu, 21 Dec 2023 23:31:58 -0600 last edited: Thu, 21 Dec 2023 23:32:58 -0600

Federated Hub News

news@federatedhub.org

Mario Vavti wrote the following post Thu, 21 Dec 2023 11:32:00 -0600

2023 Highlights
- Queueworker refactored and moved to core
- Native dark/light mode for redbasic theme
- Vastly improved HQ widget
- Shiny new website https://hubzilla.org
- TOTP multi-factor authentication
- Improved PWA
- Theme improvements
- Performance improvements
- Reduced memory consumption
- Directory sync refactored
- OCAP access tokens
- Moderation of unsolicited comments/reactions
- Faces addon for face recognition in photos
- Logger statistics addon for developers and admins

2024 Outlook
- Native repeats
- Internal use of AS2

Hubzilla Roadmap

Hubzilla 8.8.4 Released!

Wed, 20 Dec 2023 08:46:09 -0600

Federated Hub News

news@federatedhub.org

Mario Vavti wrote the following post Wed, 20 Dec 2023 06:44:39 -0600

Hubzilla 8.8.4 Released!

Hubzilla 8.8.4
- Fix regression introduced in version 8.8.3
- Add test for Lib/Config
- Add active addons and blocked sites to siteinfo

Hubzilla Release

Streams 2024 Roadmap Update

Tue, 19 Dec 2023 16:58:22 -0600

Federated Hub News

news@federatedhub.org

Mike Macgirvin 🖥️ wrote the following post Tue, 19 Dec 2023 15:03:54 -0600

I've been intentionally vague about the 2024 roadmap for the streams repository until I had a clearer picture myself of what needs to happen. Here's the high-level summary...

In 2024 you're going to see the conversation take centre stage.

We're moving to a container model. Or more precisely we've always had a container model, we're just re-architecting it to fit better into the ActivityStreams framework.

We're keeping Nomad. For now. Because nomadic identity. We're keeping OpenWebAuth. Because single sign-on. OpendIDConnect? OAuth? Do you really want to click through a bunch of permission dialogues every time you get a protected photo/video in your stream? I certainly don't. Just show me the bloody media.

LD-signatures will be going away. Replaced with signed objects (FEP-8b32). Yay.

"Require Authenticated Fetch" will be turned on by default for all new sites. This is necessary to deal with all the new threat vectors that are emerging in the fediverse with the entrance of Meta and presumably other corporate players. You are free to turn it off.

The next one is a biggy. The default permissions/privacy role new channels for our network will not be "social-anybody-can-comment" OR "social-all-my-posts-are-public". It will be "social-restricted". All of your posts and files and media and events and everything you do are going to be visible to connections only by default and disallow public comments -- and posting publicly will require you to change this setting. Which of course you can easily do.

This is the sane default for our corner of the fediverse because we can offer this setting. Nobody else can. And also because providing a relatively safe and personal and private online space by default is the right thing to do.

Streams Roadmap

Federated Hub News

news@federatedhub.org

Fediverse news related to Decentralized Social Media, Fediverse-enabled Forums, Nomadic Identity, Remote Authentication, Hubzilla, Streams, ActivityPub, OpenWebAuth, and more.

Homepage:: https://federatedhub.org

Sorry, you have got no notifications at the moment...

Connections

Archives

Categories

Tags