Rikki

On 11/29/2023 at 4:18 PM, Matt said:

We are happy with using signals and a mathematical model for this feature.

Just to be clear, I think this part is a good idea - my suggestion was to go a step further and summarize the contents of those posts pulled out by your own model using AI, rather than just outputting the highlighted posts as-is one after the other.

I agree that just feeding an entire topic consisting of 50% junk into an AI summary probably wouldn't give great results. But if you use your signals to pull out the noteworthy posts and then summarize those, I think the result would be likely be pretty good. AI is really good at summarizing text, after all.

I clicked into this very excited, thinking you'd be showing off an AI-generated 'executive summary' of topics. Genuinely curious: why not feed those posts with high impact signals into an LLM to summarize? Not long ago your approach would have been great, but now I think will be in danger of feeling pretty clunky, manual and old fashioned. This seemed like it'd be the perfect opportunity to use a modern tool to solve the problem.

Shout out to the video editor you've hired ( 😉 ) - the preview videos you're putting out for v5 have been really slick. Way better than those Canva-esque templated ones!

This looks really, really good. I'm so glad to see new CSS underpinning everything - about time! Automatically creating color palettes from main colors is lovely too. While we worked towards some of these changes with v4 it was always difficult without breaking the entire ecosystem. I'm happy you've managed to get a clean break.

22 minutes ago, Matt said:

We have an internal wiki that is quite basic, but we'll eventually get an improved version out to the public (this is a little out of date but you get the idea).

I see @Ehren came around to Tailwind 😉 

I think personally I would dispute the idea of 'dead space' as a concept. You don't have to fill every pixel of a page with content, and doing so could actually have a negative effect by taking focus away from the actual content people are trying to find.

Facebook doesn't do it, Reddit doesn't do it, Instagram doesn't do it, so that should be a good indicator I think.

Looks great, good job on tackling some of the oldest bug bears 🔥

4 minutes ago, Charles said:

Go to https://communityhive.com not www. The next update will force redirects from www. to just the root domain.

Ah - the logo at the top links to www.

Could someone help @Charles figure out the CORS error I'm seeing?

Access to fetch at 'https://communityhive.com/webapi/feed' from origin 'https://www.communityhive.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Do my eyes deceive me or did you build a React app?

This is something you need to fix on the API side. By default browsers will not let you make ajax requests to other sites. On the API side, you need to adjust the headers it sends to include Access-Control-Allow-Origin headers that allow your community URL.

35 minutes ago, Matt said:

We don't want to be stuck in the past too.

That reminds me of post #25630909 on Facebook 😂 Go check it out!

1 hour ago, Adlago said:

I found that your original JS processes data-src. I.e. no custom JS required.

Well, by custom JS I meant the JS inside IPS4. It doesn't make sense to rely on JS at all for lazy loading simple images these days, so I'd go with loading="lazy".

21 hours ago, Adlago said:

. Loading = lazy makes loading icons delay, but does not onload them after loading the page, data-src should be added

Yes it does - loading="lazy" is a browser-native lazy loading approach, so you just include the src as normal. The data-src version is if you're using the custom JS lazy loading approach (and there's no benefit of doing that for reaction images).

I think supporting one level of sub-comments (a la stack overflow, or even status updates in IPS profiles) in forum topics and then putting answers to questions as sub-comments would be a great improvement and make it a bit easier to follow the flow of live topics. I've found this one a bit more difficult to follow post-liveness.

Looking forward to seeing how Live Topics has turned out 🎉

4 hours ago, PatrickRQ said:

@Rikki, Nobody asked you directly and this is most important part I believe. Assuming there was no internal fight about what should be leading color of main IPS theme; what are you going to do now? new project? new company? new wife.. pff I meant life? 😅

I took a position at Help Scout as a JS engineer 🙂 

It's a shame the upload experience hasn't been updated, because that was the weakest part IMO.

A formal design system is something I experimented with but unfortunately never got the opportunity to get to production.

17 hours ago, JamiUB said:

And obviously Charles, [...] is a dang superstar!

Oh no, he's going to add that to the list now.

That's an amazing opportunity - best of luck @Jordan Miller. You brought a zeal to IPS that was sorely needed and hopefully it'll continue after you're gone.

Sometimes, turning the relationship on its head and actually employing the troll can have a beneficial outcome.

34 minutes ago, Adlago said:

No, I can't do what I used to do again, you'll ask why?
- First, I don't change rules in main css
- But for more than 6 months I have been working on a project where
custom css is the only css that is loaded in the head, main css is loaded before closing the body tag.
- in the custom css content, all the framework and responsive file names are found, and some others. But with numbering, for example 1fr_global.css or 2res_ responsive.css, etc.
- In these new files, I move used rules when analyzing site pages, i.e. in the main css all the rules are contained (as they have been moved they are stopped from execution only) - or here in the main css all the rules are loaded that are unused effectively when loading the site pages.
This new layout greatly speeds up site loading.
The custom.css file also exists in custom directory and there are my customizations - and as you know, the rules there are the latest and are executed by the browser as they are there.
Since IPS introducing restrictions for visibility on css main, I abandoned a project where mobile view loads on PSI test data between 88 and 94 points depending on server busyness.
And believe me - during the time I was working on this project - several updates were completed - without any site issues...

Firstly, I should note that what you're doing is not really intended to be possible. You should be aware that if/when the frontend stack of the product is modernized, it's likely none of this will be possible because that just isn't compatible with how modern web apps are built. I know you've enjoyed this flexibility to really make low level changes but it's unlikely to be possible forever.

That said... Could you not:

• Still create your new custom css files names 1fr_global.css etc.
• Grab the classes using the technique I mentioned in this topic (use web inspector to get the compiled css file contents)
• Put all that in your custom css files however you wish
• Modify your includeCSS template to exclude any CSS files that are not 'custom' (so that the core CSS are no longer included in the page at all)

17 hours ago, Adlago said:

@Rikki Reading this thread, which I created because "you cut off my quick glance" - I am left with the clear impression that you are making a huge mistake.
Most of your clients are not interested in this at all.
But the few "crazy like me" seekers and experimenters you want to banish. Why?

It's best to ban the themes too - let's all use only one - it will be heaven for your support...

Hey Adlago,

I don't work at IPS (despite that cute cartoon avatar I have), so I'm able to tell you that you're doing it wrong. You should never have been editing the default CSS files, and it's unfortunate that the product allowed it all this time.

I assure you, you can do everything you did before. It'll be even better than before, actually, because it won't break on every upgrade.