Skip to content

Docs: added summary 286: added config#340

Open
Alpastx wants to merge 1 commit intoOurTechCommunity:mainfrom
Alpastx:summary-286
Open

Docs: added summary 286: added config#340
Alpastx wants to merge 1 commit intoOurTechCommunity:mainfrom
Alpastx:summary-286

Conversation

@Alpastx
Copy link
Copy Markdown
Contributor

@Alpastx Alpastx commented May 3, 2026

No description provided.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 3, 2026

👷 Deploy request for otc-catchup pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit db80a40

Copy link
Copy Markdown
Member

@ankushhKapoor ankushhKapoor left a comment

Choose a reason for hiding this comment

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

The summary is not well written.
You need to prompt it so that the output is short, crisp and uses easy English language (words).
Tell it to not include any non tech conversation , don't include em dashes, don't write name of the person who shared the link, don't keep trailing slashes in links.
Also, if any summary point contains platform HackTheBox and the link of that platform is present in additional resources, it is better to use that link in the summary point itself rather than in additional resources. (just an example about this platform, use similar approach for all platforms or whenever it seems appropriate)

Comment on lines +7 to +8
* The session started with a talk on emergency phone alerts in the US, how simultaneous broadcasts feel in offices, what typical messages contain (vehicle or clothing cues, names, last-seen hints), and anecdotal views on how quickly children are found.
** Alpesh Bhagwatkar recalled reading rough recovery-rate figures in roughly the 50–60% range, without claiming rigorous statistics. Later in chat Kaustubh shared an Ontario Police–quoted report suggesting very high safe-recovery rates after Amber-style alerts—still jurisdiction-specific and not directly comparable to informal anecdotes.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
* The session started with a talk on emergency phone alerts in the US, how simultaneous broadcasts feel in offices, what typical messages contain (vehicle or clothing cues, names, last-seen hints), and anecdotal views on how quickly children are found.
** Alpesh Bhagwatkar recalled reading rough recovery-rate figures in roughly the 50–60% range, without claiming rigorous statistics. Later in chat Kaustubh shared an Ontario Police–quoted report suggesting very high safe-recovery rates after Amber-style alerts—still jurisdiction-specific and not directly comparable to informal anecdotes.
* Brief discussion took place on emergency alert systems and their real-world impact.


* The session started with a talk on emergency phone alerts in the US, how simultaneous broadcasts feel in offices, what typical messages contain (vehicle or clothing cues, names, last-seen hints), and anecdotal views on how quickly children are found.
** Alpesh Bhagwatkar recalled reading rough recovery-rate figures in roughly the 50–60% range, without claiming rigorous statistics. Later in chat Kaustubh shared an Ontario Police–quoted report suggesting very high safe-recovery rates after Amber-style alerts—still jurisdiction-specific and not directly comparable to informal anecdotes.
* Harsh Kapadia and Alpesh briefly discussed shell prompt customization (`PS1` / “prompt statement”): showing Git branch metadata versus history / exit-status placeholders such as `!` and `?`, which Alpesh said he had not dug into despite seeing them daily.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
* Harsh Kapadia and Alpesh briefly discussed shell prompt customization (`PS1` / “prompt statement”): showing Git branch metadata versus history / exit-status placeholders such as `!` and `?`, which Alpesh said he had not dug into despite seeing them daily.
* Harsh Kapadia and Alpesh briefly discussed shell prompt customization (`PS1` / “prompt statement”): showing Git branch metadata versus history / exit-status placeholders such as `!` and `?`

* The session started with a talk on emergency phone alerts in the US, how simultaneous broadcasts feel in offices, what typical messages contain (vehicle or clothing cues, names, last-seen hints), and anecdotal views on how quickly children are found.
** Alpesh Bhagwatkar recalled reading rough recovery-rate figures in roughly the 50–60% range, without claiming rigorous statistics. Later in chat Kaustubh shared an Ontario Police–quoted report suggesting very high safe-recovery rates after Amber-style alerts—still jurisdiction-specific and not directly comparable to informal anecdotes.
* Harsh Kapadia and Alpesh briefly discussed shell prompt customization (`PS1` / “prompt statement”): showing Git branch metadata versus history / exit-status placeholders such as `!` and `?`, which Alpesh said he had not dug into despite seeing them daily.
**Shivang Chheda clarified in chat that in one common convention `+n` counts staged files, `!n` modified-but-unstaged files, and `?n` untracked files—and that “PS” here means the shell prompt, not PowerShell.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
**Shivang Chheda clarified in chat that in one common convention `+n` counts staged files, `!n` modified-but-unstaged files, and `?n` untracked filesand that “PS” here means the shell prompt, not PowerShell.
** Shivang Chheda clarified that in one common convention `+n` counts staged files, `!n` modified-but-unstaged files, and `?n` untracked files and that “PS” here means the shell prompt, not PowerShell.

**Shivang Chheda clarified in chat that in one common convention `+n` counts staged files, `!n` modified-but-unstaged files, and `?n` untracked files—and that “PS” here means the shell prompt, not PowerShell.
** Bhavesh Kukreja pointed at link:https://github.com/HarshKapadia2/dotfiles/tree/main/customize-ps1[Harsh’s `customize-ps1` notes^] for reference.
* Alpesh showcased internal tooling at Cyber Unbound (cyber-security-focused recruitment), built after earlier resistance to automation inside the agency.
* Alpesh’s second demo was a static typing-practice site in the Monkeytype mould but seeded with offensive-security commands and one-line explanations
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
* Alpesh’s second demo was a static typing-practice site in the Monkeytype mould but seeded with offensive-security commands and one-line explanations
* Alpesh showed a static typing-practice site in the Monkeytype mould but seeded with offensive-security commands and one-line explanations

