Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://federate.social/users/jik/statuses/113115839535619155">Jonathan Kamens (jik@federate.social)'s status on Monday, 16-Sep-2024 02:42:04 JST</a><a href="https://federate.social/@jik" title="jik@federate.social"><img src="https://gnusocial.jp/avatar/112846-48-20230416171343.webp" width="48" height="48" alt="Jonathan Kamens" style="position: absolute; left: 0; top: 0;">Jonathan Kamens</a></section><article><p>The repeated logins and separate contact info stored for each nonprofit at <a href="https://classy.org/" rel="nofollow noreferrer">https://classy.org/</a> seem weird at first, but after some thought they make sense.<br>The repeat logins are necessary because each org site is under the org's TLD, so each needs a separate login cookie.<br>The separate contact info makes sense because nonprofits don't want their data commingled with other nonprofits' data.<br><a href="https://federate.social/tags/ChangeOfAddress" rel="tag">#ChangeOfAddress</a> 🧵</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3673031#notice-7196984">In conversation</a><time datetime="2024-09-16T02:42:04+09:00" title="Monday, 16-Sep-2024 02:42:04 JST">about 2 months ago</time> <span>from <span><a href="https://federate.social/@jik/113115839535619155" rel="external" title="Sent from federate.social via ActivityPub">federate.social</a></span></span><a href="https://federate.social/@jik/113115839535619155">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: www.classy.org</div><h5><a href="https://www.classy.org/">Classy Online Fundraising Platform</a></h5><div></div></header><div>Classy's fundraising solutions help you transform transactions into relationships. Discover why thousands of nonprofits choose Classy.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Jonathan Kamens (jik@federate.social)'s status on Monday, 16-Sep-2024 02:42:04 JST Jonathan Kamens
The repeated logins and separate contact info stored for each nonprofit at https://classy.org/ seem weird at first, but after some thought they make sense.
The repeat logins are necessary because each org site is under the org's TLD, so each needs a separate login cookie.
The separate contact info makes sense because nonprofits don't want their data commingled with other nonprofits' data.
#ChangeOfAddress 🧵
In conversationabout 2 months ago from federate.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: www.classy.org
  Classy Online Fundraising Platform
  Classy's fundraising solutions help you transform transactions into relationships. Discover why thousands of nonprofits choose Classy.

Public

Embed Notice

HTML Code

Corresponding Notice