POST /2/message Will it allow for html in the body

[richard]

I'm trying to embed links in the message.  

Something simple like

message=<a%20href=%22http://www.meetup.com%22>Meetup</a>

Can you tell me what I need to do to get it to not read this as text but as html?

[Doug Tangren]

Hi Richard. This text is what gets rendered inside of email templates generated by the site's backend along with other member to member messages submitted on the site. Since those emails may also be marked up as html, user submitted text is sanitized things that may cause those templates to render in unsuspected ways. There isn't currently a way in the API to interpret these messages as anymore than plain text.

 

[*Dominique*]

It would be really nice if at minimum the backed code would turn URLs into hyperlinks as I believe it does for text entered via the Web front end.

Dominique

--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to
meetup-api+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

[Mike Fulton]

On Tuesday, October 9, 2012 11:48:37 AM UTC-7, Doug Tangren wrote:

Hi Richard. This text is what gets rendered inside of email templates generated by the site's backend along with other member to member messages submitted on the site. Since those emails may also be marked up as html, user submitted text is sanitized things that may cause those templates to render in unsuspected ways. There isn't currently a way in the API to interpret these messages as anymore than plain text.

 

I understand the problem, but wouldn't it make more sense to "sanitize" the text when it's put into the email rather than when it's submitted via the API?

And if it *must* be "sanitized" then why not do it with the same rules as the website's event editor?  While the website's event editor is already stripping out enough stuff to be annoying, it seems like the API "sanitize" is far more nuclear-powered. I'd rather have the web editor's subset of HTML than nothing.

I am currently working on a feature that will post events via the API and it's going to be crippled if I am restricted to plain text.

Mike

[Mike Fulton]

On Tuesday, October 9, 2012 11:48:37 AM UTC-7, Doug Tangren wrote:

Hi Richard. This text is what gets rendered inside of email templates generated by the site's backend along with other member to member messages submitted on the site. Since those emails may also be marked up as html, user submitted text is sanitized things that may cause those templates to render in unsuspected ways. There isn't currently a way in the API to interpret these messages as anymore than plain text.

Oh, also... if this restriction cannot be lifted, can we at least get the API documentation edited to mention it? 

I'll admit, I made an invalid assumption that HTML was allowed, but that was based on the fact that the web editor does allow it to a certain degree, and the fact that the documentation doesn't say otherwise.

[Doug Tangren]

Hi Mike,

Sorry for the restriction but we have to be very careful about free form user-submitted input when it comes to markup. The text editor we use on the site has in some ways dictated how and what we escape. I can say there there is an internal effort to develop a minimalist markup scheme that will be well defined. When this goes into effect both the site and official Meetup client apps ( which use the same public API available to you ) will be using it. At that point it would be easier to document in the public API.

 

Mike

--

--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to
meetup-api+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en
 

---

You received this message because you are subscribed to the Google Groups "Meetup API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[salt...@gmail.com]

I just wanted to mention that you have a similar discrepancy with the event description. The API is stripping things that the Web site is not. We are waiting for a fix to that too.

Dominique

[Mike Fulton]

I can understand that you wouldn't want to allow just anything to be included, but it doesn't make sense for it to strip things that would be allowed by the web-based editor.  There should be consistency in what's allowed.

Any timeframe on this new "minimalist markup scheme" ?

Mike