#vdirsyncer — Public Fediverse posts

#TerSoftware de linha de comando:

- #todotxt
- #git, tanto na linha de comando quanto integrado ao RStudio
- #APT, apesar de o GNOME Software fazer um bom trabalho
- #Neovim (aprendendo) e #MicroTextEditor (para tarefas simples)
- #QuartoPub, apesar de geralmente usar pelo #RStudio
- #RStats, apesar de usar mais pelo RStudio
- #RClone, #Restic, #OfflineIMAP, #VDirSyncer para backup
- #SSH
- GNU #CoreTools, #Sudo, #SystemD

#blambers

#TerSoftware de linha de comando:

- #todotxt
- #git, tanto na linha de comando quanto integrado ao RStudio
- #APT, apesar de o GNOME Software fazer um bom trabalho
- #Neovim (aprendendo) e #MicroTextEditor (para tarefas simples)
- #QuartoPub, apesar de geralmente usar pelo #RStudio
- #RStats, apesar de usar mais pelo RStudio
- #RClone, #Restic, #OfflineIMAP, #VDirSyncer para backup
- #SSH
- GNU #CoreTools, #Sudo, #SystemD

#blambers

#TerSoftware de linha de comando:

- #todotxt
- #git, tanto na linha de comando quanto integrado ao RStudio
- #APT, apesar de o GNOME Software fazer um bom trabalho
- #Neovim (aprendendo) e #MicroTextEditor (para tarefas simples)
- #QuartoPub, apesar de geralmente usar pelo #RStudio
- #RStats, apesar de usar mais pelo RStudio
- #RClone, #Restic, #OfflineIMAP, #VDirSyncer para backup
- #SSH
- GNU #CoreTools, #Sudo, #SystemD

#blambers

#TerSoftware de linha de comando:

- #todotxt
- #git, tanto na linha de comando quanto integrado ao RStudio
- #APT, apesar de o GNOME Software fazer um bom trabalho
- #Neovim (aprendendo) e #MicroTextEditor (para tarefas simples)
- #QuartoPub, apesar de geralmente usar pelo #RStudio
- #RStats, apesar de usar mais pelo RStudio
- #RClone, #Restic, #OfflineIMAP, #VDirSyncer para backup
- #SSH
- GNU #CoreTools, #Sudo, #SystemD

#blambers

#TerSoftware de linha de comando:

- #todotxt
- #git, tanto na linha de comando quanto integrado ao RStudio
- #APT, apesar de o GNOME Software fazer um bom trabalho
- #Neovim (aprendendo) e #MicroTextEditor (para tarefas simples)
- #QuartoPub, apesar de geralmente usar pelo #RStudio
- #RStats, apesar de usar mais pelo RStudio
- #RClone, #Restic, #OfflineIMAP, #VDirSyncer para backup
- #SSH
- GNU #CoreTools, #Sudo, #SystemD

#blambers

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".

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".

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".

Is there a way for #vdirsyncer to display new and modified appointments when I sync them? Like a changelog. Seems extremely helpful and common, but I can't find it in the docs.

Does anyone have an example config for #vdirsyncer and #khal for home-manager on #nixos? I read the documentation but it stops at the actual collections/remotes, or at least gets pretty opaque.

Just found carl, a modern version of cal (the unix calendar utility that prints a tabular view of months).

What stands out for me here is the ability to highlight events from calendar files.

This is superb in conjunction with vdirsyncer, which I’ve been using for a long time for exactly the purpose of having a local directory of .ics files for each of my Nextcloud DAV calendars.

https://github.com/b1rger/carl

Also featured in my link log: https://blog.jutty.dev/links

#unix #linux #cli #vdirsyncer

@whynothugo congrats on the stable release of the #vdirsyncer rewrite!

In your blog post you mention that it's not feature complete when compared with the old version, do you have a list somewhere of what's missing so I could see if I'd be able to try out the new version?

https://whynothugo.nl/journal/2024/09/29/vdirsyncer-status-update-2024-09/

Who thought it was a good idea to let #vdirsyncer print "uploading item [id] to [name of local calendar]" when it's actually simply inserting some event from the remote side to the local one?

