2
20 Comments

I've just put together the beta version of the API. Anyone willing to try it (it's free)?

The API is not perfect, but if someone feels like giving it a shot, it would mean a lot to me: splitcss.com

I also made a Github package for Laravel, in case you are interested how an integration on a website might look like.

  1. 2

    That looks very interesting. Once you release a stable version, i'll use the service for sure. Good luck with the project.

  2. 2

    Hello @vlad86, can you email me [email protected] - about a possible security issue? I don't want to disclose publicly. Thanks.

    1. 1

      Oh sure Robin! I will email you right away! Thanks for helping me iron out the vulnerabilities

      1. 1

        Glad I could help.

  3. 1

    I gave it a try and successfully integrated it into my build steps for moving all the CSS on my home page from a stylesheet to the head.

    I received frequent timeouts, even after 60 seconds. Sometime the same request (nothing changed) would take 3 tries. It would be nice to have the ability to view access and error logs of my api requests through my account on your website.

    When I try to pass the query param bypass_cache=1, I receive the error message response: "{\"code\":\"UnprocessableEntity\",\"message\":\"\\\"bypass_cache\\\" is not allowed\"}". It would be very useful to have this working. Having to log in manually to your website to reset the cache is not something I'd like to add to my build steps.

    My account shows 0 (zero) calls for this month for my single API key after making multiple requests.

    Hope this feedback helps!

    1. 1

      Hey, I just noticed there is still a lot of CSS rules remaining that do not exist on the page: https://www.tipalink.com/. Any idea what's going on?

      1. 2

        Hey hey, thanks for your feedback and insights!
        We are working on it :)
        We will try to iron out the bugs asap and let you know.
        Seriously, I really appreciate your input.

        1. 1

          no problem. i know how every lit bit of user feedback helps!!

          1. 1

            Hey Derek, we have released a new version which should fix the performance issues and the bypass_cache parameter.
            The service is still in beta though, so number of requests is not officially logged yet.

            We would be happy to get more feedback.
            Cheers,
            Vlad

  4. 1

    Looks pretty interesting, I've bookmarked it, hopefully its a success so I can use it some day. The landing page looks nice as well. There's just some weird horizontal overflow for some reason..

    1. 1

      Hey thanks for the nice words!

      Could you please tell me your screen resolution, the device, the OS version and the browser version you are using?

      I'd like to take a closer look under which circumstances that weird horizontal overflow appears.

      1. 1

        Google Chrome 80.0.3987.149 (Offizieller Build) (64-Bit) (cohort: Stable)
        Problem persists independently of screen resolution, it also exists in the responsive view inside Dev Tools (at least when viewing normally and enabling dev tools after it loaded). Honestly, I'm super confused right now. Good luck trying to fix (or even reproduce this)

        1. 1

          Cool thanks for the info! Is that a desktop machine that you are having? And if yes, is it a Windows machine? I think sometimes it matters, so it would help me reproduce it.

          1. 1

            Yes, I'm on desktop. Tried on a 4k display and a 1080 set to 2x to avoid scaling issues. I tried with Chrome, Edge & Internet Explorer 11. The page looked like garbage on IE, but the horizontal scroll issue persisted.

            Note that the video container has a bigger outline (dropshadow) than the dark blue preview frame with the green button.

            1. 1

              Thanks! I'm on mac, and tbh I forgot to test it on a Windows machine.
              I'm downloading a Windows VM right now .
              Thank you so much for pointing it out!

  5. 1

    A few notes:

    1. The example curl command provided in the docs didn't work for me. I needed to provide the -g flag to allow including [] in the URL.
    2. Did you consider using standard HTTP content negotiation for determining the response format instead of your own idiosyncratic way? E.g. curl -H "Accept: application/json"
    3. You may want to consider a more permissive cross origin policy. I can imagine wanting to call your API from a web app.
  6. 1

    That looks interesting and will definitely try it out in the near future. I'm happy to drop you a message when I'm testing it and with my feedback if you would rather that privately rather than on a public forum.

    1. 1

      Thank you so much! 🙏

      Pity that there is no private messaging feature on IndieHackers.

      You can reach me on Github, Twitter or email any time.

      1. 2

        Yeah it is definitely a shame although I think it keeps the community as open as possible.

        I have just followed you on Twitter and sent you an email so you have my details as well.

Trending on Indie Hackers
How I grew a side project to 100k Unique Visitors in 7 days with 0 audience 47 comments Competing with Product Hunt: a month later 33 comments Why do you hate marketing? 27 comments $15k revenues in <4 months as a solopreneur 14 comments Use Your Product 13 comments How I Launched FrontendEase 13 comments