Frühere Suchanfragen

Keine früheren Suchanfragen

Suchoptionen

Nur verfügbar, wenn angemeldet.
sueden.social ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Eine Community für alle, die sich dem Süden hingezogen fühlen. Wir können alles außer Hochdeutsch.

Verwaltet von:

Serverstatistik:

1,8 Tsd.
aktive Profile

sueden.social: ÜberStatusProfilverzeichnisDatenschutzerklärung

Mastodon: ÜberApp herunterladenTastenkombinationenQuellcode anzeigenv4.4.3

#webfinger

0 Beiträge0 Beteiligte0 Beiträge heute
Antwortete im Thread
Thomas Kujawa

@saiki @db_geek @MartinH

Ich habe

#Webfinger Support
Redirect 301 /.well-known/webfinger /index.php/.well-known/webfinger

ergänzt.

In der .htaccess stand weiter oben

RewriteCond %{HTTP_USER_AGENT} DavClnt
RewriteRule ^$ /remote.php/webdav/ [L,R=302]
RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteRule ^\.well-known/carddav /remote.php/dav/ [R=301,L]
RewriteRule ^\.well-known/caldav /remote.php/dav/ [R=301,L]
RewriteRule ^remote/(.*) remote.php [QSA,L]
RewriteRule ^(?:build|tests|config|lib|3rdparty|templates)/.* - [R=404,L]
RewriteRule ^\.well-known/(?!acme-challenge|pki-validation) /index.php [QSA,L]
RewriteRule ^ocm-provider/?$ index.php [QSA,L]
RewriteRule ^(?:\.(?!well-known)|autotest|occ|issue|indie|db_|console).* - [R=404,L]

Fortgeführter Thread
Strypey

#FediverseHistogram

On October 2, 2013, GNU social developer MMN-o (Mikael Nordfeldth) published a blog piece announcing that they'd rolled out a change to their WebFinger implementation, adding backwards-compatible support for the RFC7033 version;

"Plus of course the former RFC6415 (Web Host Metadata), which StatusNet supports (but only XRD format)."

web.archive.org/web/2016072211

For those who don't know, masrodon.social was created to federate with #GnuSocial servers.

web.archive.orgGNU Social now supports WebFinger (RFC7033) | MMN-o | Blog
#WebFinger#StatusNet
Fortgeführter Thread
Strypey

"That's the irony of what Blaine did when he created WebFinger. It was supposed to support multiple! It wasn't supposed to just be this is your fediverse address, it was supposed to be, here's how you find all the different account of information about me, and different things."

@rabble, 2025

wedistribute.org/podcast/s2e3-

So ... WF is meant to facilitate something like Libravatar, where all roads lead back to a canonical profile? Hmm ...

We Distribute · S2E3 – Rabble from Nos.Social
Mehr von We Distribute
#identity#PortableIdentity#WebFinger
Fedify: ActivityPub server framework

🎉 Huge shoutout to two amazing contributors from Korea's #OSSCA program who've made excellent contributions to #Fedify!

👏 @gaebalgom tackled a tricky terminal compatibility issue in PR #282, fixing the fedify node command's favicon display on terminal emulators without truecolor support (#168). His solution elegantly detects terminal capabilities and falls back to 256-color mode when needed—ensuring a great experience across different environments.

🌟 @joonnot enhanced Fedify's #WebFinger functionality in PR #281 by adding a configurable maxRedirection option to the lookupWebFinger() function (#248). He transformed a hardcoded limitation into a flexible, user-customizable parameter while maintaining perfect backward compatibility.

Both delivered thoughtful, well-implemented solutions that showcase the quality of contributions coming from the OSSCA program. Welcome to the Fedify community! :fedify:

#ActivityPub#opensource#fedidev
Fedify: ActivityPub server framework

🎉 Big thanks to @2chanhaeng for his first contribution to #Fedify! He implemented the new fedify webfinger command in PR #278, which allows isolated #WebFinger lookups for testing configurations. This addresses the need for developers to test WebFinger functionality without performing comprehensive object retrieval.

The contribution includes:

  • A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
  • Clean JSON output of WebFinger JRD results
  • Proper error handling for invalid handles and lookup failures
  • Complete #CLI integration with help text and usage examples

This was originally filed as issue #260 and marked as a good first issue—perfect for newcomers to learn the codebase structure while contributing meaningful functionality. The PR has been merged and will be included in the upcoming Fedify 1.8.0 release.

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

unstable.fedify.devfedify: CLI toolchain | FedifyThe fedify command is a CLI toolchain for Fedify and debugging ActivityPub-enabled federated server apps. This section explains the key features of the fedify command.
#opensource#fedidev
Fedi:Tagestipp/tröt

Im #Fediverse spielt das #Protokoll #WebFinger gemäß #RFC 7033 eine wichtige Rolle, um Nutzende ausfindig zu machen.

Diese Webfinger-Abfragen finden im normalen Umgang mit dem Fediverse aus Sicht der Nutzerschaft hinter den Kulissen statt. Von einer fediversalen #Instanz wird erwartet, daß sie über eine sogenannte "Well-known #URI" (dazu an anderer Stelle mehr) auf eine Webfinger-Anfrage reagiert.

Dieser (gut bekannte) Identifikator lautet:

/.well-known/webfinger?resource=acct:

(wobei die Domain der Instanz sowie die abzufragende Kennung zu ergänzen ist)

Netterweise kann man diese Abfrage auch über die Weboberfläche von webfinger.net durchführen lassen.

Wer neugierig ist und dies (z.B. mit der eigenen Fediverse-Adresse) ausprobieren will:

