Matt

Thanks!

It's a great team effort as always, but a special shout out to @Olivia Clarkwho keeps schedules on track, information flowing and generally makes sure we stay organised.

Thanks!

It's a great team effort as always, but a special shout out to @Olivia Clarkwho keeps schedules on track, information flowing and generally makes sure we stay organised.

Thanks!

It's a great team effort as always, but a special shout out to @Olivia Clarkwho keeps schedules on track, information flowing and generally makes sure we stay organised.

Thanks!

It's a great team effort as always, but a special shout out to @Olivia Clarkwho keeps schedules on track, information flowing and generally makes sure we stay organised.

Thanks!

It's a great team effort as always, but a special shout out to @Olivia Clarkwho keeps schedules on track, information flowing and generally makes sure we stay organised.

All I really got to say is IPB knocked this one out of the park. HOMERUN! I better add also I'm also really impressed with low bug count in betas. The dev team is organized better than ever.. It's taken some years to get everything on the track it is but I feel it was well worth it and well worth the wait. Should I be giving @Lindy some credit here?? If I do will @Matt pull the Lindy factor line on me? 🤣 This is really such a well rounded product now all the way around. Great awesome job IPB!
 

Awesome! Thanks for the positive feedback - that's exactly what we wanted to hear! 
I'd love to take credit, but it's definitely not me - it's really a cumulation of an amazing development team, new processes and the addition of @Olivia Clarkto the team last year. I'm extremely proud of everyone at IPS; we're very fortunate! 
Thanks again. 4.5 is the best yet. 🙂 

This statement is so inaccurate, Snopes just went bankrupt writing its response.

 

This won't make it past approval now. It has to be more than a simple wrapper or web view app.

This won't make it past approval now. It has to be more than a simple wrapper or web view app.

This won't make it past approval now. It has to be more than a simple wrapper or web view app.

This statement is so inaccurate, Snopes just went bankrupt writing its response.

 

This statement is so inaccurate, Snopes just went bankrupt writing its response.

 

This statement is so inaccurate, Snopes just went bankrupt writing its response.

 

I've said it many times.

Apple will never make PWA a first person citizen on its platform; this means complete with full service workers and notifications.

They do not want a mass App Store exodus. They want that 30% in-app payment slice.

https://www.theverge.com/2020/6/18/21296180/apple-hey-email-app-basecamp-rejection-response-controversy-antitrust-regulation

We can definitely do more with our PWA implementation, but we decided the sensible approach was to create native apps.

I've said it many times.

Apple will never make PWA a first person citizen on its platform; this means complete with full service workers and notifications.

They do not want a mass App Store exodus. They want that 30% in-app payment slice.

https://www.theverge.com/2020/6/18/21296180/apple-hey-email-app-basecamp-rejection-response-controversy-antitrust-regulation

We can definitely do more with our PWA implementation, but we decided the sensible approach was to create native apps.

I've said it many times.

Apple will never make PWA a first person citizen on its platform; this means complete with full service workers and notifications.

They do not want a mass App Store exodus. They want that 30% in-app payment slice.

https://www.theverge.com/2020/6/18/21296180/apple-hey-email-app-basecamp-rejection-response-controversy-antitrust-regulation

We can definitely do more with our PWA implementation, but we decided the sensible approach was to create native apps.

I've said it many times.

Apple will never make PWA a first person citizen on its platform; this means complete with full service workers and notifications.

They do not want a mass App Store exodus. They want that 30% in-app payment slice.

https://www.theverge.com/2020/6/18/21296180/apple-hey-email-app-basecamp-rejection-response-controversy-antitrust-regulation

We can definitely do more with our PWA implementation, but we decided the sensible approach was to create native apps.

I've said it many times.

Apple will never make PWA a first person citizen on its platform; this means complete with full service workers and notifications.

They do not want a mass App Store exodus. They want that 30% in-app payment slice.

https://www.theverge.com/2020/6/18/21296180/apple-hey-email-app-basecamp-rejection-response-controversy-antitrust-regulation

We can definitely do more with our PWA implementation, but we decided the sensible approach was to create native apps.

I've said it many times.

Apple will never make PWA a first person citizen on its platform; this means complete with full service workers and notifications.

They do not want a mass App Store exodus. They want that 30% in-app payment slice.

https://www.theverge.com/2020/6/18/21296180/apple-hey-email-app-basecamp-rejection-response-controversy-antitrust-regulation

We can definitely do more with our PWA implementation, but we decided the sensible approach was to create native apps.

I've said it many times.

Apple will never make PWA a first person citizen on its platform; this means complete with full service workers and notifications.

They do not want a mass App Store exodus. They want that 30% in-app payment slice.

https://www.theverge.com/2020/6/18/21296180/apple-hey-email-app-basecamp-rejection-response-controversy-antitrust-regulation

We can definitely do more with our PWA implementation, but we decided the sensible approach was to create native apps.

