Made a few changes in the mailchimp before sending June that we should update in template:

• Logo to 200px
• Add some text into with donation & unsubscribe link
• Make sure we use correct social links in footer

(I saved this as a mailchimp template as well.)

Other notes:

• We should try make sure any terms/tech has a brief little description (e.g. Cabal, SSB, etc). I added a line to the cabal section but we can make sure to include this on future ones.

Referenced logo is outdated, but an issue has been created at dat-ecosystem-archive/design/issues/31

Originally posted by @todrobbins in #3 (comment)

I have been recently pinged by people mentioning that the newsletter with the next comm-comm meeting didn't arrive, presumably because no-one sent out one? How will the newsletter work in future?

SoapDog from SSB got Dat archives loading in Patchfox, a Firefox based SSB client. %efD09B2e/0R82ZgfKauE3neTpIstYlVXFkg3D5PgBMs=.sha256

Context:

• In #5, the April newsletter, I wanted to add Transparent Salaries under Community Projects.
• Transparent Salaries is a Beaker-Browser website that you can buy copies of from Gumroad.
• @RangerMauve refused to add it: "I don't think that paid projects are in the spirit of the newsletter.".

I clearly disagree. And, to be honest, Transparent Salaries in a limbo state and adding it doesn't really matter much to me. But I think refusing paid projects might set a dangerous precedent in the community.

So, what are the reasons paid projects aren't in the spirit of this newsletter?

GPM https://github.com/geut/building-up-on-dat/tree/master/packages/gpm

Also get Diego's slides

Is there some easy way we can automagically add newsletters to the blog for x-post <3?

The last one we have on the blog was in July, but it looks like we have some more recent newsletters..

Hey all!

Post any links or ideas for the newsletter for June here. 😁

Feel free to post links to anything interesting you saw in September

I'd like to get the newsletter figured out some time before the end of the month.

This is following up from the conversation here

Here's what I'm thinking we'll need to figure out

• Reach out to the community to learn what they'd like to see
  • Links for new things?
  • Updates from the dat project / what our focus is
  • Summaries of working group / comm comm meetings?
• Figure out how the posts will be authored
  • Markdown?
  • A template?
• Figure out how the posts will be sent out
  • Github Hooks?
  • Pull requests?
  • Manually hitting send?
• Frequency?
  • Every month?
  • Every two weeks?

cc @todrobbins @joehand @Karissa

Hey all, post any links you think should go in the May newsletter

Here's some stuff off the top of my head:

@cblgh's summary of some Dat stuff from DTN: https://merveilles.town/@cblgh/102141050711422037

The official DTN recap post: https://hx.ht/#post-04-dtn-recap

@sammacbeth's post about getting his Dat web extension working: https://sammacbeth.eu/blog/2019/05/12/dat-for-firefox-2.html

Livestream from the Dat event on Sunday: https://twitter.com/dat_project/status/1130094584602800129

Some visuals drawn up by @_irina for some of the talks at DTN: https://twitter.com/_lrlna/status/1129361644134567936

Cabal-desktop got fixed up by @Karissa! https://github.com/cabal-club/cabal-desktop

We sent out the first newsletter last month: https://mailchi.mp/881088ed65b0/dat-news-announcements-three-protocols-and-a-future-of-the-decentralized-internet-comm-comm-and-more