Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ivatar
ivatar
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Oliver Falk
  • ivatarivatar
  • Issues
  • #12

Closed
Open
Created Nov 12, 2018 by Oliver Falk@oliverMaintainer

e.g. ".well-known/avatars" as an alternative/addition to DNS SRV for federated libravatars?

Looking at WebFinger and its avatar link rel I was wondering if one could use a .well-known/avatars or something similar as an alternative/addition to DNS SRV records federated avatars server?

E.g. either add something like:

https://example.com/.well-known/avatars

or

https://example.com/.well-known/avatars-server

which responds with the avatars-server (and maybe port/path) to Well-Known URIs?

Or maybe it would fit better to use RFC 6415's .well-known/host-meta or even WebFinger?

Edited Nov 12, 2018 by Oliver Falk
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None