tahoe-lafs/trac-2024-07-25

change the hostname in the version strings from allmydata.org #1482

New issue

Open

opened 2011-08-13 05:12:30 +00:00 by zooko · 1 comment

zooko commented

2011-08-13 05:12:30 +00:00

Owner

Our protocol versioning scheme uses URLs to indicate specific versions of things. Those URLs currently have hostname "allmydata.org" but we've moved to make "tahoe-lafs.org" our primary hostname for the open source project. Should we change those URLs? Would that confuse clients that are using those URLs for version indicators -- would they think that this means a new (and presumably incompatible) version of the protocols in question and thus refuse to interoperate or something?

wiki/Versioning, [introducer server's implementation]source:trunk/src/allmydata/introducer/server.py?annotate=blame&rev=5110#L51

Our protocol versioning scheme uses URLs to indicate specific versions of things. Those URLs currently have hostname "allmydata.org" but we've moved to make "tahoe-lafs.org" our primary hostname for the open source project. Should we change those URLs? Would that confuse clients that are using those URLs for version indicators -- would they think that this means a new (and presumably incompatible) version of the protocols in question and thus refuse to interoperate or something? [wiki/Versioning](wiki/Versioning), [introducer server's implementation]source:trunk/src/allmydata/introducer/server.py?annotate=blame&rev=5110#L51

tahoe-lafs added the

labels 2011-08-13 05:12:30 +00:00

tahoe-lafs added this to the undecided milestone 2011-08-13 05:12:30 +00:00

davidsarah commented

2011-08-13 19:36:10 +00:00

Author

Owner

Replying to zooko:

Our protocol versioning scheme uses URLs to indicate specific versions of things. Those URLs currently have hostname "allmydata.org" but we've moved to make "tahoe-lafs.org" our primary hostname for the open source project. Should we change those URLs?

When we next make an incompatible change to each protocol, yes -- but we don't make incompatible changes very often.

Replying to [zooko](/tahoe-lafs/trac-2024-07-25/issues/8987): > Our protocol versioning scheme uses URLs to indicate specific versions of things. Those URLs currently have hostname "allmydata.org" but we've moved to make "tahoe-lafs.org" our primary hostname for the open source project. Should we change those URLs? When we next make an incompatible change to each protocol, yes -- but we don't make incompatible changes very often.

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1482

No description provided.