silverpill

@silverpill@mitra.social · Joined ⁨Nov⁩ ⁨2021⁩

Developer of ActivityPub-based micro-blogging and content subscription platform Mitra. I help maintain the FEP repository and write my own FEPs too. Currently working on ActivityPub Next.

Matrix
@silverpill:unredacted.org
$XMR
48YM8jwJqDkeUvD38vepSXFeMZH1zsjbvGwTTuaNSSq6Q5GyeWaeiheAZUsSmNn72YdyLpw8geb4FL3opZfGbguJLUj8Mi9
PGP
0541 49E3 0F91 C6D7 8FFA C49C 955F 5A6E 2123 25F0
OMEMO fingerprint
689a2fb0ec87a9481fb45cb7d8870da6aeb4d8247bd69a39017701133b901f04
Matrix (backup)
@silverpill:poa.st

silverpill boosted

Replying to @⁨mitchconner@clubcyberia.co⁩

@Mitch Conner @silverpill Exactly this exists on Hubzilla, (streams) and Forte. With even more options, actually. Hubzilla calls them "privacy groups", (streams) and Forte call them "access lists".

Now it comes: You can not only post to one specific such group/list. You can also post to several ones. Or to any combination of privacy groups/access lists and single contacts.

Better yet: You can even exclude single contacts or the members of certain privacy groups/access lists. You can post to the members of privacy groups Foo and Bar, except if they're also in privacy group Baz, and except for Alice, and in addition, you can post to Bob and Carol.

In addition, Hubzilla, (streams) and Forte don't just define who receives the post. They don't simply flag it a DM either. They flag it "restricted" and only grant the recipients permission to read the post, read any comments and interact with anything in the conversation. In practice, this also means that those who have these permissions can not only interact with the original poster, but just as well with each other, because it isn't a DM.

Anything that doesn't understand these permissions, e.g. Mastodon, do understand it as a DM. This limits their possibilities to interact, but it's the safe way.

And yet, Hubzilla, (streams) and Forte still have private and/or secret groups with moderation (like Facebook groups) on top of all this. (streams) and Forte even optionally have two levels of non-moderator users.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #Groups #FediGroups #FediverseGroups #PrivateGroups #Permissions #PrivacyGroups #AccessLists
hub.netzgemeinde.euNetzgemeinde/Hubzilla

Private groups

Lately, I've been seeing various people claiming that fediverse doesn't have private groups. They often point to some task force at w3c that is supposedly working to fill the gap.

However, fediverse has had private groups for a very long time:

- Hubzilla channels. This project probably had private groups before ActivityPub. The implementation was later adapted for ActivityPub and refined in subsequent forks, Streams and Forte. It is now partially documented in FEP-171b: Conversation Containers.
- Smithereen groups. This implementation is documented in FEP-400e: Publicly-appendable ActivityPub collections (published in 2021) and FEP-db0e: Authentication mechanism for non-public groups.
- Lemmy communities. Private groups were proposed in Lemmy RFC 0005 and have been implemented in the development version. There is a test instance running this version (Lemmy v1.0b) at https://voyager.lemmy.ml/

There are probably other implementations that I am not aware of.

#Hubzilla #Smithereen #Lemmy

info.hubzilla.huGroups / Forums / Communities - en - Hubzilla KnowledgeDB

silverpill boosted

FEP-2345: fediverse:creator

Hello! First time submitting a FEP myself. This one is for a feature Mastodon has had since July 2024, which is fairly popular among bloggers and journalists.

Often, the author of a website is present on the social media platform where the links to the website are being shared. However, usually there is no quick way to navigate to the author's social media profile from the link preview. Being able to navigate to the social media profile of a website's author from that website's link preview is a win-win situation for the author and for the platform. This FEP defines a new meta property fediverse:creator which can appear in the section of any website.

PR: https://codeberg.org/fediverse/fep/pulls/893

Mastodon BlogHighlighting journalism on MastodonToday we're launching a new feature that will highlight writers and journalists that are active on the fediverse when their articles are being shared.

Replying to @⁨silverpill@mitra.social⁩

@sun @deutrino

>can you tell me more about where I can read about your work with p2p and your idea for adapting forgefed? I'm interested.

1. My experiment with ActivityPub over Syncthing: https://mitra.social/post/019de9a2-7769-7713-85c9-ad8e8599268d
2. ActivityPub & iroh: https://mitra.social/post/019f8116-59de-71f2-8c56-2e87e32c2859
3. I'm currently working on federated groups in Mitra and so far they seem to be compatible with FEP-ef61 and therefore with P2P ActivityPub
4. ForgeFed has many similarities with federated groups: https://codeberg.org/ForgeFed/ForgeFed/issues/324

Mitra ZeroFediverse & P2P - Post by @silverpillFediverse & P2P - Post by @silverpill

silverpill boosted

It's been a while since an update! While the automated status updates on this account have stopped (four years ago), the site has been running in the background all this time. Work has been done by the new owners to fix some of the performance related issues, and to modernize the site. Latest updates, in addition to fixing loading times, include icons for most of the major platforms and a search box for instance names.

