Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add homepage to Mouseflow #219

Merged
merged 1 commit into from
May 11, 2024
Merged

Conversation

lasseschou
Copy link
Contributor

No description provided.

Copy link

vercel bot commented May 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
third-party-web ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 10, 2024 8:50pm

Copy link
Owner

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks! 🎉

@patrickhulce patrickhulce merged commit 6203a63 into patrickhulce:master May 11, 2024
7 checks passed
Copy link

🎉 This PR is included in version 0.24.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@lasseschou
Copy link
Contributor Author

@patrickhulce do you still maintain the data, or you do need help?

@patrickhulce
Copy link
Owner

@lasseschou I do but at an infrequent rate. Help always appreciated!

There is a script to query latest data and instructions for contributions if you want to help out:)

@lasseschou
Copy link
Contributor Author

Great stuff. Yup, I've seen the SQL queries and instructions. So does this mean that you're doing that locally, now and then, and then upload the results? Would it be an idea to set up a monthly job to automatically query the dataset and deploy a new version? Only thing is, it's not totally free - but since Google is using the dataset in Lighthouse, I guess maybe @paulirish can help with this?

@patrickhulce
Copy link
Owner

does this mean that you're doing that locally, now and then, and then upload the results?

Exactly.

Would it be an idea to set up a monthly job to automatically query the dataset and deploy a new version? Only thing is, it's not totally free

Yeah cost is what was stopped me.

I'm not sure that Lighthouse is using anything other than the classifications at the moment (which wouldn't be helped by automated queries), but I certainly wouldn't turn down funding for it from @paulirish if it's there ;)

@lasseschou
Copy link
Contributor Author

Even the classifications that Lighthouse use need regular updates. It looks like it's still using data from 4+ years ago, and new third-party entities pop up all the time.

Commenting on a pull request like this probably isn't the best way, but @paulirish if you could pull some strings and get @patrickhulce a GCP account for third-party-web with a generous free tier for querying the HTTP Archive, I'm sure we could get an automated monthly job up and running, which would benefit Lighthouse (get more up-to-date third-party entities), but also help raise awareness of how CPU heavy the third-parties are, and thus apply a pressure to reduce the third-party load generally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants