#addressbooks — Public Fediverse posts

Popular Science: Flip through Charles Darwin’s digitized address book. “If you’ve ever wondered whose addresses Charles Darwin was sure to keep tabs on—or even a few rat poison recipes—you’re in luck. A digitized edition of the famed naturalist’s personal address book is available online for the first time.”

https://rbfirehose.com/2025/11/30/popular-science-flip-through-charles-darwins-digitized-address-book/

If you'd like to migrate your #AddressBooks and #calendars from somebody else's platform to a self-hosted or self-managed one, but there's no "migration assistant":

Check whether both platforms support the #CalDAV and #CardDAV standards. If they do, look into #vdirsyncer https://vdirsyncer.pimutils.org

We'd recommend to test-migrate your existing data to a local filesystem storage first, and swap in your new storage only when syncing to the test storage worked without errors.

To protect yourself against migration blunders, mark your source storage (platform) as read_only and let it "win" in your conflict_resolution setting.

For address book pairs, you can also sync the "displayname" and "description" metadata – for calendar pairs, additionally "color" and "order".

If you'd like to migrate your #AddressBooks and #calendars from somebody else's platform to a self-hosted or self-managed one, but there's no "migration assistant":

Check whether both platforms support the #CalDAV and #CardDAV standards. If they do, look into #vdirsyncer https://vdirsyncer.pimutils.org

We'd recommend to test-migrate your existing data to a local filesystem storage first, and swap in your new storage only when syncing to the test storage worked without errors.

To protect yourself against migration blunders, mark your source storage (platform) as read_only and let it "win" in your conflict_resolution setting.

For address book pairs, you can also sync the "displayname" and "description" metadata – for calendar pairs, additionally "color" and "order".

In #I2P, it's possible to have different b32 addresses for a single domain.

Eg. when #nameRegistries have different persistence policies.

We looked into this and found a number of conflicting addresses. When visiting one of these sites we weren't informed a conflict existed among our three #addressBooks.

Can #eepsites gain redundency from this or will the router always pick the same address?

#askFedi @i2p @sadiedoreen

In #I2P, it's possible to have different b32 addresses for a single domain.

Eg. when #nameRegistries have different persistence policies.

We looked into this and found a number of conflicting addresses. When visiting one of these sites we weren't informed a conflict existed among our three #addressBooks.

Can #eepsites gain redundency from this or will the router always pick the same address?

#askFedi @i2p @sadiedoreen