opentype

1. Yes, members can unfollow at anytime.
2. No. There is another plugin for new members:
They were made in different time, that's why they're two. I want to merge them and sell only one. Purchasers of any of them will be added to the new plugin; no ETA though.

I recommended it too a while ago. Makes perfect sense to support these Twitter meta tags along with the ones Facebook looks for. Tweets with images are so much more likely to get clicks than just plain links. 
If you can’t wait: it’s surprisingly simple to add it to certain templates. For example, I added this to my video database in Pages:
{{\IPS\Output::i()->metaTags['twitter:card'] = 'summary_large_image';}} {{\IPS\Output::i()->metaTags['twitter:site'] = '@TypographyGuru';}} {{\IPS\Output::i()->metaTags['twitter:title'] = $record->_title;}} {{\IPS\Output::i()->metaTags['twitter:description'] = 'Watch this video in the collection of the best typography videos on Typography.Guru';}} {{\IPS\Output::i()->metaTags['twitter:image'] = (string) \IPS\File::get( 'cms_Records', $record->record_image )->url;}}  

I recommended it too a while ago. Makes perfect sense to support these Twitter meta tags along with the ones Facebook looks for. Tweets with images are so much more likely to get clicks than just plain links. 
If you can’t wait: it’s surprisingly simple to add it to certain templates. For example, I added this to my video database in Pages:
{{\IPS\Output::i()->metaTags['twitter:card'] = 'summary_large_image';}} {{\IPS\Output::i()->metaTags['twitter:site'] = '@TypographyGuru';}} {{\IPS\Output::i()->metaTags['twitter:title'] = $record->_title;}} {{\IPS\Output::i()->metaTags['twitter:description'] = 'Watch this video in the collection of the best typography videos on Typography.Guru';}} {{\IPS\Output::i()->metaTags['twitter:image'] = (string) \IPS\File::get( 'cms_Records', $record->record_image )->url;}}  

I recommended it too a while ago. Makes perfect sense to support these Twitter meta tags along with the ones Facebook looks for. Tweets with images are so much more likely to get clicks than just plain links. 
If you can’t wait: it’s surprisingly simple to add it to certain templates. For example, I added this to my video database in Pages:
{{\IPS\Output::i()->metaTags['twitter:card'] = 'summary_large_image';}} {{\IPS\Output::i()->metaTags['twitter:site'] = '@TypographyGuru';}} {{\IPS\Output::i()->metaTags['twitter:title'] = $record->_title;}} {{\IPS\Output::i()->metaTags['twitter:description'] = 'Watch this video in the collection of the best typography videos on Typography.Guru';}} {{\IPS\Output::i()->metaTags['twitter:image'] = (string) \IPS\File::get( 'cms_Records', $record->record_image )->url;}}  

Insert one item in to your pages database. Look at the cms_databases table in your site database and identify the database_id for your pages database. Look at the cms_custom_database_X (where X = that database id) table and review the content, and how it is populated. Take that structure and mirror it in your excel spreadsheet (titles etc) Use the Import -> CSV functionality in phpmyadmin to import the csv file in to the table. It's how I've populated over 100 years worth of football league tables in to a pages database - approximately 20,000 records.

I just tried this on a test installation, but changing the conf_global did not seem to do anything at all. Is that really all we would have to do to start this process?

No. The scenarios are:
MySQL <= 5.1You cannot use UTF8MB4 at all MySQL >= 5.5UTF8. Certain characters (like certain Emoji) won’t be supported and could cause problems in earlier releases. Therefore the most recent version now warns you about this when you try to include such characters. UTF8MB4: You are free to use any characters. 

I agree to the feature request. 

However, I would suggest that you stick to calm factual descriptions for such requests. IPS will judge the feature request by itself. It doesn’t need red, exclamation marks or exaggerations (i.e. “it’s useless”). 
If it helps you as a work-around: On my 3.4 site I monitor Wiki article changes by having set up blocks which are ordered by last change. It’s much easier to spot changes this way. 

I agree to the feature request. 

However, I would suggest that you stick to calm factual descriptions for such requests. IPS will judge the feature request by itself. It doesn’t need red, exclamation marks or exaggerations (i.e. “it’s useless”). 
If it helps you as a work-around: On my 3.4 site I monitor Wiki article changes by having set up blocks which are ordered by last change. It’s much easier to spot changes this way. 

I agree to the feature request. 

However, I would suggest that you stick to calm factual descriptions for such requests. IPS will judge the feature request by itself. It doesn’t need red, exclamation marks or exaggerations (i.e. “it’s useless”). 
If it helps you as a work-around: On my 3.4 site I monitor Wiki article changes by having set up blocks which are ordered by last change. It’s much easier to spot changes this way. 

Stop spreading these false information. The UTF8 type is a user-choice during installation or upgrade. There is no “automatic” conversion, because that wouldn’t even work, e.g. when your database runs on MySQL 5.1. In addition, your are not “stuck” with UTF8. Its YOUR MySQL database on YOUR server. You can do whatever you want with it. If you are not able to, maybe you should better move to IPS’ clould solution. But don’t expect IPS to become your server admin. 

Stop spreading these false information. The UTF8 type is a user-choice during installation or upgrade. There is no “automatic” conversion, because that wouldn’t even work, e.g. when your database runs on MySQL 5.1. In addition, your are not “stuck” with UTF8. Its YOUR MySQL database on YOUR server. You can do whatever you want with it. If you are not able to, maybe you should better move to IPS’ clould solution. But don’t expect IPS to become your server admin. 

It won't work. You'll still come across the index too long issue as I keep saying...  Well you're not going to be happy until you get a step by step so try this. At your own large risk!
Backup your board. Take the board offline Backup your board!!!! Add/Change conf_global.php to include 'sql_utf8mb4' = true In the ACP goto Support -> Something is not working It will spit out hundreds of MySql commands, copy them to a text file (there's no chance of them working from Fix Automatically unless your board is small) Run the commands in phpmyadmin one by one or in small batches. Make a note of the tables that give errors about indexes being too long For the tables with index-too-long error:
Goto the table / Structure tab. Scroll down and click on "+indexes" Delete all but the primary indexes Rerun the Support tool in the ACP, it should give you the correct command to recreate the index with the correct length

No. The scenarios are:
MySQL <= 5.1You cannot use UTF8MB4 at all MySQL >= 5.5UTF8. Certain characters (like certain Emoji) won’t be supported and could cause problems in earlier releases. Therefore the most recent version now warns you about this when you try to include such characters. UTF8MB4: You are free to use any characters. 

No. The scenarios are:
MySQL <= 5.1You cannot use UTF8MB4 at all MySQL >= 5.5UTF8. Certain characters (like certain Emoji) won’t be supported and could cause problems in earlier releases. Therefore the most recent version now warns you about this when you try to include such characters. UTF8MB4: You are free to use any characters. 

Hiding/deleting posts is always a tricky issue. It's necessary, but it can create new discussions, because the users who's posts got hidden can get pretty mad.

On Facebook Pages this is solved quite nicely. If you hide a post, no one will see it anymore BUT the author. So provoking posts will not cause any trouble, but the author won't get mad, because he/she will still see the post.

This might be a nice option to have on IP.Board as well.

Hiding/deleting posts is always a tricky issue. It's necessary, but it can create new discussions, because the users who's posts got hidden can get pretty mad.

On Facebook Pages this is solved quite nicely. If you hide a post, no one will see it anymore BUT the author. So provoking posts will not cause any trouble, but the author won't get mad, because he/she will still see the post.

This might be a nice option to have on IP.Board as well.