#namecollision — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #namecollision, aggregated by home.social.
-
@t73fde Re: Namenskollisionen / #NameCollision.
The localhost #FederatedWiki server tells you if the page already exists. In case of a collision, the client decides what changes need to be made to the history (keyword: journal) to bring the page to the desired state. The history is kept so that earlier versions can be restored (keyword: replay).
-
@t73fde Re: Namenskollisionen / #NameCollision.
The localhost #FederatedWiki server tells you if the page already exists. In case of a collision, the client decides what changes need to be made to the history (keyword: journal) to bring the page to the desired state. The history is kept so that earlier versions can be restored (keyword: replay).
-
@t73fde Re: Namenskollisionen / #NameCollision.
The localhost #FederatedWiki server tells you if the page already exists. In case of a collision, the client decides what changes need to be made to the history (keyword: journal) to bring the page to the desired state. The history is kept so that earlier versions can be restored (keyword: replay).
-
@t73fde Re: Namenskollisionen / #NameCollision.
The localhost #FederatedWiki server tells you if the page already exists. In case of a collision, the client decides what changes need to be made to the history (keyword: journal) to bring the page to the desired state. The history is kept so that earlier versions can be restored (keyword: replay).
-
@t73fde Re: Namenskollisionen / #NameCollision.
The localhost #FederatedWiki server tells you if the page already exists. In case of a collision, the client decides what changes need to be made to the history (keyword: journal) to bring the page to the desired state. The history is kept so that earlier versions can be restored (keyword: replay).