Illustrations

It is strongly advised to choose the level of image privacy before the images become uploaded. If you upload images as public, when they are supposed to become turned as private and shared for example with family only, anyone online gets a few seconds or even minutes chance to view and comment those images. So, consider setting the access permissions before you upload. First hover the cursor over one of the files you are going to upload: Then click on it to open the permission settings seen on the main image. Choose " Apply to all files to upload ", and click 'APPLY'. If for some reason this does not work for you, and you get an error message instead, then please check that you don't have an extension blocking ipernity.com . Or use 'Organize' tool to do the same: We also discovered a bug. If you upload images first as public, and next fave them (add star) before you turn them private, those images then stay visible on your personal faves: www.ipernity.com/doc/serola/favorite/self There on my personal faves among my own photos you should not see a photo of egg shells. But you do because of a bug in the ipernity code.

1. Choose album 2. Click 'Upload from your computer' 3. Choose file(s) 4. Choose visibility (aka privacy, aka authorization) 5. Click 'UPLOAD'

If you are missing some features like unable to add location on the map or unable to change the authorization on uploader, then you may have some extension blocking those features. What you then have to do is whitelist ipernity.com. How to do that may vary, but here's how to do that on AdBlock for Firefox: On AdBlock Dashboard and whitelist you add a new line and write there the URL address of ipernity home page and put /* into the end of the line. The asterisk symbol * in the end of the URL means that all pages under that web site are then ignored by AdBlock extension. The syntax may vary, but this is probably the most common one. There are many different advertisement blocking extensions, and how to access and edit the whitelist on them can be tricky. I do recommend visiting on their own help pages to find out more specific instructions. You can also ask and share help here on comments. Ignoring (whitelisting) all pages at ipernity can be done because we do not have any advertisements here. Well yes, those SPAM accounts popping out on daily bases of course, but we keep on trying to get them all deleted as soon as they rise their ugly heads. They should not much bother anyone if you stay out of images uploaded recently by all ipernity users . More about whitelists here: github.com/gorhill/uBlock/wiki/Dashboard:-Whitelist github.com/gorhill/uBlock/wiki/How-to-whitelist-a-web-site Instructions for uBlock extension: youtu.be/7SGFoyvl_k4

➽ How to embed video onto blog article

➽ How to embed video onto blog article

➽ How to embed video onto blog article

And I was wondering why there was so much memory used on my Android phone! Especially Instagram seem to collect a huge cache. I had over 5GB cache collected by Instagram on my phone! =O ➽ How to clear Instagram cache on Android & iPhone Luckily not many other apps on my phone seem to keep so huge cache. I would call that as a design flaw, to not restrict the size of software cache in any way. I do not know if there are similar issues on PCs. Anyway, cache can be useful to save us from loading data every time when visiting the same web pages, but cache also can take a lot of local memory.

Author : Sami Serola Created : December 8, 2019 Updated : December 22, 2020 When ima team updated the frequently asked questions (FAQ) section , it was decided to use "photo articles" instead of blog articles. The main reason was because the "internal links" on ipernity blog articles opens always on new tab and not on the same tab. From FAQ point of view it is better to open links on the same tab. Moreover, there were no resources to change and fix the way how links are implemented on ipernity articles. But lately I have started to think that if and when ima finally get the reprogramming started, it could be better to combine those two. Instead of having separate articles, one could just as well write what is called as " photoblog " or "photolog", which is sometimes shortened even as "plog". What it would mean is that it should then be possible to write articles also without any image. That is actually how it is done at such photo sharing platform as YouPic. There the stories become displayed as such on the similar news feed as here on ipernity. But here on ipernity it would require some more information displayed than just the author's name and image . Maybe the image title and some of the caption would do, and a symbol to declare that it is indeed an article with no images. Something similar as on one's own personal photos at the moment . But it would also require similar text editing tools provided for image caption as there is currently on blog articles. What I actually did when writing this story, is that I first wrote this on articles tool . Then I (re)viewed it on source mode, corrected misspellings, copied the text with HTML codes, and pasted it onto this "image caption". Although, one can also write the HTML code directly into caption area, if only one knows how to do that. But in this way, copying the text and HTML formatted links from the article tool, one can avoid the HTML formatting mistakes more easily. Then to show some possibilities of inserting also images within the text, I simply copied the image share codes from several images and pasted them here. Currently the beauty of this approach is that one can even remove the links "around" the image codes. Moreover, it is possible to change the dimensions (width&height) to create nice collages. Although, tampering the image codes is somewhat against the terms of service: " Note : do not forget that our Terms of Service impose that the photo must be clickable and that the link must redirect to the ipernity page displaying this photo. " However, I think it is supposed to be an advice to someone who copies the image code (if enabled), and uses it outside ipernity. So, it is supposed to make sure the image represented for example on someone's blog elsewhere would also provide link to the original source. Besides, if one can just as well write similar code also by oneself, and if one only tampers with one's own contents (own images and/or free material online), that should be allowed and okay here at ipernity. I actually admit doing so every now and then. For example sometimes I replace the link with one that opens my private image . Or sometimes I remove the link on PiPs that would direct to "dead end" anyway (link to private image).

Already for years anyone have had a possibility to use Stylish browser extension and something like Ipernity Dark Skin originally developed by Spotomy . That has provided a nice option for geeks like me, to view pages in dim light. Dark background and lighter fonts provide sort of an inverted layout to view pages, which also can be found as more friendly for the eyes. If you already use Stylish, or are interested to use it, you may wish to find out what styles there are available for the ipernity web site: userstyles.org/styles/browse?search_terms=ipernity&type=false So far the option to change the page and font colors has been either the plain default white provided by ipernity, or possible only for geeks who know how to install and use Stylish . Now thanks to Rob, we all have easy to use options to change the page colors. One may argue it violates one's own user account space here at ipernity. However, the user does not "own" the page or font colors. This is now the first step to let the user to change the background colors more easily. Later on it may become possible to change also the font colors. So, you may like it or not, but your audience can now do something as hideous (or nice) as this: The ipernity club member can now change their personal preference of page background, margin (sides) and comment section background colors: Keep in mind that these page color preferences affects only the way how the individual user wishes to view the pages. So, if someone wishes to view ipernity on pink background, it does not change the way how all others sees the pages. Moreover, as ipernity club member you can still decide what is the layout and color theme on your personal account pages (your banner image, title bar text and color, and so called title bar colors on your own pages). And that is how all others will see your ipernity account pages. For example currently I have decided to use one of my images on the banner, light, almost transparent background behind the title, and black background on sub title bars: All this is more or less the same as if the user would get to decide on what color paper they like to print their news paper. One could for example print out this page onto pink paper. However, the contents, texts and images are still the same for all.

PicMonkey API based editor that requires Adobe Flash is no longer an option soon coming to it's end. We need to either give up on such additional service entirely, or find a replacement for it (some HTML5 based API/SDK service). One hardly finds anything for free anymore. So, if we still do wish to have one, it very likely will cost us something. Feedback on this subject is welcome. Here are some online editors available that I have manage to find. ➽ photoeditorsdk.com One option is Photo Editor SDK used at Flickr: photoeditorsdk.com/case-studies . SDK stands for software development kit . The photo above has been edited on Photo Editor SDK to get the text added. All who still have account at Flickr can test it there. ➽ fotor.com Fotor as such does not save EXIF, at least not with the free version. There's no adjustable simple border width, and in my test I had to crop to make the standard black border thinner. Fotor provides SDK , and it may come with extras like print designer, collage maker, and GoArt . ➽ ribbet.com Saves EXIF and provides simple frames easy to add. Currently Ribbet uses Adobe Flash, but has a HTML5 under development. There's similar application programming interface (API) provided as there used to be for PicMonkey. But will that be available once they get their HTML5 editor finished, is still open. May provide also collage maker. ➽ pixlr.com Just rediscover this myself. I will update this part later. However, no API available at the moment . ➽ picmonkey.com PicMonkey is also developing their HTML5 based version, but whether it will be available via API or SDK is still open. Moreover, it very likely is no longer free to use, as their Adobe Flash based API was. Also PicMonkey has their collage maker , but at least that does not seem to be integrated to their photo editor. UPDATE May 13, 2020: We are now informed by PicMOnkey. Unfortunately they are no longer providing API service for their new HTML5 online editor. It means PicMonkey especially is no longer an option in the future. --- Keep in mind that these online photo editors are out there to use anyway. So, I recommend visiting those web sites in case you for example need to make collages. If it is decided to give up providing integrated online photo editor, then there are number of software available out there. PhotoShop and Lightroom are of course the most known, but they are not free. Instead of even trying to introduce all of them here, I recommend reading Stacy Fisher 's 10 Best Free Photo Editors review at lifewire.com. And if it is photo editing on handhelds that you are interested on, then read Tom J Law 's The 19 Best Photo Editing Apps for iPhone and Android in 2020 at Oberlo (beware the nasty pop-up ads). And if you already miss the possibility to edit the existing image on your albums, do remember that you can always use 'ACTIONS > Replace' to "update" your existing image here at ipernity. That is useful for example when you wish to change the image but keep the discussions below. Like I have done here. ---- This issue has been discussed also previously, for example on comments under following images of mine:

When editing blog articles, the 'Insert a media' option does not currently work. Apologies for the inconvenience. Meanwhile the workaround is to insert the image code in source code. Retrieve the HTML image code from your albums on another tab, click the 'Source' button on blog editor tool bar, and insert the image code on appropriate place. Then click the 'Source' button again to get back to WYSIWYG view. UPDATE January 10, 2020: Full blog article updated to give more detailed instructions on how to add images on source view . Text and images free to use, if you wish to translate or something...

If you wish to change the album order on the 'Upload' dialog, then you need to change the album order on the 'Organize' tool. The same thing can be done via 'Albums' and 'Tools > Change the display order of the albums' menu option. And if you have folders , then go to the particular folder and use 'Tools' menu there to organize albums inside the folder. On 'Albums' root one can also use 'Tools' menu to organize the order of folders if you have any. Check out also the possibility to use ' Featured albums '.