NEW BOLTON MARCH 2017 WORKSHOP VENUES ANNOUNCED
- St Paul’s Astley Bridge CE Primary School BOLTON
- St Catherine’s CE Primary, Horwich, BOLTON
- Eagley Junior School, BOLTON
- Kearsley West Primary School, BOLTON
Musical.ly co-CEO Alex Zhu last year said:
“Today the very proposition of the app is not about creating music videos. It’s not about lip-syncing. It’s about a social network,” Zhu said. “It’s a community. People want to stay because there are other people. ” Full Article on UK Business Insider
The app is intended for teens not tweens but last year found itself in a social media whirlwind triggered by a Dad’s story who discovered his daughter had been receiving grooming messages from a user profile designed to deceive.
This week, one of the primary schools we support got in touch to say they were contacting parents in writing to advise on the inherent risks associated with the app for younger children. The age limit is 13+ BUT the trap here is that we all get overly focused on this age limit.
Seeing as it’s ‘you’ reading this post then the chances are we’re preaching to the converted and you know that this is as much about being aware what our children are using, open conversations and knowing how to manage privacy as much as any age limit.
Useful to watch
We quickly made this video to be shared with schools to help parents understand how to control just how visible and reachable they are on Musical.ly. This is all common sense stuff and applies to other networks too as you’ll already know.
Useful to read
Webwise is the Irish Internet Safety Awareness Centre which is co-funded by the Department of Education and Skills and the EU Safer Internet Programme.
Musical.ly has this for parents
Here’s something that not a lot of people know.
There’s a goal in mind for the web and that is to enable every website address to begin with https:// instead of http:// so that the data that passes between site and sender/visitor is encrypted. Google are big supporters of it amongst others.
Here’s something that not a lot of people know either.
This is the how the various web browsers that people use globally compare and yes, back there in the distance is Internet Explore & Edge with Chrome beating way out in front.
Why are these ‘pub trivia’ facts important?
Well, at the end of January this year, Google’s latest version of Chrome (v56) (the dead popular one) will ultimately start telling visitors to your school website whether it’s secure or not.
What are the benefits of going secure?
What can your school do about it?
Your web site host will have a very easy and quick method of applying a security certificate to your website thus making it secure for visitors and site managers. It’s pretty rare that the school tech support would touch this job so unless they’re the person who built and hosted your website we suggest leaving them well alone. This Google site has a technical guide for how to implement an SSL so if your tech is the person they may want this link. Schools who have a Blippit Site are already compliant with SSL in place.
Our suggestion would be to get the ball rolling tomorrow with a quick email to your provider saying:
We’d like you to apply an SSL certificate to our school website please. We’d like to do this for 12 months initially and need this in place by February or March at the latest. Can you let us know what we need to do on our part to do this e.g. forward an email from the certificate issuing authority to you when it comes?
<School Who Knows What They’re Talking About>”
What happens if we don’t get a security certificate applied to the school website?
You can carry on as you are and everything will stay the same. The main issue is that the world’s most widely used web browser will start telling visitors that your site is not secure and in this day and age that’s probably not what you want.
Good luck & support a more secure web!
LetsEncrypt runs the certificate authority that issues free SSL certificates so cost is no longer a barrier to using HTTPS and both Google and Mozilla to actively promote and recommend the use of HTTPS as standard.