That’s a total letdown. I’ve been citing mailchimp for years fighting against the concept of a single opt-in. Especially surprised that they shared very little data to support the change.
Forum notifications are not the kind of “unsolicited commercial email” generally restricted by law as “spam.”
Key words in bold.
If you sign up for a forum expect to get email from the host and as mentioned that feature should be disclosed in the signup/terms and there should be opt-out preferences.
Totally different than, I have this random email addrress so I am going to send a commercial email.
Email service providers may have broader policies than the law. Also the laws differ by location so how and if you are required to get the consent may differ.
Also “generally” meaning that sending an email about the forum might be ok; third party offers maybe not ok unless those types of emails are disclosed.
I am suggesting get the consent via the signup/terms. Otherwise, even the email digest could be suspect–another reason to add the privacy/term link to the invite page.
Hi All,
With the impending GDPR date soon aproaching. What’s the consensus on sending an email to all of our users notifying them of new privacy policy and information on data control.
All of the various services I belong to this past week have been coming out of the woodwork.
This feature is so useful, I do not understand why the developers are not willing to implement it.
Specially with GDPR it would be great to be able to use discourse as a mailing list and have all users in a single place.
Why are you not implementing this? other people mentioned that this a basic functionality in other forum software
Would this work for you?
- Set up an Announcements category that every person who registers watches first post by default (can be set in admin settings)
- Allow only staff to post in the Announcements category to protect users from spam (can be set in category settings)
Now when you post in Announcements, everyone gets the notification, including people who haven’t signed in because with them watching first post, they’ll get emailed with the full text of the post.
That is exactly what we do. I was puzzled once because I needed to pin a new banner but wanted to make sure that people had access to previous banners and announcements. After all, announcements usually carry information that is useful but once read, if it remains in the landscape, people won’t see it anymore. So I made optin to receive the first post the default for that category, and each new announcement is a new topic. It keeps history, users can all read but only admins can post. Each announcement gets also pinned until it is replaced by a new one. People can of course opt-out from watching announcement but from what I observe, it is one of the most watched channels.
Anche io. È una bella frase. Sono finito anch’io in questa discussione cercando un’opzione del genere.
Ma questo è un punto, e un punto ben espresso. Grazie @awesomerobot
Non sono sicuro di capire cosa state facendo in termini di fissaggio dei topic. Potreste spiegare meglio? Se tutti vengono avvisati dell’ultimo topic di annuncio, a cosa serve un topic fissato, mi chiedo…
Credo che la maggior parte delle intenzioni alla base di questa richiesta di funzionalità possa essere soddisfatta combinando il fissaggio di nuovi post come suggerito sopra con i riassunti programmati.
Molto dell’interesse qui è legato a un caso d’uso per newsletter. Una combinazione di argomento newsletter, un post fissato per gli utenti attivi/che visitano il sito e un riassunto programmato (per utenti inattivi/passivi), credo soddisferebbe gran parte della domanda.
Attualmente, tuttavia, non sono sicuro che sia possibile programmare un riassunto in questo modo:
-TorqueWrench
Pin del banner. Per chi sceglie di non visualizzare i nuovi post. E perché è lì che sollecitiamo sponsorizzazioni trimestrali.
Quando ho pubblicato per la prima volta questo contenuto, la strategia preferita era “guarda il primo post”, ma c’era un bug con quella funzionalità sul nostro sito: i nuovi account non si attivavano quando la funzionalità era abilitata. Non ho mai verificato in seguito se il team avesse trovato una soluzione per questo problema.
Grazie. Ho ora implementato questo come test (nessun pin, ma tieni d’occhio il primo post come predefinito) e vedrò semplicemente come la comunità lo accoglie… Voglio allontanarmi dalle newsletter via email perché Mailch*** e simili sono un vero fastidio ![]()