* Alpesh’s second demo was a static typing-practice site in the Monkeytype mould but seeded with offensive-security commands and one-line explanations
* GAMILTRON asked for hackathon-laptop advice on a roughly ₹20–30k budget saved from pocket money, primarily general web/systems development rather than heavy local AI.
** Suggestions spanned stretching toward a used Apple silicon MacBook if finances allow, buying vetted refurbished business-class Windows machines, verifying CPU generation (Windows 11 eligibility versus Linux-first setups), favouring SSDs over HDDs and planning at least ~500 GB for tooling footprints like `node_modules`, and understanding RAM/core trade-offs versus his powerful gift-built desktop (RTX 4070 class, ample RAM) that cannot travel.
** Harsh cautioned against exposing a home PC over the internet for remote hackathon use—carrier-grade NAT (CGNAT) realities in India, tunneling products popular in self-hosted circles, and his own past US experience with dynamic DNS, SSH exposure, and frequent ISP-blocked intrusion attempts even with mitigations—while acknowledging theoretical workarounds Shivang Chheda raised.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
** Harsh cautioned against exposing a home PC over the internet for remote hackathon use—carrier-grade NAT (CGNAT) realities in India, tunneling products popular in self-hosted circles, and his own past US experience with dynamic DNS, SSH exposure, and frequent ISP-blocked intrusion attempts even with mitigations—while acknowledging theoretical workarounds Shivang Chheda raised.
** Harsh advised against exposing a personal computer to the internet for hackathons. He explained that due to CGNAT in India it’s not straightforward, and even if you make it work using tunneling or port forwarding, your system can attract hacking attempts. Based on his experience, even with protections, such setups face frequent attacks, so it’s risky unless properly secured.

* link:https://github.com/HarshKapadia2/dotfiles/tree/main/customize-ps1[Harsh Kapadia — customize `PS1` (dotfiles)^]
* link:https://tornews.com/privacy/security/what-is-google-dorking/[What is Google dorking? (Tor News)^]
* link:https://www.hackthebox.com[Hack The Box^]
* link:https://news.ycombinator.com/item?id=47788857[Hacker News — IPv8 draft thread — GAMILTRON / Bhavesh^]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
* link:https://news.ycombinator.com/item?id=47788857[Hacker News IPv8 draft thread — GAMILTRON / Bhavesh^]
* link:https://news.ycombinator.com/item?id=47788857[Hacker News - IPv8^]

* link:https://tornews.com/privacy/security/what-is-google-dorking/[What is Google dorking? (Tor News)^]
* link:https://www.hackthebox.com[Hack The Box^]
* link:https://news.ycombinator.com/item?id=47788857[Hacker News — IPv8 draft thread — GAMILTRON / Bhavesh^]
* link:https://www.datacamp.com/blog/faiss-facebook-ai-similarity-search[Datacamp — Faiss overview — Rudraksh^]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
* link:https://www.datacamp.com/blog/faiss-facebook-ai-similarity-search[Datacamp Faiss overview — Rudraksh^]
* link:https://www.datacamp.com/blog/faiss-facebook-ai-similarity-search[Datacamp - Faiss overview^]

* link:https://www.hackthebox.com[Hack The Box^]
* link:https://news.ycombinator.com/item?id=47788857[Hacker News — IPv8 draft thread — GAMILTRON / Bhavesh^]
* link:https://www.datacamp.com/blog/faiss-facebook-ai-similarity-search[Datacamp — Faiss overview — Rudraksh^]
* link:https://arxiv.org/abs/2512.24601[arXiv:2512.24601^]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
* link:https://arxiv.org/abs/2512.24601[arXiv:2512.24601^]
* link:https://arxiv.org/abs/2512.24601[arXiv: Recursive Language Models^]

* link:https://news.ycombinator.com/item?id=47788857[Hacker News — IPv8 draft thread — GAMILTRON / Bhavesh^]
* link:https://www.datacamp.com/blog/faiss-facebook-ai-similarity-search[Datacamp — Faiss overview — Rudraksh^]
* link:https://arxiv.org/abs/2512.24601[arXiv:2512.24601^]
* link:https://www.linkedin.com/feed/update/urn:li:activity:7456373930421870592/[Bhavesh — LinkedIn project update (AutoTriage)^]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
* link:https://www.linkedin.com/feed/update/urn:li:activity:7456373930421870592/[Bhavesh LinkedIn project update (AutoTriage)^]
* link:https://www.linkedin.com/feed/update/urn:li:activity:7456373930421870592[Bhavesh - LinkedIn project update (AutoTriage)^]

Comment on lines +31 to +32
* link:https://github.com/BhaveshKukreja29/AutoTriage/blob/main/code/router.py#L30[AutoTriage `router.py` (regex excerpt)^]
* link:https://github.com/BhaveshKukreja29/AutoTriage/blob/main/code/router.py#L58[AutoTriage `router.py` (prompt routing)^]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
* link:https://github.com/BhaveshKukreja29/AutoTriage/blob/main/code/router.py#L30[AutoTriage `router.py` (regex excerpt)^]
* link:https://github.com/BhaveshKukreja29/AutoTriage/blob/main/code/router.py#L58[AutoTriage `router.py` (prompt routing)^]
* link:https://github.com/BhaveshKukreja29/AutoTriage[AutoTriage - GitHub^]

@ankushhKapoor
Copy link
Copy Markdown
Member

Please remove all remaining em dashes. @Alpastx

@ankushhKapoor ankushhKapoor mentioned this pull request May 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants