Search
Items tagged with: Federation
[strong]Friendica | Wie komme ich an den Kommentar?[/strong]
Ich habe in diesem Beitrag laut feddit.org folgenden Kommentar:
Problem ist einzig und allein, dass er mir unter Friendica nicht angezeigt wird. Gerade herausgefunden habe ich das die Beiträge der Gruppe/Community Verkehrswende offenbar auch nicht korrekt hier her federiert werden. Da gibt es also offenbar mehr Probleme als ich ursprünglich dachte.
Wie komme ich an den Kommentar, um darauf reagieren zu können?
Danke für Eure Tipps und Hilfe im Voraus.
#Friendica #Frage #Beitrag #Kommentar #Federation #Lemmy #Fedditorg #federation #2025-08-31 !Friendica Support
[strong]ÖPNV | Busfahren, wie auf der Ladefläche eines Pritschenwagens[/strong]
Ich wollte einmal darauf hinweisen das einer der Gründe das viele selbst da wo der ÖPNV via Bus gut verfügbar und gut gemacht ist, die Verbindung via Bus meiden, da eine Fahrt damit nicht so viel angenehmer als auf der Ladefläche eines Pritschenwagens ist. Gerade bei längeren Strecken im ländlichen Bereich schlägt sich auch das massiv nieder.
Moderne Linienbusse sind in Sachen Barrierefreiheit und Transportkapazität den im ländlichen Bereich früher einmal oft eingesetzten Reisebussen in vielen überlegen, aber eben nicht in allem. Den wenn es um den Fahrkomfort geht, verlieren die modernen Linienbusse auf voller Länge. Da fangen die Busse schon bei kleinen Unebenheiten und schlechter Straße an zu rütteln und zu vibrieren wir irre, daran sich vor oder nach der Arbeit noch ein wenig zu erholen ist nicht zu denken. Das Smartphone, Tablet oder gar Laptop zu benutzen ist oft reine Glückssache und auch die Polsterung der Sitze die einiges abfangen könnte, wird seit vielen Jahren immer mieser. Ja das sind im Endeffekt Luxusprobleme und Überfüllung, ausgefallene Klimatisierung und Heizungen sind schlimmer. Aber das ist eben auch ein Punkt der sehr wichtig ist, wenn man Menschen davon überzeugen will von ihrem bequemen Auto auf den ÖPNV zu wechseln.
#ÖPNV #Bus #Busverkehr #Linienbus #Reisebus #Komfort #Bequemlichkeit #Mobilität #2025-08-30 @Verkehrswende
Concept for discussion: Replacing HTTP Signatures with Bearer Tokens for ActivityPub Federation
Curious what other people think about this idea. What if federation security was re-worked to use target-assigned bearer tokens to authenticate GET/POST requests? This would remove the need for complicated signing schemes and reduce system load under heavy traffic bursts (as no cryptography is required).
A basic implementation could look like this:1. When instance A (
2. Instance B makes a POST request back to a dedicated verification endpoint on instance A (for discussion, we'll say it's
3. Instance A checks the verification token (and verify that it matches the target domain name) and return a successful value. The verification code must be invalidated after this call!4. Instance B, after verifying instance A's request, returns a securely-generated federation key back to instance A. This federation key is a bearer token used to authenticate all requests from instance A to instance B. This key must be unique to instance A!5. Instance A completes the original request with the
6. Instance B receives the request, detects the federation key, and checks it against the list of registered instances.
7. If the key does not exist or A has been defederated, then a
8. If the key is expired or revoked, then
Advantages versus HTTP Signatures:- No cryptography requirements.
- Simple logic, no edge cases around HTTP query parameters or header order.
- Equally effective for all request types.
- Keys can be easily revoked or rotated.
- Supports authorized fetch and defederation use cases "by default".
Disadvantages versus HTTP Signatures:- Breaks the actor model - instances are required as a first-class concept. (but really, the actor model is basically dead already. you can't even federate reliably without a WebFinger server, at minimum.)
- Requires multi-request "handshake" before communication. (but this is already required in practice, since a signature can't be validated without first requesting the signing actor.)
- Out-of-band protocol - communication can't happen over ActivityPub / ActivityStreams because this is a prerequisite to authenticate any request. (but again, we already require WebFinger and some software requires NodeInfo for full support.)
So, what are your thoughts? Good idea? Bad idea? Did I miss something? Please let me know, I welcome replies here!
#ActivityPub #AP #Federation
Curious what other people think about this idea. What if federation security was re-worked to use target-assigned bearer tokens to authenticate GET/POST requests? This would remove the need for complicated signing schemes and reduce system load under heavy traffic bursts (as no cryptography is required).
A basic implementation could look like this:1. When instance A (
a.example.com) first attempts to federate with instance B (b.example.com), a POST request is made to a dedicated registration endpoint. (for discussion, we'll say it's https://b.example.com/activity-pub/register-instance). This request includes fields necessary for verification, including the source domain name, target domain name, and a securely-generated verification token. Other metadata could be included to allow instance B to selectively allow/prohibit federation based on other criteria, but this is optional.2. Instance B makes a POST request back to a dedicated verification endpoint on instance A (for discussion, we'll say it's
https://a.example.com/activity-pub/verify-registration). This request must include the target domain name and verification token provided in step 2.3. Instance A checks the verification token (and verify that it matches the target domain name) and return a successful value. The verification code must be invalidated after this call!4. Instance B, after verifying instance A's request, returns a securely-generated federation key back to instance A. This federation key is a bearer token used to authenticate all requests from instance A to instance B. This key must be unique to instance A!5. Instance A completes the original request with the
Authorization header set to Bearer {federation_key}.6. Instance B receives the request, detects the federation key, and checks it against the list of registered instances.
7. If the key does not exist or A has been defederated, then a
403 Forbidden error is returned.8. If the key is expired or revoked, then
401 Unauthorized error is returned. Upon receiving a 401 error, instance A should start over from step 1 to re-authenticate and complete the request with a new token. This process should not be repeated for recursive failures!9. If the key is approved, then a 200 OK response or 202 Accepted response is returned, and A can consider the request as successful.Advantages versus HTTP Signatures:- No cryptography requirements.
- Simple logic, no edge cases around HTTP query parameters or header order.
- Equally effective for all request types.
- Keys can be easily revoked or rotated.
- Supports authorized fetch and defederation use cases "by default".
Disadvantages versus HTTP Signatures:- Breaks the actor model - instances are required as a first-class concept. (but really, the actor model is basically dead already. you can't even federate reliably without a WebFinger server, at minimum.)
- Requires multi-request "handshake" before communication. (but this is already required in practice, since a signature can't be validated without first requesting the signing actor.)
- Out-of-band protocol - communication can't happen over ActivityPub / ActivityStreams because this is a prerequisite to authenticate any request. (but again, we already require WebFinger and some software requires NodeInfo for full support.)
So, what are your thoughts? Good idea? Bad idea? Did I miss something? Please let me know, I welcome replies here!
#ActivityPub #AP #Federation
HTTP authentication - HTTP | MDN
HTTP provides a general framework for access control and authentication. This page is an introduction to the HTTP framework for authentication, and shows how to restrict access to your server using the HTTP "Basic" scheme.MDN Web Docs
@Friendica Admins @Friendica Developers @Friendica Support What is the consensus on adding relays in #friendica, do they actually help #federation, do they reduce it, speed it up, slow it down, increase it, as a concept I understand it as say #hamradio relays, it allows your reach to go further, but since my instance is federated, how much further do relays actually deliver my posts, and again does it actually help to have them? I have tried a few, with mixed results and I am rather baffled by their existence and usability in relation to my instance, any clear answers would be appreciated.
[strong]Friendica: Unvollständige Federation mit Lemmy[/strong]
Wenn ich die Lemmy Community
https://feddit.org/c/heidelberg der ich seil längerer Zeit folge direkt öffne, sehen die ersten sechs Beiträge so aus:
Wenn ich sie mir jedoch über Friendica anschaue sehen ich jedoch nur die drei Beiträge davon, die ich selbst erstellt habe:
Sprich die Hälfte der Beiträge fehlt. [strong]Woran kann das liegen ?[/strong]
#Friendica #Frage #Lemmy #Federation #Beiträge #2025-04-28 !Friendica Support @Matthias
Federation of organisation accounts to Diaspora
Hello !Friendica Support
Do accounts marked as organization not federate to diaspora?
#question #federation #Diaspora
Do accounts marked as organization not federate to diaspora?
#question #federation #Diaspora
Deleting posts
Hello !Friendica Support,
Shouldn't the deletion of posts also be federated?
Both are Friendica instances. However, it is a calendar entry, but also deleting events should be federated after all.
#bug #federation
Shouldn't the deletion of posts also be federated?
- I wrote a test post on instance A,
- It arrived on instance B.
- Now I have deleted it on instance A.
- Now it should be deleted on instance B as well.
Both are Friendica instances. However, it is a calendar entry, but also deleting events should be federated after all.
#bug #federation