Imagine my anxiety when I tried to make extra sure (with read_only=true etc.) that it does NOT modify my Google Calendar while I'm setting everything up, only to then read hundreds of "uploading" messages?

(It simply always says "uploading", no matter what the destination is.)

#Linux #CLI #UX

I finally found a workaround for my issue with #NextCloud calendars. #VDirSyncer is the answer.

We share calendars with my fiancée to see each other's program but also invite each other to events that we want the other to attend.
NextCloud sadly has event ids unique across all calendars, thus this use case creates many id collisions between calendars.

When Vdirsyncer copies events from ics to caldav it does not use event ids, but creates own hash id from event content.

https://github.com/nextcloud/calendar/issues/5277

Ok, da ist echt was im Argen. Von der manuell erstellten Liste mit den 8 noch fehlenden Terminen, ist der Import schon wieder für zwei Termine gescheitert. Dieses Mal aber immerhin mit einem Fehler. Leider kann man von dem Fehler aber nicht auf die fehlenden Termine schließen.

Das ist mir jetzt doch zu doof und die Feiertage/Ferien habe ich jetzt über die Kommandozeile mit #khal importiert und mit #vdirsyncer nach #nextcloud synchronisiert.

Das läuft schon länger, wird aber selten genutzt.

Please tell me I am not the only one whose #addressbook is filled with actual contact pictures, birthdays and as much detail as possible about their #contacts?

Of course, everything self-hosted on #Nextcloud, synced with #DAVx5 and #vdirsyncer

Please tell me I am not the only one whose #addressbook is filled with actual contact pictures, birthdays and as much detail as possible about their #contacts?

Of course, everything self-hosted on #Nextcloud, synced with #DAVx5 and #vdirsyncer

Please tell me I am not the only one whose #addressbook is filled with actual contact pictures, birthdays and as much detail as possible about their #contacts?

Of course, everything self-hosted on #Nextcloud, synced with #DAVx5 and #vdirsyncer

Please tell me I am not the only one whose #addressbook is filled with actual contact pictures, birthdays and as much detail as possible about their #contacts?

Of course, everything self-hosted on #Nextcloud, synced with #DAVx5 and #vdirsyncer

Please tell me I am not the only one whose #addressbook is filled with actual contact pictures, birthdays and as much detail as possible about their #contacts?

Of course, everything self-hosted on #Nextcloud, synced with #DAVx5 and #vdirsyncer

Some thoughts on trying to use my #calendar a bit more and being more #productive because of it. Kinda... This is day 28 of #100DaysToOffload!

Featuring #Orage and #Vdirsyncer integration!

https://joelchrono.xyz/blog/using-my-calendar-more-often/

So, my #FLOSS todo list for the next days:
- get that #Recoll plugin for #Synapse working again
- write that script to make @qownnotes use @pandoc and @libreoffice to generate a PDF booklet
- make that #iBook G4 running again and set up an usable PIM suite using #vdirsyncer, #khal, #khard and #mutt.

If I'm somewhat recreated by that time I'm gonna restart coding on #ObjGTK. But after Christmas I'm really too exhausted to get into deep work too soon. 🤔 🤷‍♂️

So, my #FLOSS todo list for the next days:
- get that #Recoll plugin for #Synapse working again
- write that script to make @qownnotes use @pandoc and @libreoffice to generate a PDF booklet
- make that #iBook G4 running again and set up an usable PIM suite using #vdirsyncer, #khal, #khard and #mutt.

If I'm somewhat recreated by that time I'm gonna restart coding on #ObjGTK. But after Christmas I'm really too exhausted to get into deep work too soon. 🤔 🤷‍♂️

So, my #FLOSS todo list for the next days:
- get that #Recoll plugin for #Synapse working again
- write that script to make @qownnotes use @pandoc and @libreoffice to generate a PDF booklet
- make that #iBook G4 running again and set up an usable PIM suite using #vdirsyncer, #khal, #khard and #mutt.

If I'm somewhat recreated by that time I'm gonna restart coding on #ObjGTK. But after Christmas I'm really too exhausted to get into deep work too soon. 🤔 🤷‍♂️

