Document the semantics of our various domains #210
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
3 participants
koen
Notifications
Due date
No due date set.
Blocks
#288 external developers empowered to contribute
fediversity/fediversity
Reference
fediversity/fediversity#210
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We have at least three fediversity-related domains:
The semantic differences aren't clear and we should document them. See Fediversity/Fediversity#201 (comment) for context.
we may want to reconsider whether these domains should even be hard-coded into our code-base in the first place
They were hard-coded to have something for an initial demo, so writing down how to get rid of them is not wrong. Of course the next better solution would be to mock away an API for registering DNS domains, but that's a slightly larger task.
kiara referenced this issue2025-06-10 20:32:13 +02:00
closing in favor of trying to get hard-coded stuff out of the code-base in the first place