If you have a question about the Experimenting with Sensor Fusion competition, you can ask it here.

I am finding it very difficult to participate in this challenge due to platform issues. I have had to modify the blogs several times because the new version of Verint treats them as SPAM for having too many Links. I can no longer edit the blogs with either Edge or Chrome because the editor crashes with the 'latest versions of Edge and Chrome. I have installed Firefox but it also fails with code widgets.
At the moment I have managed to publish two blogs and I have a third inaccessible marked as SPAM before even publishing it, marked as SPAM when including the tags and saving as draft.
I try to take advantage of free time to work on the project but blogging is proving to be quite a frustrating experience.

For the rest, thank you very much to the whole team of element14, the development kit is fascinating and I hope to continue telling my experiences with it.

I am finding it very difficult to participate in this challenge due to platform issues. I have had to modify the blogs several times because the new version of Verint treats them as SPAM for having too many Links. I can no longer edit the blogs with either Edge or Chrome because the editor crashes with the 'latest versions of Edge and Chrome. I have installed Firefox but it also fails with code widgets.
At the moment I have managed to publish two blogs and I have a third inaccessible marked as SPAM before even publishing it, marked as SPAM when including the tags and saving as draft.
I try to take advantage of free time to work on the project but blogging is proving to be quite a frustrating experience.

For the rest, thank you very much to the whole team of element14, the development kit is fascinating and I hope to continue telling my experiences with it.

It happened to me today, under these circumstances:

I showed code snippet from GITHUB, where a normal practice is to sign your code and commits with an email address.

The flag message referred to that email address as reason for review.

I'm sorry to hear about your experience. I know our development team is working on it. Let me ask about it tomorrow and see what the pathway to resolving them is. I open open to extending this challenge by several weeks to make up for lost time. 

I submitted a suggestion in the feedback area:  suggestion: moderation queue - warn when saving as draft 

It could allow a writer to keep on writing. And to either let them remove the flagged content, or let the review team decide, when it's time to publish.

Jan,

Thanks for doing that. 

Randall

Sanitizing personally identifiable information from content is a good habit to get into

The weekend wasn't great for site issues, unfortunately, I started today with a swathe of messages of the server admin team working over the weekend to get the server back online and they're taking it up with the website vendor today.

Thanks for all your effort. None of us should work on weekends or break time.