Check it out and join the Matrix chat room.

https://the-federation.info

#thefederation #fediverse #activitypub #diaspora #decentralization

FEP-0806: Simple client-side encryption

https://codeberg.org/silverpill/feps/src/branch/main/0806/fep-0806.md

The FEP now includes the recommended algorithm parameters.

I consider it finished but I don't plan to continue working on my implementation or publishing to the main FEP repository. It would be better to focus on group messaging with forward secrecy (MLS or similar).

#fep_0806 #e2ee

Summary card of repository silverpill/feps, described as: My FEPsCodeberg.orgfeps/0806/fep-0806.md at mainfeps - My FEPs

Setting up a Forgejo instance: https://code.mitra.social/silverpill/mitra

It will be mirroring repositories related to the #Mitra project. I don't plan to migrate from Codeberg right now, but it wouldn't hurt to have a self-hosted instance in case they decide to enforce the new anti-crypto policy.

This will also allow me to test the implementation of federation in Forgejo.

Summary card of repository silverpill/mitra, described as: Federated social networkForgejo: Beyond coding. We Forge.mitraFederated social network

silverpill boosted

[Decentralized, federated platform for dog owners]

I haven’t been able to get this idea out of my head for a while now. 😩😁

Why are there centralized platforms for dog owners—but no open, decentralized alternative? 🤔

What if clubs, animal shelters, dog training schools, or local communities could run their own instances while still being interconnected, based on ActivityPub, similar to the Fediverse? 😃

Possible features could include:
🐶 Dog profiles
🚶 Walks & meetups
📍 Dog parks & local spots
⚠️ Poisoned bait and hazard alerts
🔎 Missing & found dogs

The focus would be on data sovereignty, local communities, and open standards instead of a centralized platform. 😉

Attached is a preliminary concept diagram to make the idea more tangible.

I’d be interested to know:
Would you use something like this, or even help build it? ⁉️ 🙄

#Fediverse #ActivityPub #OpenSource #SelfHosting #Dogs #DogLovers #AnimalWelfare #Community #Idea

Infographic in DIN A4 format titled “Dog Network – Decentralized. Local. For Dogs and Their Owners.” The infographic visualizes the concept of a decentralized dog platform based on ActivityPub. At the center, a network diagram connects several independent communities (e.g., animal shelters, dog training schools, local communities, or breed groups) that communicate with one another via a federated infrastructure.

On the right, a smartphone app with a map view is shown as an example. Surrounding it are potential features: dog profiles, walks and meetups, warnings about hazards and poisoned bait, dog parks and local spots, missing or found dogs, as well as groups and discussion forums.

Other sections explain data protection, data sovereignty, self-hosting, open-source technologies, and an optional, privacy-friendly meeting mode that uses intentionally imprecise location data. The design primarily uses shades of green and natural tones, featuring illustrations of dog owners, dogs, maps, and network symbols. The graphic serves as an initial concept sketch and does not represent a finished product or final design.
ALT

silverpill boosted

Replying to @⁨silverpill@mitra.social⁩

@silverpill No stance - i.e. All good.

Crypto is a technology in the first place and nothing that should be banned or moderated on the code level. Many people use it in a very positive way.

Abuse and bad acting is always possible and might surely happen in this sector more frequently than elsewhere - but that is actor-related and nothing of our business hosting source code.

If someone would use crypto projects on our CI to act questionable or perform harmful actions - this would be another case then.

Proposal: Replace gateways query parameter in 'ap' URIs with @gateway, which can be used multiple times

https://codeberg.org/fediverse/fep/pulls/890

Before:

?gateways=https%3A%2F%2Fserver1.example,https%3A%2F%2Fserver2.example

After:

?@gateway=https%3A%2F%2Fserver1.example&@gateway=https%3A%2F%2Fserver2.example

Query parameters are often used to specify collection filters. The @ prefix will make it clear that gateway parameter is special.

#fep_ef61

Summary card of an issue titled "WIP: FEP-ef61: Define `@gateway` query parameter" in repository fediverse/fepCodeberg.orgWIP: FEP-ef61: Define `@gateway` query parameterReplacing `gateways` query parameter in 'ap' URIs with `@gateway`, which can be used multiple times. https://socialhub.activitypub.rocks/t/fep-ef61-portable-objects/3738/92

Codeberg is banning "cryptocurrency projects":

https://codeberg.org/Codeberg/org/pulls/1254#issuecomment-19820413

I don't know if Mitra qualifies as such, but I guess it is time to move to a self-hosted forge.

Summary card of an issue titled "Proposal for Assembly 2026: Disallow cryptocurrency projects" in repository Codeberg/orgCodeberg.orgProposal for Assembly 2026: Disallow cryptocurrency projectsContext: - https://forum.codeberg.org/d/82-taking-a-stance-against-cryptocurrency - https://codeberg.org/Codeberg/Community/issues/794 - https://codeberg.org/Codeberg/Community/issues/2184