Hacker Newsnew | past | comments | ask | show | jobs | submit | samsep10l's commentslogin

(async function() { const UNFOLLOW_LIMIT = 800; const delay = (ms) => new Promise(resolve => setTimeout(resolve, ms)); const findButton = (txt) => [...document.querySelectorAll("button")].find(btn => btn.innerText === txt);

  console.log("Start");

  for (let i = 0; i < UNFOLLOW_LIMIT; i++) {
    const $next = findButton("Following");
    if (!$next) {
      console.log(`No more users to unfollow, stopping at ${i} unfollows.`);
      break;
    }

    $next.scrollIntoViewIfNeeded();
    $next.click();
    await delay(100);

    let $confirm = findButton("Unfollow");
    if ($confirm) {
      $confirm.click();
      await delay(100);

      // Verify if the unfollow was successful
      $confirm = findButton("Follow");
      if ($confirm) {
        console.log(`Unfollowed #${i + 1}`);
      } else {
        console.log(`Failed to unfollow #${i + 1}`);
        i--; // Do not count this as a successful unfollow
      }
    } else {
      console.log(`Failed to find the "Unfollow" confirmation button for #${i + 1}`);
      i--; // Do not count this as a successful unfollow
    }

    await delay(20 * 1000); // Wait 20 seconds, Instagram allows about 200 unfollows per hour
  }

  console.log("The end");
})();

https://github.com/eyeblech/insta-unfollow.js


This Python script monitors the connection status of Mullvad VPN and alerts you with a sound when it disconnects.

https://github.com/eyeblech/mullvad-alert


A lightweight Python utility that polls a YouTube channel or playlist and sends a notification when new videos are published. Works with Discord webhooks and can be scheduled via cron.

https://github.com/eyeblech/yt-vid-notifier


wow , you tryna fck me or what!


>> Would love feedback from terminal + Python folks


Huge thanks to https://github.com/Itz-Ashlynn/ for Terabox-Web—the API that makes this all possible.


kinda , yeah - sickos


leave a feedback folks:|


Perhaps consider a public domain film for the demo?

https://en.wikipedia.org/wiki/List_of_films_in_the_public_do...


looks cool! one bit of feedback: make your demo gif get to the point faster. either practice typing a bit quicker or speed it up 2x for the typing section


Or use a terminal recorder to generate it:

https://github.com/orangekame3/awesome-terminal-recorder


oh my god , i have fcking updated my demo.gif

get outta here !


Might want to add a disclaimer/warning and/or add additional confirmation/wording before downloading. You don't want your user to go to jail because of a mistake that could be avoided: https://news.ycombinator.com/item?id=46364645


Great tool I would have loved back when I watched movies :) Could the same be done for music ?


>Use it. Fork it. Improve it.

These———LLM———slop———READMEs———make———me———vomit.


The emoji everywhere is what does it for me. Emoji on every title. Emoji on every item of a list. The same ones over and over. So much visual noise. They’re used like a deficient visual crutch.


I always tell my LLMs: "Try not to sound like an LLM. And no emojis!"

Works alright.


Most boring part of developing is writing docs. I see it as boilerplate. If you don't like it, you're free to open a PR.


The whole repo is fucking boilerplate.


Get used to it. Nobody will write readmes by hand. I've always hated it and now I'll just let the LLM write it.


It's certainly a sign of something. Not positive at best neutral. As you say it's at best an indication that the author doesn't like writing.

Could it be an indication that the author didn't write the actual code? Is it a sign that the author doesn't really care that much about their project and furthermore could that be a sign that the project is also be be valued by us as much as the author? Maybe the code quality and documentation is less important than the utility. After all many of us don't like writing tests for code!

Perhaps but perhaps we just need to get used to these signs too and get over it.


It used to be "don't try to outsmart the compiler", I'm waiting for the time people start saying the same thing about LLMs.


"you're absolutely right!"


Then get some freaking taste in READMEs. We can guide the LLMs to better results.


This argument is getting old. Just because you don’t like something, it doesn’t mean everyone agrees and will take the same shortcuts you do. Fortunately not everyone in the world has the same disregard for their own work, and many of us understand the signal it sends when you’re unwilling to even write your own instructions.

If you want your READMEs sloppily written by LLMs, that’s your prerogative. Just like it’s the prerogative of everyone visiting your repo and bumping into a slop README to decide if they want to even give your tool a second look before abandoning it.

Slop READMEs suggest slop code. Soon everyone who’ll even look at your code are other sloppers and (if it ever gets popular) malicious actors who’ll exploit it in an afternoon because no users understand anything the code does.


the world is moving towards this, so all the naysayers will be dinosaurs :-)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: