20 comments

  • ahmedfromtunis 12 minutes ago

    As a (former) reporter, site monitoring is a big part of what I do on a daily basis and I used many, many such services.

    I can attest that, at least from the landing page, this seems to be a very good execution of the concept, especially the text-based diffing to easily spot what changed and, most importantly, how.

    The biggest hurdle for such apps however are 'js-based browser-rendered sites' or whatever they're called nowadays. How does Site Spy handle such abominations?

  • tene80i 40 minutes ago

    RSS is a useful interface, but: "Do most people just want direct alerts?" Yes, of course. RSS is beloved but niche. Depends who your target audience is. I personally would want an email, because that's how I get alerts about other things. RSS to me is for long form reading, not notifications I must notice. The answer to any product question like this totally depends on your audience and their normal routines.

    • ikari_pl 15 minutes ago

      It's niche because some companies decided so.

      you used to have native RSS support in browsers, and latest articles automatically in your bookmarks bar.

  • dev_at 8 minutes ago

    There's also AnyTracker (an app) that gives you this information as push notifications: https://anytracker.org/

  • xnx 2 hours ago

    I like https://github.com/dgtlmoon/changedetection.io for this. Open source and free to run locally or use their Saas service.

    • vkuprin an hour ago

      Yep, changedetection.io is a good project. With Site Spy, I wanted to make the browser-first workflow much easier: install the extension, connect it to the dashboard, click the exact part of the page you care about, and then follow changes as diffs, history, or RSS with very little setup. I can definitely see why the open-source / self-hosted route is appealing too.

    • raphman an hour ago

      There's also https://github.com/thp/urlwatch/ - (not aware of any SaaS offer - self-hosted it is).

      • vkuprin an hour ago

        Yep, urlwatch is a good one too. This category clearly has a strong self-hosted tradition. With Site Spy, what I’m trying to make much easier is the browser-first flow: pick the exact part of a page visually, then follow changes through diffs, history, RSS, and alerts with very little setup

    • pelcg an hour ago

      Looks cool and this can be self hosted and it is for free.

      Nice will try this out!

    • beepbooptheory 31 minutes ago

      Sure but this one has a MCP server, costs money, and was presumably made last night!

  • reconnecting 18 minutes ago

    I remember there was something called Visualping many years ago, and the real issue was that when a website changed its structure, it broke the comparison.

    Did you solve this?

  • enoint 2 hours ago

    Quick feedback:

    1. RSS is just fine for updates. Given the importance of your visa use-case, were you thinking of push notifications?

    2. Your competition does element-level tracking. Maybe they choose XPath?

    • vkuprin an hour ago

      Yep, Site Spy already has push notifications, plus email and Telegram alerts. I see RSS as the open interface for people who want to plug updates into their own reader or workflow. For urgent things like visa slots or stock availability, direct alerts are definitely the main path.

      And yeah, element-level tracking isn't a brand new idea by itself. The thing I wanted to improve was making it easy to pick the exact part of a page you care about and then inspect the change via diffs, history, or RSS instead of just getting a generic "page changed" notification

  • hinkley 35 minutes ago

    Back in 2000 I worked for a company that was trying to turn something like this into the foundation for a search engine.

    Essentially instead of having a bunch of search engines and AI spamming your site, the idea was that they would get a feed. You would essentially scan your own website.

    As crawlers grew from an occasional visitor to an actual problem (an inordinate percent of all consumer traffic at the SaaS I worked for was bots rather than organic traffic, and would have been more without throttling) I keep wondering why we haven’t done this.

    Google has already solved the problem of people lying about their content, because RSS feeds or user agent sniffing you can still provide false witness to your site’s content and purpose. But you’d only have to be scanned when there was something to see. And really you could play games with time delays on the feed to smear out bot traffic over the day if you wanted.

  • bananaflag an hour ago

    Very good!

    This is something that existed in the past and I used successfully, but services like this tend to disappear

    • vkuprin an hour ago

      That’s a completely fair concern. Services in this category do need to earn trust over time. I built the backend to handle a fair amount of traffic, so I’m not too worried about growth on that side. My goal is definitely to keep this running for the long term, not treat it like a one-off project

  • makepostai 2 hours ago

    This is interesting, gonna try it on our next project! thumb up

  • digitalbase an hour ago

    Cool stuff. You should make it OSS and ask a one time fee for it. I would run it on my own infra but pay you once(.com)

  • pwr1 2 hours ago

    Interesting... added to bookmarks. Could come in handy in the future