Group: Ipernity User Help Central


☑ Chrome does not display ipernity images embedded in third-party websites as default


Team
By A Team club
17 Sep 2021 - 7 comments - 275 visits- Permalink   |   Translate title into English

For the past 2 years, Google has been pursuing a strategy of banning content from non-encrypted websites from the web: blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html

As a result, content linked back to ipernity will not be displayed. Instead, Chrome presents the following screen by default for this website www.clubespacephoto.org

Screenshot 2021-09-17 08.53.01a

Firefox, on the other hand, shows the full web page and thus once again provides an argument why it is more user-friendly browser.

Screenshot 2021-09-17 08.53.01b

We therefore again recommend using Firefox as the default browser. It is fast, secure and rarely makes any problems for us.

Nevertheless, Chrome users do not have to give up in such cases. The Chrome setting in question can be changed. Below you will find the steps you need to take in the three main languages. Afterwards, Chrome will also work without any problems.

The topic of this discussion has been edited by Team 2 years ago.

7 comments - The latest ones
 Team
Team club
[EN]

To display embedded content in such cases, go to

- Options (the three dots at the top right of the browser main bar)
- Settings
- Privacy and Security
- Site Settings
- Content / Images
- custom settings / may show images
- add under 'Allowed to show images' the URL of the website in question
- click on the added URL
- click on 'Allow insecure content' in the menu that opens.

The complexity is not our fault, it's Google's. Sorry.
2 years ago. Edited 2 years ago.
Marja Savonije club has replied to Team club
So you need to "allow insecure content". That sounds stupid.
2 years ago.
ୱ Kiezkickerde ( ͡°… club has replied to Marja Savonije club
It sounds stupid but it wasn´t because you are surfing also on ipernity which is also in most areas just http. But that´s not a problem at all because all pages which really need a higher level of security (like login pages, payment pages and so on) are using https.
If you sending or reeding a comment you simple don´t need such a high security level - what should happen with the text of a comment after you or the webserver send it? Or if you watch for photos - what should happen to a photo after you send your request to the webserver that it should send you this photo so you can see it?
It´s the same issue and reason as described in www.ipernity.com/group/36014/discuss/195128/comment/63491962#comment63491962
2 years ago.
Bergfex club has replied to Marja Savonije club
One does not generally 'allow insecurte content'.

Firstly, Google's wording is semantically wrong. It is not about 'insecure content', but unencrypted content. Secondly, with such browser settings you only allow it for a single defined page, not in general. Thirdly, you allow only unencrypted third party images.

As Kiezkicker has already explained: What sense does it make to encrypt an image during transmission that is going to be made public anyway? Someone who intercepts it could save his/her work because he/she will find the image on ipernity and in search results anyway.

ipernity is not insecure! It's just that a lot of content isn't encrypted because it's pointless.

See my article: The power of misused words
2 years ago. Edited 2 years ago.
Marja Savonije club has replied to Bergfex club
I understand both your explanations. As I have never had any experience not to be able to see whatever site I prefer not to change the Google security settings. Thanks for the explanations!
2 years ago.
 Team
Team club
[FR]

Pour rendre le contenu intégré visible dans de tels cas, allez à l'adresse suivante

- Options (les trois points en haut à droite de la barre principale du navigateur)
- Paramètres
- Vie privée et sécurité
- Paramètres du site web
- Contenu / Images
- paramètres personnalisés / peut montrer des images
- ajouter
- saisissez l'URL du site web en question dans le masque de saisie qui s'ouvre.
- cliquez sur l'URL que vous avez saisie
- cliquez sur "Autoriser les contenus dangereux" dans le menu qui s'ouvre.

Le fait que ce soit si compliqué n'est pas de notre fait, mais de celui de Google. Désolé.
2 years ago. Edited 2 years ago.
 Team
Team club
[DE]

Um eingebettete Inhalte in solchen Fällen sichtbar zu machen, gehe zu

- Optionen (die drei Punkte rechts oben in der Browser Hauptzeile)
- Einstellungen
- Datenschutz und Sicherheit
- Webseite-Einstellungen
- Inhalte / Bilder
- benutzerdefinierte Einstellungen / dürfen Bilder anzeigen
- hinzufügen
- gib in die sich öffnende Eingabemaske die URL der betroffenen Webseite ein
- klicke auf die eingegebene URL
- klicke im Menü, das sich dann öffnet, 'Unsichere Inhalte zulassen'

Dass es so kompliziert ist, liegt nicht an uns, sondern an Google. Sorry.
2 years ago. Edited 2 years ago.

You must be a member of this group to reply to this topic. (Join?)