tahoe-lafs/trac-2024-07-25

Allow metadata (location, contact information) to be added to announcements #650

New issue

Open

opened 2009-02-27 21:47:21 +00:00 by soult · 1 comment

soult commented

2009-02-27 21:47:21 +00:00

Owner

It would be useful for the VolunteerGrid if users could add some metadata to announcements, e.g. storage node location, contact information or notes about the connectivity. This would probably also help to implement the idea in ticket #642.

IRC log (UTC)

[21:21]	<zooko> Ooh, I want a way to put metadata into the
announcement, next to the "nickname" so that we can, if we choose,
put geographic location in there.  :-)
[21:22]	<soultcer> I added a table at
http://allmydata.org/trac/tahoe/wiki/VolunteerGrid but metadata
for storage node announcements sounds easier to maintain and more
fun. Maybe you can add not only a location node but also a contact
node, in case we need to contact node owners.

It would be useful for the [VolunteerGrid](wiki/VolunteerGrid) if users could add some metadata to announcements, e.g. storage node location, contact information or notes about the connectivity. This would probably also help to implement the idea in ticket #642. **IRC log (UTC)** ``` [21:21] <zooko> Ooh, I want a way to put metadata into the announcement, next to the "nickname" so that we can, if we choose, put geographic location in there. :-) [21:22] <soultcer> I added a table at http://allmydata.org/trac/tahoe/wiki/VolunteerGrid but metadata for storage node announcements sounds easier to maintain and more fun. Maybe you can add not only a location node but also a contact node, in case we need to contact node owners. ```

tahoe-lafs added the

labels 2009-02-27 21:47:21 +00:00

tahoe-lafs added this to the undecided milestone 2009-02-27 21:47:21 +00:00

warner commented

2009-03-01 04:28:51 +00:00

Author

Owner

Yes! #466 (extensible introducer announcements) would make this pretty easy: the biggest challenge would be deciding the name of the dictionary key.

Yes! #466 (extensible introducer announcements) would make this pretty easy: the biggest challenge would be deciding the name of the dictionary key.

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#650

No description provided.