So, my #FLOSS todo list for the next days:
- get that #Recoll plugin for #Synapse working again
- write that script to make @qownnotes use @pandoc and @libreoffice to generate a PDF booklet
- make that #iBook G4 running again and set up an usable PIM suite using #vdirsyncer, #khal, #khard and #mutt.

If I'm somewhat recreated by that time I'm gonna restart coding on #ObjGTK. But after Christmas I'm really too exhausted to get into deep work too soon. 🤔 🤷‍♂️

So, my #FLOSS todo list for the next days:
- get that #Recoll plugin for #Synapse working again
- write that script to make @qownnotes use @pandoc and @libreoffice to generate a PDF booklet
- make that #iBook G4 running again and set up an usable PIM suite using #vdirsyncer, #khal, #khard and #mutt.

If I'm somewhat recreated by that time I'm gonna restart coding on #ObjGTK. But after Christmas I'm really too exhausted to get into deep work too soon. 🤔 🤷‍♂️

Today I managed to install and configure
- my contacts (vdirsyncer + khard, formerly khal)
- my calendar (calcurse + calcurse-caldav. Might switch to vdirsyncer)
- my mail (offlineimap + neomutt)
- my todo txt (todo.sh)

Not happy with saving credentials in plain text :-(

But I can look into Lua (conky and awesome WM widgets) next!

#vdirsyncer #khard #khal #calcurse #offlineimap #neomutt #todotxt

Today I managed to install and configure
- my contacts (vdirsyncer + khard, formerly khal)
- my calendar (calcurse + calcurse-caldav. Might switch to vdirsyncer)
- my mail (offlineimap + neomutt)
- my todo txt (todo.sh)

Not happy with saving credentials in plain text :-(

But I can look into Lua (conky and awesome WM widgets) next!

#vdirsyncer #khard #khal #calcurse #offlineimap #neomutt #todotxt

Today I managed to install and configure
- my contacts (vdirsyncer + khard, formerly khal)
- my calendar (calcurse + calcurse-caldav. Might switch to vdirsyncer)
- my mail (offlineimap + neomutt)
- my todo txt (todo.sh)

Not happy with saving credentials in plain text :-(

But I can look into Lua (conky and awesome WM widgets) next!

#vdirsyncer #khard #khal #calcurse #offlineimap #neomutt #todotxt

Today I managed to install and configure
- my contacts (vdirsyncer + khard, formerly khal)
- my calendar (calcurse + calcurse-caldav. Might switch to vdirsyncer)
- my mail (offlineimap + neomutt)
- my todo txt (todo.sh)

Not happy with saving credentials in plain text :-(

But I can look into Lua (conky and awesome WM widgets) next!

#vdirsyncer #khard #khal #calcurse #offlineimap #neomutt #todotxt

Today I managed to install and configure
- my contacts (vdirsyncer + khard, formerly khal)
- my calendar (calcurse + calcurse-caldav. Might switch to vdirsyncer)
- my mail (offlineimap + neomutt)
- my todo txt (todo.sh)

Not happy with saving credentials in plain text :-(

But I can look into Lua (conky and awesome WM widgets) next!

#vdirsyncer #khard #khal #calcurse #offlineimap #neomutt #todotxt

I just had a #dejavu of having set this up before, but here's a simple solution to read-only sync your #CardDAV #contacts to #ClawsMail with #vdirsyncer

🔗 http://vdirsyncer.pimutils.org/en/stable/tutorials/claws-mail.html#vdirsyncer-with-claws-mail

Bonus: If you happen to use the @nextcloud (Android) App with contact backup enabled, you can just open that .vcf file in #claws directly.

#mail #mua #selfhosted #addressbook #sync #tool #cron #vcard

Alright, #TechnicalJiggeryPokery conundrum of the moment:

Two Debian machines, both running stable.

On one, #vdirsyncer and #khal work perfectly.

The other crashes with errors about xdg.basedirectory.

I'm barely capable of understanding the problem, but I think it has to be something garbled up with Python.

Anyone know of either a fix, or a way to cleanly get back to a known good configuration?

I'm on the verge of reinstalling the misbehaving bix because I can't figure out what went wrong.