shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

270
active users

#tbsync

5 posts1 participant0 posts today
Bill Taroli :neurodiversity:<p>🧵 2/5 Further, the “native” connection to EWS/OWA within Thunderbird is only available in 140 when you enable a custom setting (search for “ews”). What you see in the new Account Hub will depend on whether that custom setting is enabled. </p><p><a href="https://federate.social/tags/thunderbird" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>thunderbird</span></a> <a href="https://federate.social/tags/tb140" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tb140</span></a> <a href="https://federate.social/tags/TbSync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TbSync</span></a> <a href="https://federate.social/tags/EAS4TbSync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EAS4TbSync</span></a> <a href="https://federate.social/tags/exchange" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>exchange</span></a> <a href="https://federate.social/tags/ews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ews</span></a> <a href="https://federate.social/tags/owa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>owa</span></a> <a href="https://federate.social/tags/eas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eas</span></a> <a href="https://federate.social/tags/imap" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>imap</span></a> <a href="https://federate.social/tags/pop3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pop3</span></a> <a href="https://federate.social/tags/smtp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>smtp</span></a> <a href="https://federate.social/tags/GraphAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GraphAPI</span></a> <a href="https://federate.social/tags/WhyIsMicrosoftSoHard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WhyIsMicrosoftSoHard</span></a></p>
Bill Taroli :neurodiversity:<p>🧵 3/5 Right now, Exchange requires add-ons to work. Usually this means TbSync or OWL. Each of these has its own set of features and limitations to consider. Account Hub will show you Exchange in two flavors… one says “add-on required” and the other doesn’t. It’s the latter one that is the native integration in experimental form at this time (and does email ONLY for now). </p><p><a href="https://federate.social/tags/thunderbird" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>thunderbird</span></a> <a href="https://federate.social/tags/tb140" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tb140</span></a> <a href="https://federate.social/tags/TbSync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TbSync</span></a> <a href="https://federate.social/tags/EAS4TbSync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EAS4TbSync</span></a> <a href="https://federate.social/tags/exchange" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>exchange</span></a> <a href="https://federate.social/tags/ews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ews</span></a> <a href="https://federate.social/tags/owa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>owa</span></a> <a href="https://federate.social/tags/eas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eas</span></a> <a href="https://federate.social/tags/imap" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>imap</span></a> <a href="https://federate.social/tags/pop3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pop3</span></a> <a href="https://federate.social/tags/smtp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>smtp</span></a> <a href="https://federate.social/tags/GraphAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GraphAPI</span></a> <a href="https://federate.social/tags/WhyIsMicrosoftSoHard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WhyIsMicrosoftSoHard</span></a></p>
Bill Taroli :neurodiversity:<p>🧵 4/5 Until now, I have been using IMAP+SMTP, and TbSync for address books and calendars. After going through a few iterations, I have now settled on using Exchange (native, experimental) accounts (yes, plural) for email and sticking with TbSync for calendars and address books.</p><p><a href="https://federate.social/tags/thunderbird" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>thunderbird</span></a> <a href="https://federate.social/tags/tb140" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tb140</span></a> <a href="https://federate.social/tags/TbSync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TbSync</span></a> <a href="https://federate.social/tags/EAS4TbSync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EAS4TbSync</span></a> <a href="https://federate.social/tags/exchange" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>exchange</span></a> <a href="https://federate.social/tags/ews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ews</span></a> <a href="https://federate.social/tags/owa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>owa</span></a> <a href="https://federate.social/tags/eas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eas</span></a> <a href="https://federate.social/tags/imap" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>imap</span></a> <a href="https://federate.social/tags/pop3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pop3</span></a> <a href="https://federate.social/tags/smtp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>smtp</span></a> <a href="https://federate.social/tags/GraphAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GraphAPI</span></a> <a href="https://federate.social/tags/WhyIsMicrosoftSoHard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WhyIsMicrosoftSoHard</span></a></p>
Bill Taroli :neurodiversity:<p>🧵 5/5 TbSync was a small challenge because, as has happened in the past with major Thunderbird updates, it was declared unsupported and automatically disabled by Thunderbird 140esr. Following the instructions in <a href="https://github.com/jobisoft/TbSync/issues/753#issuecomment-3051737579" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/jobisoft/TbSync/iss</span><span class="invisible">ues/753#issuecomment-3051737579</span></a> (file-based reinstall of TbSync and EAS-4-TbSync) resolves the issue for now.</p><p><a href="https://federate.social/tags/thunderbird" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>thunderbird</span></a> <a href="https://federate.social/tags/tb140" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tb140</span></a> <a href="https://federate.social/tags/TbSync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TbSync</span></a> <a href="https://federate.social/tags/EAS4TbSync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EAS4TbSync</span></a> <a href="https://federate.social/tags/exchange" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>exchange</span></a> <a href="https://federate.social/tags/ews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ews</span></a> <a href="https://federate.social/tags/owa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>owa</span></a> <a href="https://federate.social/tags/eas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eas</span></a> <a href="https://federate.social/tags/imap" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>imap</span></a> <a href="https://federate.social/tags/pop3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pop3</span></a> <a href="https://federate.social/tags/smtp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>smtp</span></a> <a href="https://federate.social/tags/GraphAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GraphAPI</span></a> <a href="https://federate.social/tags/WhyIsMicrosoftSoHard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WhyIsMicrosoftSoHard</span></a></p>
Bill Taroli :neurodiversity:<p>🧵 1/5 <span class="h-card" translate="no"><a href="https://mastodon.ie/@padraig" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>padraig</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.online/@thunderbird" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>thunderbird</span></a></span> Took a little searching but I am working again! Yay. The complexity is that which setup to use with Exchange can be legacy (POP3, IMAP+SMTP, EAS, EWS/OWA) or current Graph API. Thunderbird 140 supports all of the legacy API but not yet Graph API.</p><p><a href="https://federate.social/tags/thunderbird" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>thunderbird</span></a> <a href="https://federate.social/tags/tb140" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tb140</span></a> <a href="https://federate.social/tags/TbSync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TbSync</span></a> <a href="https://federate.social/tags/EAS4TbSync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EAS4TbSync</span></a> <a href="https://federate.social/tags/exchange" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>exchange</span></a> <a href="https://federate.social/tags/ews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ews</span></a> <a href="https://federate.social/tags/owa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>owa</span></a> <a href="https://federate.social/tags/eas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eas</span></a> <a href="https://federate.social/tags/imap" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>imap</span></a> <a href="https://federate.social/tags/pop3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pop3</span></a> <a href="https://federate.social/tags/smtp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>smtp</span></a> <a href="https://federate.social/tags/GraphAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GraphAPI</span></a> <a href="https://federate.social/tags/WhyIsMicrosoftSoHard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WhyIsMicrosoftSoHard</span></a></p>
Bill Taroli :neurodiversity:<p><span class="h-card" translate="no"><a href="https://mastodon.online/@thunderbird" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>thunderbird@mastodon.online</span></a></span> <span class="h-card" translate="no"><a href="https://tilvids.com/accounts/thunderbird" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>thunderbird@tilvids.com</span></a></span> So… is anyone keeping tabs on <a href="https://federate.social/tags/Betterbird" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Betterbird</span></a>? I can’t say I’m fond of everything they’ve done, but in the world of “we care about using Graph with <a href="https://federate.social/tags/O365" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>O365</span></a> <a href="https://federate.social/tags/Exchabge" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Exchabge</span></a>” this is starting to gain steam. I’m resisting g the fork, but I’m curious what the team has to say on the subject. </p><p>Indeed the latest round of chat revolved around a version of <a href="https://federate.social/tags/TbSync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TbSync</span></a> hacked to talk to <a href="https://federate.social/tags/GraphAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GraphAPI</span></a>.</p><p><a href="https://federate.social/tags/Office365" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Office365</span></a> <a href="https://federate.social/tags/Thunderbird" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Thunderbird</span></a></p>