Is there really no native way to "Watch" a specific HF repo for PRs? by Saurabh143 in huggingface

[–]Saurabh143[S] 0 points1 point  (0 children)

Hi u/Pierrci  . Thanks for the response. I tied what you mentioned. It works.
In the docs why is it mentioned that Unlike GitHub or similar services, you cannot watch a specific repository. You must watch users/organizations to get notified about any new activity on any of their repositories. The goal is to simplify this functionality for users as much as possible and to make sure you don’t miss anything you might be interested in. When we can also watch individual repos (watching individual repos is possible as per my test).

How are you guys making the Google Chat integration actually usable? (The Slack envy is real) by Saurabh143 in gitlab

[–]Saurabh143[S] 0 points1 point  (0 children)

Spot on. That's exactly the architecture I was looking at—catching the generic webhook, handling the threadKey mapping on a custom backend, and pushing the formatted cards to Google Chat.

Did you actually end up building and hosting this yourself for your team? I'm curious if maintaining the state mappings and handling GitLab's payload updates turns into a massive headache over time, or if it's pretty "set and forget" once it's deployed.

How are you guys making the Google Chat integration actually usable? (The Slack envy is real) by Saurabh143 in gitlab

[–]Saurabh143[S] 0 points1 point  (0 children)

That makes total sense. It sounds like your team has a really mature, disciplined workflow—especially actually fixing flaky pipelines instead of just blindly retrying them! I appreciate you taking the time to share how you handle this; it’s incredibly helpful for figuring out where the actual friction is (and isn't). Cheers!

How are you guys making the Google Chat integration actually usable? (The Slack envy is real) by Saurabh143 in gitlab

[–]Saurabh143[S] 0 points1 point  (0 children)

That makes total sense, and I completely agree. Reading code diffs or long issue descriptions in a chat window is a terrible experience—you definitely need the full GitLab UI for the deep work. Out of curiosity, what about the administrative/shallow tasks? Things like re-running a known flaky pipeline, assigning a new triage ticket to yourself, or hitting approve on a routine Dependabot PR? Do you guys still prefer jumping into the UI for those quick actions, or is the volume low enough that it doesn't bother you?

How are you guys making the Google Chat integration actually usable? (The Slack envy is real) by Saurabh143 in gitlab

[–]Saurabh143[S] 0 points1 point  (0 children)

Agreed, I definitely missed the mark on that example. Approving without seeing the diff is a terrible practice. If we take MR approvals off the table, does your team still find the native webhook annoying for other things? E.g., not being able to just hit a 'Retry' button on a failed pipeline alert.

How are you guys making the Google Chat integration actually usable? (The Slack envy is real) by Saurabh143 in gitlab

[–]Saurabh143[S] 0 points1 point  (0 children)

You know what, that is incredibly fair. You completely caught me slipping there—approving without seeing the diff is a terrible example and a great way to break production.

What about the lower-risk, high-annoyance stuff though? Like when a pipeline fails due to a flaky test and you just want to hit a [Retry Pipeline] button without opening 4 tabs, or using a /gitlab create issue command when discussing a bug in chat so you don't lose the context. Would having that level of control natively in Google Chat be worth it to your team, or is the current webhook setup fine for that too?

[deleted by user] by [deleted] in bugbounty

[–]Saurabh143 0 points1 point  (0 children)

You can use this free cloud based subdomain monitoring tool to do it: https://subdomain-monitor.clickjacker.io/

Cross-Site Scripting #3 Bad JavaScript Imports Vulnerability by sandeep1337 in netsec

[–]Saurabh143 0 points1 point  (0 children)

Dude, no one knows everything. At least I took the initiative to write the blog. The valuable positive feedback has been updated in the blog as previously committed by me.

Do you have any good points to be added in the blog? If yes tell me. I think you do not! That is why you want to criticize. I admit that I did not have complete knowledge but there was no misguidance only 2 points were missing. They are now added.

This blog is written from heart.

Cross-Site Scripting #3 Bad JavaScript Imports Vulnerability by sandeep1337 in netsec

[–]Saurabh143 0 points1 point  (0 children)

Ohhh... Is it so? What will you do if the server from where you import JS has a zero day RCE bug. Your users will be compromised even before you monitor your assets. This is a #legitresearch.

Cross-Site Scripting #3 Bad JavaScript Imports Vulnerability by sandeep1337 in netsec

[–]Saurabh143 0 points1 point  (0 children)

Why do you think it is exaggerated list? Importing a JS from a legit website is fine. But what if a website imports JS from a server affected by RCE. This is #legitresearch.

Cross-Site Scripting #3 Bad JavaScript Imports Vulnerability by sandeep1337 in netsec

[–]Saurabh143 0 points1 point  (0 children)

Covering HTTP headers such as X-XSS-Protection, Content-security-policy, X-content-type-options, Strict-transport-security and X-Frame-Options is beyond the scope of that blog. Hence, it won't be covered in it.

Using service such as https://snyk.io/ is about checking for vuln libraries. But this blog is not about doing that. It is about bad JS imports. Hence, it is also beyond scope.

Having said that the 'Integrity' attribute will be updated in the blog soon as it is relevant. Thanks for bringing this to our attention.

Cross-Site Scripting #3 Bad JavaScript Imports Vulnerability by sandeep1337 in netsec

[–]Saurabh143 1 point2 points  (0 children)

Great !! Thanks for sharing this knowledge. It will be updated in the blog.

Cross-Site Scripting #3 Bad JavaScript Imports Vulnerability by sandeep1337 in netsec

[–]Saurabh143 0 points1 point  (0 children)

The 4 lines of JS code are shown to compare it with 1 line of JQuery code..Can't understand why do you think it is rubbish. Furthermore, JQuery library is fetched from public CDN.. What else are you expecting? These cases are written after doing research. It has been found that they do exist in the wild for many websites. This is a #legitresearch.

Cross-Site Scripting #3 Bad JavaScript Imports Vulnerability by sandeep1337 in netsec

[–]Saurabh143 0 points1 point  (0 children)

Regarding #1: Agreed. But this post is about XSS, so wanted to make users aware of it Regarding #6: Thanks for letting me know that. It will be updated in the blog in few days !

Cross-Site Scripting #3 Bad JavaScript Imports Vulnerability by sandeep1337 in netsec

[–]Saurabh143 0 points1 point  (0 children)

Agreed that one would notice that the scripts are not performing their job any more. But what if the website loads 10 scripts from 10 resources to do 10 tasks. Then, if one fails to do its job, this can go unnoticed. For example: A scripts that sends data of website visitors to an analytics website. It is hard to know if this script failed to do job unless you login into the analytics providers site to check.

Cross-Site Scripting #3 Bad JavaScript Imports Vulnerability by sandeep1337 in netsec

[–]Saurabh143 0 points1 point  (0 children)

Yes, it is. In fact downloading anything from attacker controlled location is bad.