SeNioR-

so what? better this than nothing 👍

AdSense has announced a new version of auto-ads with a lot more control options. Any experiences with this?

Tags are essential for searching our community (and many others) so it would be great if ADMIN had the option to set the default Searches to include Tags. I know we can access tag searches, but that's not an intuitive or easily accessible search for function.
Thanks!

It looks like the Instagram login handler on the Marketplace is broken. Tried contacting the dev to no avail. Does anyone know of other ways to setup Instagram login integration?

so what? better this than nothing 👍

You might be aware of this already, but it is a request that would be highly appreciated by myself and I think by the rest of the community as well.

On my forums, I have specific forums which are not accessible for guests and also not for the google search crawler, because I prefer this forums not to be searchable through google.

However, it would be great if we could set separate access (f.i. as a separate user group) for the AdSense crawler, because irrespective of whether you can google these private forums, I want the ads on these forums to be as relevant as possible. The login feature of the adsense crawler doesn't work with IPB, as far as I know.

Please IPS, could you include code that recognizes the AdSense crawler and assign it to a specific user group? Thanks!

FYI, in response to being asked about the list from the medium article, Apple PWA dev responded as follows:   EVERYONE WHO IS READING THIS, PLEASE PLEASE PLEASE PROVIDE FEEDBACK HERE: https://bugs.webkit.org/show_bug.cgi?id=182566 EXPLAINING WHY PWA PUSH NOTIFICATIONS ARE VERY IMPORTANT TO SOFTWARE LIKE INVISION WHERE A WHITE LABEL MOBILE APP FOR EACH COMMUNITY IS NOT FEASIBLE. PLEASE TRY TO AVOID "+1 I NEED THIS" AND PROVIDE AS MUCH SPECIFIC, CONCRETE DETAIL ON HOW YOU WOULD MAKE USE OF THE ABILITY TO SEND PUSH NOTIFICATIONS TO MOBILE USERS AND WHY A NATIVE APP ISNT A SOLUTION
I asked Invision if they had plans to make a formal use case proposal through this channel and as of right now they do not, so it is on us as a community to advocate loud and often for why push needs to be implemented on iOS with concrete examples of how our communities would use it (and just as importantly, not abuse it).
@Matt, I appreciate that the view is that Apple is strategically holding back push support in iOS so as not to cannibalize the app store, but when the Apple dev who is responsible for implementation is specifically asking for concrete examples from people who would benefit from push API PWA support in iOS, we should still work together to provide that feedback even if it's ultimately a dead-end. 
@Joel R you are probably one of the best in this community at taking all the noise from in here and distilling into actionable efforts, so anything you can do to help wrangle us into a coherent community driven effort to make our request heard loud and clear to Apple here would be sincerely appreciated. 
Also tagging some of the devs I see posting often who might be able to help provide the technical info submissions for their apps, etc. 
@Fosters @Adriano Faria @CodingJungle @opentype @newbie LAC @TheJackal84 @All Astronauts
Also, as a final thought, I'm not sure how much communication there is between the development teams for Invision, Xenforo, NodeBB, Discourse, Vanilla, etc. etc., but this is one of those topics where forming a lobbying group of developers where you can aggregate the number of users across all platforms and deliver some consistent messaging would be really helpful IMO. Any victories we can make with PWA in iOS ultimately serves to keep all of our communities alive and able to compete with other closed platforms, as ultimately user engagement on mobile through notifications (and in the case of iOS, the complete lack thereof) is going to make or break many of us.

On my forum the last month. Android - 49,4%, iOS - 12% 
Push on Android would be great.

 

so what? better this than nothing 👍

so what? better this than nothing 👍

Better than not at all though in the meantime

+1 for push notifications.

I have figured out that there is no meta description for the links with /page/XXX at the end
topics http://www.example.com/forums/topic/17589-whatever/page/XXX article comments http://www.example.com/articles/category/article/page/XXX blog entry http://www.example.com/blogs/entry/17589-whatever/page/XXX and so on I have lot of pages where Sign in... and menu structure is taken into description by Google instead of the content of the page. It looks messy in search results and does not attract users to click. 

Glad to hear that 4.4 has resolved the sitemap issues. 🙂

I think this becomes a negative result for Google. Google scans the whole page and index content on a specific page. In your sitemap_posts file, you have tons of links to the same pages (they have not differences by the code or view). So with that, you bring Google just problems. Moreover, for preventing duplications Google gives us a links management service, where we can 'say' to Google which params identify something important with content changing (like a 'page' attribute) or something not necessarily (like an 'unread' param).
Additional, you made just problems for Google. If you wish to highlight or markup the content on the page - you should use schema.org meta, html5 tags. All of that already done by IPS. You don't need to do anything more in general purpose.
Anyway, if your really want to scan every post like an individual content - make a special request to the topic, which will show only one post without other (but with the link to the default view). In this way, you'll increase your number of scanned 'pages'. But it mustn't be good for your SEO.

I don't think it will have any impact, mostly because we use canonical meta tags to prevent duplicate "pages" being indexed. When I clicked on this topic I ended up at URL:
https://invisioncommunity.com/forums/topic/442742-large-community-you-have-a-problems-with-sitemap/page/10/?tab=comments#comment-2784429 In the HTML page source I have
<link rel="canonical" href="https://invisioncommunity.com/forums/topic/442742-large-community-you-have-a-problems-with-sitemap/page/10/" /> So when Google visits the URL I did, the resulting URL they will index is 
https://invisioncommunity.com/forums/topic/442742-large-community-you-have-a-problems-with-sitemap/page/10/  
With your customization you are attempting to send signals to Google "look at this URL and this URL and this URL" all from the same topic with the same canonical tag, which is different from the URL in the sitemap. I think, if anything, this will cause confusion to Google's spiders along the lines of "why does their sitemap say to index url X but when we visit it they tell us the canonical URL is Y?"

@DawPi has completed the custom sitemap application that I mentioned which handles all posts. You can see an example of it here:
https://www.celiac.com/sitemap_posts.php
but it is modeled after the existing sitemap--but this one handles just forum posts. We were not able to add a minimum word count to this application, as one person suggested, because it slowed things down and put a load on the CPU. We were, however, able to add the ability to exclude certain forums, for example my site has around 25 different forums, so I was able to exclude a general chit chat and a technical support forum that are more or less off the main topic of my site.
Whether or not this will be a benefit or liability in Google search is an open question, but I'll follow up here with any noticeable changes, positive or negative.
I believe this will have positive results, simply because we are making it easier for Google to index specific content and allow them to provide more relevant search results for any given query. Currently Google's results may send people to a topic page like this one /page/10/, and the person who searched will still have to fish on it for the specific results of their query. With all posts indexed, Google should be able to send the person directly to the content that answers their query...at least that is my hope here.
Anyone interested in this app can contact @DawPi
Here is a screenshot of the admin page:

I have written a lot about this subject, incl. and i have a design to use the critical CSS to remove the Render-blocking CSS. Yes, it works, but it takes a lot of time to analyze and develop a good critical CSS.
For a few days I've been exploring another idea that came to my mind.
Code in IncludeCSS works perfectly and this code tells the browser - download all those CSS and use them to represent the site. But this code does not tell the browser when and how to use them.
The idea I'm using right now is - I created a new template that I put before closing the tag head. In my experiment, this template looks like this:
{template="preload_css" app="core" location="global" group="analysis" params=""} In this template I placed this code
{{foreach array_unique( \IPS\Output::i()->cssFiles, SORT_STRING ) as $file}} <link rel='preload' href='{expression="\IPS\Http\Url::external( $file )->setQueryString( 'v', \IPS\CACHEBUST_KEY )"}' as="style"> {{endforeach}} {{$customCss = \IPS\Theme::i()->css( 'custom.css', 'core', 'front' );}} {{foreach $customCss as $css}} <link rel='preload' href='{expression="\IPS\Http\Url::external( $css )->setQueryString( 'v', \IPS\CACHEBUST_KEY )"}' as="style"> {{endforeach}} Now, besides a browser command to download all CSS, I send the browser a command - use these CSS as a matter of priority.
And the result of over 100 my tests - no render-blocking CSS ...
There are no side effects or any other bad impact.
I've installed it on my live site and it works perfectly.
If a development team wishes, let him test it and apply it in later releases. This will speed up all sites using this really good platform.

Profiles on IPS have virtually no meta tags, at all.
This could be improved by adding a link to the users avatar and maybe a general description line like so,
$description = "Explore {$this->member->name}'s " . \number_format( $this->member->member_posts ) . " posts on " . \IPS\Settings::i()->board_name; $newMeta = [ 'title' => $this->member->name, 'description' => $description, 'og:title' => $this->member->name, 'og:description' => $description, 'twitter:description' => $description, 'og:image' => $this->member->photo, 'profile:username' => $this->member->name, 'og:url' => $this->member->url() ]; \IPS\Output::i()->metaTags = array_merge( \IPS\Output::i()->metaTags, $newMeta ); Otherwise links to profiles contain no description or anything aside the default og:image if you have one set in the settings.

We still need WhatsApp share button as long as the hook is not working anymore.

@dayh I overwrote the editor icon calls with CSS using FontAwesome icons like so:
.cke_button__bold:after { background: none !important; font-size: 1.4rem !important; font-family: "FontAwesome"; content: "\f032"; position: relative; top: 0rem; left: 0rem; } FontAwesome 4.7 cheatsheet: https://fontawesome.com/v4.7.0/cheatsheet/

Can't wait for the new version which will limit links. We see a huge increase of users that signup just to drop a link and then never come back or posting anything useful. So if you can add a limitation of links in the message I would set up a members group for members that just signed up and till they make 5-10 useful posts without links they will not be promoted to regular member group where they can posts links.

I would recommend to use our Profile completion setup. You can force a user to complete their profile when they complete their registration or you can turn off quick registration and any field that you have setup in the Profile to be shown on Registration will again.

Took me a few years to decide, after being with VB having the full licence with apps, but it didn't worked well as I cannot compare with IPB in any way. so here we go, we have decided taht we need to pay for apps 🙂