by khoobid_shoma ·
Hello Today, I got a suspicious message from a stranger Telegram user. After some minutes, I opened the notification and only read the message without opening any link. Then immediately, I got an error about no service availability for my simcards. I do not remember the exact error message but it was something like that. I restarted my phone immediately and re-insert the simcards (from different operators in different countries). But, none of them connects to network anymore.
My Telegram account is still accessible and I checked no other sessions are alive on unknown devices.
I turned off my phone which is Android (Samsung). I also blocked my phone number for now.
I am "sure" it was not a furtuitous and bad chance. Everything happened in 1 second. The message was saying "I am looking for my father in Germany..." and the user name had strange characters. I can also share the user name in comments but I feel that it might put the others in risk as well.
Does anyone know what happened ? What actions shall I take besides changing passwords and enabling 2FA for email, messengers, ... accounts?
by grillorafael ·
# Show HN: LinkPreview.io - Debug social cards across 6 platforms (no signup)
I built a tool that shows how your URL looks when shared on Twitter, Facebook, LinkedIn, Slack, Discord, and Google Search. All in one view, no login required.
Try it: https://linkpreview.io
## The Problem
Debugging broken social share cards currently requires jumping between 5+ platform tools (Facebook Debugger, Twitter Card Validator, LinkedIn Post Inspector), each requiring authentication. I wanted one place to paste a URL and see everything.
## What's Different
Most tools just show raw meta tag data. This renders actual preview cards and scores your tags 0-100 with actionable fixes.
- Both card variants (Twitter/Facebook each have large + compact layouts) - Truncation visualization (shows exactly where titles get cut on each platform) - Scored recommendations (20+ checks with copy-paste code snippets) - Zero friction (no signup, <2 second results)
## Tech Stack
SvelteKit (Svelte 5), Cloudflare Pages, Cheerio for server-side parsing. Client bundle <30KB gzipped.
The hard part was SSRF protection. The API fetches user-provided URLs, so I had to block private IPs, cloud metadata endpoints (169.254.169.254), and check every redirect hop to prevent attackers from using my server to port-scan internal networks.
## What I Learned
Open Graph is inconsistent across platforms. Twitter falls back to og:title sometimes. Facebook requires og:type, LinkedIn doesn't. Google ignores Open Graph entirely. Character limits vary wildly and are undocumented.
## Future
Phase 2: bulk CSV upload, scheduled monitoring, API access, Chrome extension.
Built over a weekend. Feedback welcome.
SvelteKit, Tailwind v4, Cloudflare Pages
Built this over the past few days: FiveMinuteLove https://fiveminutelove.com
It lets you create a private page with:
names + message 3–6 photos optional music optional unlock date / secret word / custom URL Use case: last-minute but personal digital gift (Valentine’s Day, anniversaries, etc.).
I’d love feedback on:
Is the core value clear on first load? Any friction in create -> preview -> checkout? Trust concerns before payment? Happy to answer technical questions too (stack, Cloudflare deploy, SEO pages, etc.).
by Mrakermo ·
I killed my Calendly link after someone I barely knew booked an intro call 30 minutes before my biggest sales meeting of the quarter. Then another person wedged themselves between two important calls, forcing me to reschedule everything.
The problem: Calendly treats all meetings as equal. It doesn't know that some people matter more, or that some time blocks are sacred.
So I built the opposite. When someone requests a meeting:
1. It searches your email history with that person
2. Understands the context (hot lead vs cold outreach vs investor vs "just curious")
3. Learns your actual schedule preferences (not just "availability")
4. Suggests times that make sense for THIS specific meeting's priority level
Example: A prospect who's been emailing about a deal gets offered your best slots.
Someone wanting to "pick your brain" gets next Tuesday at 3pm and nothing else.
It's still early—I'm using it myself and with ~10 beta users. The context analysis is basic (email volume, reply speed, keywords) but it's already prevented 3 calendar disasters this week.
Built with [tech stack]. Would love feedback, especially from anyone else who's been burned by the "first-come-first-served" scheduling model.
Live at: https://atimeforeveryone.xyz