➡️ https://webfinger.net/ im Browser aufrufen.

➡️ Oben rechts im Suchkästchen "Lookup WebFinger" die gewünschte Adresse eingeben, z.B. tagestipp@mastodonium.de (ohne das führende At-Zeichen) oder die #URL-Schreibweise https://mastodonium.de/@tagestipp und das Ergebnis bewundern.

➡️ Es sollte ein "#JSON Resource Descriptor (JRD)" zu sehen sein. Okay, möglicherweise ist das immer noch ziemlich technisch... ;-)

Zum Nachlesen und schmökern:
https://en.wikipedia.org/wiki/WebFinger
https://datatracker.ietf.org/doc/html/rfc7033
https://webfinger.net/
https://en.wikipedia.org/wiki/Well-known_URI
https://de.wikipedia.org/wiki/Uniform_Resource_Identifier

*
Plinubius 🇪🇺

@moderation Die allermeisten Kreisverbände von B90/Die Grünen nutzen Wordpress, das ihnen sehr oft von Verdigado zur Verfügung gestellt wird. Grüne-Kreisverbände könnte insofern ad hoc im Fediverse relevant werden. #ActivityPub und #Webfinger-Plugin installieren, fertig. Siehe auch chaos.social/@plinubius/114721

chaos.socialPlinubius 🇪🇺 (@plinubius@chaos.social)Jeden Verein, jede Organisation, der oder die Wordpress einsetzt, muss man eigentlich nur umwerben, das #Wordpress-Plugin #ActivityPub einzusetzen. Schon allein dadurch wüchse das Fediverse binnen Wochen um (regional) relevanten Content und lokale Communities. Das könnte man als eine kettenbriefartige Kampagne anlegen bzw. als Mitmach-Challenge. Ein kleines Video-Tutorial, fertig. @_elena@mastodon.social @kuketzblog@social.tchncs.de Wie wär's? 1/x
Antwortete Marcus Rohrmoser 🌻
Ben Pate 🤘🏻

I'd love to know more about what you're thinking here.

I don't think we're replacing #Webfinger. I think we're trying to follow through on #WhatCorySaid at #FediForum (youtube.com/watch?v=7_Gs1t0qe78)

...which is basically: Let regular people take their account to a new server any time they want, without relying on awful XML/CSV import/export jobs. This would go a long way to solving Fediverse UX issues and preventing enshitification.

Is there more that I've missed?

@mro @j12t @tchambers

YouTubeFediForum Keynote: Cory DoctorowVon FediForum
Antwortete im Thread
just small circles 🕊

@risottobias @tomgag @forgefed @meissa @forgejo @radicle

This morning I tooted about #Ayllu who just released v0.4 .. code #forge not federated (yet?), though the release adds #WebFinger support.

social.coop/@smallcircles/1145

social.coopsmall circle 🕊 in calmness (@smallcircles@social.coop)Ayllu v0.4 has been released! #Ayllu is a code forge designed for performance, simplicity and hackability. The #AGPL-licensed project by Kevin Schoon can be considered a #SmallTech / #SmallWeb initiative. You can find the Ayllu code, hosted on Ayllu at: https://ayllu-forge.org/ayllu/ayllu Read all about new features in the release notes. Also, are you good at #UX and designing UI's with plain #HTML and #CSS? Then how would you design the UI for #git blame, asks Kevin. https://kevinschoon.com/blog/announcing-ayllu-0.4
julian

Pleroma Webfinger compatibility

Does anybody know what exactly Pleroma needs for a valid Webfinger check? I'm attempting to figure out why @jmtd@pleroma.debian.social won't resolve in NodeBB, and it's because the webfinger call returns 400 Bad Request.

NodeBB is calling https://pleroma.debian.social/.well-known/webfinger?resource=acct%3Ajmtd%40pleroma.debian.social with User-Agent and Content-Type headers (curiously, it's not sending Accept, but it also fails if that header is set, so that's irrelevant.)

Navigating to that webfinger url in the browser returns XML, which is :grimacing: but I'm not even getting that when NodeBB makes the call.

community.nodebb.org/post/1044

NodeBB Community · Pleroma Webfinger compatibilityDoes anybody know what exactly Pleroma needs for a valid Webfinger check? I'm attempting to figure out why @jmtd@pleroma.debian.social won't resolve in NodeB...
#activitypub#pleroma#webfinger
*
Fedify: ActivityPub server framework

Fetching remote #ActivityPub objects or actors often involves handling #WebFinger lookups, content negotiation, and then parsing potentially untyped JSON.

With #Fedify, it's much simpler: use Context.lookupObject(). Pass it a URI (e.g., https://instance.tld/users/alice) or a handle (e.g., @alice@instance.tld), and Fedify handles the lookup and content negotiation automatically.

The real power comes from the return value: a type-safe Activity Vocabulary object, not just raw JSON. This allows you to confidently access properties and methods directly. For example, you can safely traverse account moves using .getSuccessor() like this:

let actor = await ctx.lookupObject("@alice@instance.tld");
while (isActor(actor)) {
  const successor = await actor.getSuccessor();
  if (successor == null) break;
  actor = successor;
}
// actor now holds the latest account after moves

This is readily available in handlers where the Context object is provided (like actor dispatchers or inbox listeners).

Focus on your app's logic, not protocol boilerplate!

Learn more: https://fedify.dev/manual/context#looking-up-remote-objects

fedify.devContext | FedifyThe Context object is a container that holds the information of the current request. This section explains the key features of the Context object.
#fedidev
AngesagtLive-Feeds
Über