deploy: 30e91fe

Author: ajithsureshtii

preview/pr-37/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2021 Ajith Suresh
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

preview/pr-37/README.md

@@ -0,0 +1,123 @@
+# 🚀 MPC Deadlines Hub
+
+Welcome to the **MPC Deadlines Hub**, your one-stop destination for keeping track of the latest deadlines for top Multi-Party Computation (MPC) conferences, journals, and workshops! 📅✨
+
+## 🤔 What is MPC?
+
+Secure Multi-party Computation (MPC) allows a set of mutually distrusting parties to perform a joint computation over their private inputs while preserving the privacy of their individual inputs. Curious to learn more? Check out this **[MPC overview](https://eprint.iacr.org/2020/300)**! 🔍🔐
+
+## 🚀 Adding/updating a conference
+
+Want to contribute? Awesome! Here’s how:
+
+* Read the data format description below. **Note that the timezone format sign is inverted** (e.g., UTC+7 is written as `Etc/GMT-7`). It's [not a bug][0]. Yeah, we know—it’s weird. If you have a better JavaScript timezone library in mind, hit us up! 😅
+* Update `_data/conferences.yml`. You can do this directly on GitHub or locally after forking the repo.
+* Send a pull request. 🎉
+
+💡 **Too lazy to create a pull request?** No worries! Drop a message on our **[Telegram Group](https://t.me/+sm414tMmhGhhNTA0)** 📢, and we’ll update the entries for you! 😎🚀
+
+### ✅ Is my entry in scope?
+
+This page is meant to host academic conferences, journals, workshops, and related event deadlines.
+
+Ask yourself these questions before adding an entry:
+
+- 📝 Is there a "Call For Papers"? A submission link? Formatting guidelines (page limits, style guides, etc.)?
+- 🔐 Does it mention 'secure multi-party computation', 'MPC', or 'privacy-preserving computing' in its topics?
+- 🧐 Is there a peer-review process? Are there named general/program chairs or a program committee?
+
+If you answered **YES** to all of the above, congratulations! Your conference/workshop is a great fit! 🎯
+
+### 🏆 Conference entry record
+
+Example record:
+
+```
+- name: ACM CCS
+  description: ACM Conference on Computer and Communications Security
+  year: 2025
+  link: https://www.sigsac.org/ccs/CCS2025/
+  abdeadline: Jan 02, Apr 07
+  deadline:
+    - "2025-01-09 23:59"
+    - "2025-04-14 23:59"
+  rebut: March 06-19, June 09-22
+  date: October 13-17
+  place: Taipei, Taiwan
+  comment: 2 deadlines. Notifications - March 27, June 30.
+  tags: [PRACT, APPLIED, CNF, COREAS] 
+```
+
+📌 **Notes:**
+
+- For an event with a **single deadline**, make sure to put the deadline in square brackets, like this:
+  ```
+  deadline: ["2025-04-01 23:59"]
+  ```
+- Not all fields are mandatory! Just add the relevant ones. 😊
+
+- The events are listed in alphabetical order grouped by the categories. Please make sure to have consistency while updating the entries.
+
+
+### 🔍 Field descriptions
+
+| Field name    | Description                                                 |
+|--------------|-------------------------------------------------------------|
+| `name`*      | Short conference name (no year)                              |
+| `description` | Long name or a brief description                           |
+| `year`*      | Year the conference is happening                            |
+| `link`*      | URL to the conference homepage                              |
+| `abdeadline`  | Registration and/or abstract deadline.                     |
+| `deadline`*  | Submission deadline(s)                                      |
+| `rebut`      | Rebuttal window                                            |
+| `timezone`    | Timezone in [tz][1] format (Default: UTC-12, [AoE][2])     |
+| `date`        | When the conference is happening                           |
+| `place`       | Conference location                                        |
+| `tags`        | One or more tags as detailed below.                        |
+
+📌 **Please try to maintain consistency in the order of the fields when updating an entry.**
+
+#### 📌 Special Case of Workshops
+
+Workshops can be a bit special! Here’s what to keep in mind when adding them:
+
+- If the workshop is **affiliated with a conference**, make sure to add the `conference` tag, specifying the name of the main conference. For example:
+   ```
+   conference: CCS.
+   ```
+  This helps keep things clear and organized! 🔍
+
+
+### 🏷️ Tags - Shortlisting Made Easy! 🚀
+
+We use three sets of tags that act as filters to help you quickly find relevant entries. 
+
+- **First filter**: Research Domain (e.g., THEORY, PRACT, APPLIED, etc.)
+- **Second filter**: Publication Type (e.g., CNF, JRN, WK, PS, etc.)
+- **Third filter**: [CORE](https://portal.core.edu.au/conf-ranks/) Ranking (e.g., COREAS, COREA, COREB, etc.)
+
+For the full list of tags, check out [`/_data/filters.yml`](https://github.com/mpc-deadlines/mpc-deadlines.github.io/blob/main/_data/filters.yml). 🏷️
+
+#### 🔥 Special Case: `EXP` Tag
+
+For an event that has been **announced** but the Call for Papers is **not yet available**, you can still add an entry! Just make sure to:
+- Include the `EXP` tag.
+- Fill in details based on the **previous year’s** event.
+- This will internally set some of the fields to default placeholder values (e.g., `comment: "CFP yet to be announced"`).
+
+#### 🔥 Special Case: `EXPCFP` Tag
+
+Sometimes, an event is already **confirmed** and has public details like **dates, location, and venue**, but the **CFP hasn't been published yet**. In this case, use the `EXPCFP` tag.
+
+- This is a more specific version of the `EXP` tag.
+- Use `EXPCFP` when the event is definitely happening, but the CFP is **not yet available**.
+- As with `EXP`, base your entry on the most recent available details.
+
+This helps signal to others that the event is expected, even though submission details are still pending. 🔍
+
+🔥 **Let's make MPC deadlines easy to track—together!** 🚀
+
+
+## 🙏 Acknowledgements
+
+Thanks to the amazing **[sec-deadlines](https://sec-deadlines.github.io)** page, which inspired the initial version of this hub. 🙌

preview/pr-37/bot/Dockerfile

@@ -0,0 +1,10 @@
+FROM python:3.11-slim
+
+WORKDIR /app
+
+COPY requirements.txt .
+RUN pip install --no-cache-dir -r requirements.txt
+
+COPY . .
+
+CMD ["python", "bot.py"]

preview/pr-37/bot/README.md

@@ -0,0 +1,105 @@
+# MPC Deadlines Telegram Bot
+
+Watches the [@mpc_deadlines](https://t.me/mpc_deadlines) channel. When anyone posts a conference URL it automatically:
+
+1. Scrapes the page
+2. Looks up any prior-year entry in `conferences.yml` (to inherit stable tags)
+3. Asks Groq (Llama 3.3 70B) to extract structured data and assign tags
+4. Scope-checks the event (CFP + MPC topics + peer review)
+5. Inserts or upgrades the entry (EXP → EXPCFP → FULL) in alphabetical order
+6. Opens a GitHub PR for human review
+7. Replies in the channel with the PR link
+
+---
+
+## Setup
+
+### 1. Create the Telegram bot
+
+1. Message [@BotFather](https://t.me/BotFather) → `/newbot`
+2. Copy the token into `.env` as `TELEGRAM_BOT_TOKEN`
+3. Add the bot to the channel as an **admin** with "Post Messages" permission
+
+Get the channel's numeric ID by forwarding any channel message to [@userinfobot](https://t.me/userinfobot), then add it to `ALLOWED_CHATS`.
+
+### 2. Get a Groq API key
+
+1. Sign up free at [console.groq.com](https://console.groq.com)
+2. Go to **API Keys** → **Create API Key**
+3. Copy the key into `.env` as `GROQ_API_KEY`
+
+No credit card required — Groq has a free tier.
+
+### 3. Create a GitHub fine-grained PAT
+
+Go to **GitHub → Settings → Developer settings → Fine-grained tokens**.  
+Grant on `mpc-deadlines/mpc-deadlines.github.io`:
+- **Contents**: Read & Write
+- **Pull requests**: Read & Write
+
+### 3. Configure environment
+
+```bash
+cp .env.example .env
+# Fill in all four secrets
+```
+
+### 4. Run
+
+**Docker (recommended):**
+```bash
+docker compose up -d
+```
+
+**Local:**
+```bash
+pip install -r requirements.txt
+python bot.py
+```
+
+---
+
+## How tags are assigned
+
+| Tag set | Source |
+|---|---|
+| Domain (THEORY / PRACT / APPLIED / …) | Copied from prior-year entry; otherwise inferred from CFP topics |
+| Type (CNF / JRN / WK / …) | Copied from prior-year entry; otherwise inferred from event format |
+| CORE rank (COREAS / COREA / …) | **Always copied from prior-year entry** — CORE rankings don't change. If no prior entry, Claude infers from its training knowledge |
+| Status (EXP / EXPCFP) | Determined from what the page contains: full CFP → no tag; dates/venue but no deadline → EXPCFP; announcement only → EXP |
+
+## EXP / EXPCFP logic
+
+```
+Page has submission deadline?  ──Yes──▶  FULL  (no status tag)
+        │
+        No
+        │
+Page has confirmed dates/venue? ──Yes──▶  EXPCFP
+        │
+        No
+        │
+        ▼
+       EXP
+```
+
+For EXP and EXPCFP entries the bot fills in as much as possible from the page (or prior year), sets `deadline: [TBD]`, and adds an appropriate `comment`.
+
+---
+
+## File structure
+
+```
+bot/
+├── bot.py            # Telegram bot entry point
+├── pipeline.py       # Orchestration (scrape → extract → PR)
+├── scraper.py        # Web page fetcher / cleaner
+├── extractor.py      # Claude-powered structured extraction
+├── yaml_handler.py   # conferences.yml read / insert / update
+├── github_pr.py      # GitHub branch + commit + PR creation
+├── config.py         # Environment variable loading
+├── requirements.txt
+├── Dockerfile
+├── docker-compose.yml
+└── .env.example
+```

preview/pr-37/bot/bot.py

@@ -0,0 +1,117 @@
+"""
+Telegram bot entry point.
+
+The bot listens for messages in any configured chat (channel, group, or DM).
+When a message contains a URL it kicks off the full pipeline and replies
+with a PR link or an error explanation.
+"""
+from __future__ import annotations
+
+import asyncio
+import logging
+import re
+
+from telegram import Update
+from telegram.error import Conflict
+from telegram.ext import (
+    Application,
+    MessageHandler,
+    filters,
+    ContextTypes,
+)
+
+from config import TELEGRAM_BOT_TOKEN, ALLOWED_CHATS
+from pipeline import process_url
+
+logging.basicConfig(
+    format="%(asctime)s [%(levelname)s] %(name)s: %(message)s",
+    level=logging.INFO,
+)
+logger = logging.getLogger(__name__)
+
+_URL_RE = re.compile(r"https?://[^\s<>\"']+")
+
+
+def _is_allowed(update: Update) -> bool:
+    """Return True if this chat is in the allowed list (or no list is configured)."""
+    if not ALLOWED_CHATS:
+        return True
+    chat = update.effective_chat
+    if chat is None:
+        return False
+    allowed_by_id = str(chat.id) in ALLOWED_CHATS
+    allowed_by_username = bool(chat.username) and f"@{chat.username}" in ALLOWED_CHATS
+    return allowed_by_id or allowed_by_username
+
+
+async def handle_message(update: Update, context: ContextTypes.DEFAULT_TYPE) -> None:
+    message = update.channel_post or update.message
+    if not message:
+        return
+    if not _is_allowed(update):
+        return
+
+    text = message.text or message.caption or ""
+    urls = _URL_RE.findall(text)
+    if not urls:
+        return
+
+    # Process first URL in the message; strip trailing punctuation
+    url = urls[0].rstrip(".,)")
+    logger.info("Processing URL: %s", url)
+
+    # Build a link back to the Telegram message for the PR body
+    chat = update.effective_chat
+    msg_link = ""
+    if chat and chat.username:
+        msg_link = f"https://t.me/{chat.username}/{message.message_id}"
+
+    reply = await process_url(url, msg_link)
+
+    await message.reply_text(
+        reply,
+        parse_mode="HTML",
+        disable_web_page_preview=True,
+    )
+
+
+async def handle_error(update: object, context: ContextTypes.DEFAULT_TYPE) -> None:
+    """
+    Global error handler.
+    - Conflict (409): Railway started the new container before the old one stopped.
+      Wait 15 s for the old instance to exit, then polling resumes automatically.
+    - Everything else: log it.
+    """
+    if isinstance(context.error, Conflict):
+        logger.warning(
+            "409 Conflict — previous instance still shutting down. "
+            "Waiting 15 s before resuming polling…"
+        )
+        await asyncio.sleep(15)
+        return
+
+    logger.error("Unhandled error: %s", context.error, exc_info=context.error)
+
+
+def main() -> None:
+    app = Application.builder().token(TELEGRAM_BOT_TOKEN).build()
+
+    app.add_handler(
+        MessageHandler(
+            (
+                filters.ChatType.CHANNEL
+                | filters.ChatType.GROUPS
+                | filters.ChatType.PRIVATE
+            )
+            & (filters.TEXT | filters.CAPTION),
+            handle_message,
+        )
+    )
+    app.add_error_handler(handle_error)
+
+    logger.info("MPC Deadlines bot started. Polling for updates...")
+    app.run_polling(allowed_updates=["channel_post", "message"])
+
+
+if __name__ == "__main__":
+    main()