We have talked about hashtags a lot internally over the years.

The core issue is that we're just not sure how useful they are on a forum. They work on Twitter because it's the only way to create a 'channel' of similar discussions. There is no other way to separate out conversations. So adding the tag makes it clear you're talking about that topic.

Obviously, with a forum you have categories, forums and topics. Adding a hashtag would be largely superfluous.

We have a tagging system for content already, and I would say that 98% of Invision Communities do not use it, and of the 2%, a small handful use it in a meaningful way that aids content discovery.

Hashtags are often mistyped further diluting the usefulness. Using your example, on twitter I've seen:

#blacklivematter
#blacklivesmatters
#blm
#blackouttuesday

Twitter actually is smart enough to know these are largely the same topic, so you will often see something like:

Trending
#Blacklivesmatter
Also talking about: #blm, #blackouttuesday

That's a great system but takes a lot of AI/human collating and computing power.

So our current position is simply that adding hashtags won't really increase content discovery in any meaningful way.

Facebook has hashtags but almost no one uses them.

Most hashtags are added for irony, like:

We're not going to add hashtags into 4.5

#sorryNotSorry

This creates a bunch of records and consumes a chunk of computing power and database size for almost no purpose at all.

We have talked about hashtags a lot internally over the years.

The core issue is that we're just not sure how useful they are on a forum. They work on Twitter because it's the only way to create a 'channel' of similar discussions. There is no other way to separate out conversations. So adding the tag makes it clear you're talking about that topic.

Obviously, with a forum you have categories, forums and topics. Adding a hashtag would be largely superfluous.

We have a tagging system for content already, and I would say that 98% of Invision Communities do not use it, and of the 2%, a small handful use it in a meaningful way that aids content discovery.

Hashtags are often mistyped further diluting the usefulness. Using your example, on twitter I've seen:

#blacklivematter
#blacklivesmatters
#blm
#blackouttuesday

Twitter actually is smart enough to know these are largely the same topic, so you will often see something like:

Trending
#Blacklivesmatter
Also talking about: #blm, #blackouttuesday

That's a great system but takes a lot of AI/human collating and computing power.

So our current position is simply that adding hashtags won't really increase content discovery in any meaningful way.

Facebook has hashtags but almost no one uses them.

Most hashtags are added for irony, like:

We're not going to add hashtags into 4.5

#sorryNotSorry

This creates a bunch of records and consumes a chunk of computing power and database size for almost no purpose at all.

We have talked about hashtags a lot internally over the years.

The core issue is that we're just not sure how useful they are on a forum. They work on Twitter because it's the only way to create a 'channel' of similar discussions. There is no other way to separate out conversations. So adding the tag makes it clear you're talking about that topic.

Obviously, with a forum you have categories, forums and topics. Adding a hashtag would be largely superfluous.

We have a tagging system for content already, and I would say that 98% of Invision Communities do not use it, and of the 2%, a small handful use it in a meaningful way that aids content discovery.

Hashtags are often mistyped further diluting the usefulness. Using your example, on twitter I've seen:

#blacklivematter
#blacklivesmatters
#blm
#blackouttuesday

Twitter actually is smart enough to know these are largely the same topic, so you will often see something like:

Trending
#Blacklivesmatter
Also talking about: #blm, #blackouttuesday

That's a great system but takes a lot of AI/human collating and computing power.

So our current position is simply that adding hashtags won't really increase content discovery in any meaningful way.

Facebook has hashtags but almost no one uses them.

Most hashtags are added for irony, like:

We're not going to add hashtags into 4.5

#sorryNotSorry

This creates a bunch of records and consumes a chunk of computing power and database size for almost no purpose at all.

We have talked about hashtags a lot internally over the years.

The core issue is that we're just not sure how useful they are on a forum. They work on Twitter because it's the only way to create a 'channel' of similar discussions. There is no other way to separate out conversations. So adding the tag makes it clear you're talking about that topic.

Obviously, with a forum you have categories, forums and topics. Adding a hashtag would be largely superfluous.

We have a tagging system for content already, and I would say that 98% of Invision Communities do not use it, and of the 2%, a small handful use it in a meaningful way that aids content discovery.

Hashtags are often mistyped further diluting the usefulness. Using your example, on twitter I've seen:

#blacklivematter
#blacklivesmatters
#blm
#blackouttuesday

Twitter actually is smart enough to know these are largely the same topic, so you will often see something like:

Trending
#Blacklivesmatter
Also talking about: #blm, #blackouttuesday

That's a great system but takes a lot of AI/human collating and computing power.

So our current position is simply that adding hashtags won't really increase content discovery in any meaningful way.

Facebook has hashtags but almost no one uses them.

Most hashtags are added for irony, like:

We're not going to add hashtags into 4.5

#sorryNotSorry

This creates a bunch of records and consumes a chunk of computing power and database size for almost no purpose at all.