Fast Lane!

Google Cloud can provide this as a service (amongst other services likely): https://cloud.google.com/document-ai/docs/workbench/build-summarizer-processor AWS perhaps as well: https://aws.amazon.com/blogs/machine-learning/use-a-generative-ai-foundation-model-for-summarization-and-question-answering-using-your-own-data/

We do this at work, makes catching up on looooong Space threads easy when you pop in. Ref: https://blog.google/products/workspace/hybrid-work-ai-tools-io-22/

What about one level deeper? Say the equivalent of a US state (CA for example). Not sure the equivalent in India. Anything would be helpful. Blocking 1.4B people to ward off one spammer is extremely blunt.

Hi, the geolocation block is only at a country level (really broad block). Can we narrow that down at all? For countries like India (with lots of spam attacks) this would block a few Billion legitimate people.

Not just post content. We have MASS #'s on spam accounts with no spam just just drop url ridden info in profile fields (incl profile photos).

GREAT! 🥳

Hi Olivia, any chance we can get a small push for spam prevention in the current version? 80% of signups for us are spam... 😞

Can't wait for 4.6.3 or so. I'll def upgrade once the major bugs are caught during wider roll out.

Is there a way to know when our critical plugins/apps support 4.6... coming from someone who is still on 4.4 and was waiting for probably 4.6.2 to go live... Def congrats on the 4.6 gold btw!!

Click this. https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-not-live

I think I spotted and SEO bug. If you go to a url: https://invisioncommunity.com/forums/topic/461972-xyz the real money is the "461972". IPB treats that as gold so even if a topic is renamed it just redirects you to the latest url/topic. So if you type in https://invisioncommunity.com/forums/topic/461972-xyz2323232 it would redirect to the latest furl for the topic. Here is the issue. Take this topic. The old behavior was if I change the name/furl for this topic to: https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-NOTLIVE it would redirect correctly to: https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-live But now it redirects to: https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-live/?ct=1622349311 Which for whatever reason includes the current unixtimestamp. Odd. And it splits SEO rankings up (dilutes = bad). The canonical isn't wrong, upon source inspection (https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-live/). But why ever add the unix time stamp?

If we upgrade and don't enable the new badges system, can we convert later after the upgrade? Can we swap back if we don't like it. Etc.. serious question. I'm not sure this has been addressed.