teraßyte

Template output plugins require double quotes. Try this:
{graphql="{core{me{name,url}}}"}  

Template output plugins require double quotes. Try this:
{graphql="{core{me{name,url}}}"}  

Template output plugins require double quotes. Try this:
{graphql="{core{me{name,url}}}"}  

One of these things is not like the other. 😄 







 
 

EDIT: @AlexWebsites has already made same suggestion. 

Why don't you use a pre-fix with the title like: [Cloud Only] New Live Community Features!
Save all us self-hosters some time in our day...

Considering they just removed all of the code for the native app that was being built...  I would assume that would be:
      
🤣

My 2 cents.
Make a notification when a members' post is chosen as a best answer or gets an upvote.
When a member wins a 1-3 place on leaderboard.
 

Will this allow the member to use the same password as they had before? Kind of defeats the purpose if they can.

@Matt On deletion of members: 
Could there be an option to define the name to attribute to on that page directly? So we could input for example "Member 3312" (where 3312 would be their memberId). This will keep the discussion still somewhat reader friendly, so it would still be possible to differentiate different accounts as having written in the discussion, for readers reading old content. 
Alternatively let the Anonymize attribution do a md5 hash on the (memberId+some community specific value that is unlikely to be changed) and grab the first 8 letters or something. 

Isn't this the old "Promote to article" feature? I guess the change is that now you can choose any database and not just articles (and copy all posts). But yeah, being able to use it for other application would be a much better improvement. I guess it could be supported using a new application extension.