I just want to build requests and read the responses, why the hell does everyone suddenly want me to make an account?

  • breadsmasher@lemmy.world
    link
    fedilink
    English
    arrow-up
    37
    ·
    edit-2
    5 months ago

    It seems that way with a lot of REST clients for whatever reason.

    It starts off as what we all want - a simple rest client, maybe storing environments and requests

    Then companies start building more features to try and create a whole community or ecosystem

    They start asking for account creation. Then team creation to share with your team. Then an enterprise plan. Then they gimp the original features and paywall them.

    Looking at you, Postman, Insomnia, Thunderclient

    • kjpctech@lemm.ee
      link
      fedilink
      arrow-up
      2
      ·
      5 months ago

      I’ve been using Bruno since Postman started asking for an account. It works but it does feel like I’m missing a lot of features.

  • Charlie@social.veraciousnetwork.com
    link
    fedilink
    arrow-up
    8
    ·
    5 months ago

    @lorty I feel your pain; I had to switch from Postman to Insomnia because I couldn’t use the local application anymore without creating an account, but even Insomnia is pushing to create an account somewhere.

  • PeriodicallyPedantic@lemmy.ca
    link
    fedilink
    arrow-up
    3
    ·
    5 months ago

    I wonder how hard it’d be to make a PWA and host it on GitHub 🤔 Maybe this would be a good yet-another-hobby-project-ill-never-complete to pick up

  • Carol2852@discuss.tchncs.de
    link
    fedilink
    arrow-up
    2
    ·
    5 months ago

    Intellijs build in HTTP client is good enough for me to use it for my testing purposes and even for short one-off thing I previously might’ve done with curl.

  • expr@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    5 months ago

    https://curl.se/ has been account free since 1998.

    Never understood why people keep trying to use proprietary tools for this, especially when curl is so good.

    I have a directory of shell scripts I use to test out endpoints. I persist request/response data either with environment variables or regular files. Oh and since these are just shell scripts, it’s pretty trivial to do stuff like iterate over a CSV (or JSON array) and make a request for each row, conditionally make requests, or whatever else you want.

    Oh and honorable mention goes to jo and jq for making it super easy to make/process JSON data.