bozly

7 ms·

1.
by bozly 6y ago
Wildcard DNS records (i.e. `*.example.com`) are your friend in situations like this :)
2.
by bozly 6y ago
Found the bug! Live updating should be working now
3.
by bozly 6y ago
I understand the frustration of too many logins :) If I do end up adding user accounts, it would only be to add extra functionality (persistent URLs etc) - the existing functionality + potential perma-link feature would all remain available
4.
by bozly 6y ago
The header details can be expanded by clicking the ">" arrow to the left of the "[{...},{...},etc]" I think this could be a bit more intuitive though, thanks for the feedback!
5.
by bozly 6y ago
they are auto generated by `styled-components` - a great option for "css in js" in the React ecosystem
6.
by bozly 6y ago
Great idea, having a perma-link as an alternative to the browser cookie would be very nice - I'll add this to my list :) I'm currently working on user accounts, which will eliminate the need to use the same browser.
7.
by bozly 6y ago
Oh boy, that's an embarrassing bug! Found the issue, and I'm working on fix now Edit: bug squashed - this should no longer be an issue
8.
by bozly 6y ago
Live updating should work - I'll investigate if there's any issues with the websocket api :)
9.
by bozly 6y ago
hmm - I can see a few requests have been received & stored for that endpoint.. It could be that your client killed the connection to the websocket api - does refreshing the page show the requests?
10.
by bozly 6y ago
Thanks, simplicity is definitely what I am aiming for! Making this an OSS project is the direction I plan to take - just need to tidy up the code a bit before making it public :) The current implementation is serverless on AWS though, and m
11.
by bozly 6y ago
This was definitely a concern... Each unique subdomain is checked for collision before being assigned, so no two users will receive the same endpoint. Additionally, it is assigned with a jwt, so even if someone was to brute force an endpoin
12.
by bozly 6y ago
yep, that's exactly it :) - I'm using an ALB on AWS to manage the incoming requests
13.
by bozly 6y ago
Looks like requestbin will only keep 20 requests for 48 hours. Currently, endpoints.dev will store an unlimited number of requests for 30 days. The plan is to add user login, and lift the 30 day limit for authenticated users.
14.
by bozly 6y ago
Thanks! webhook.site also looks great, I love their inclusion of an email address... I might take some inspiration from them in my next iteration ;)
15.
by bozly 6y ago
I've just released endpoints.dev - Use it to get a unique, private url that will store & display all http requests made to it. Use your unique URL with 3rd party tools to see what requests they are making, without needing to spin u
16.
Show HN: Endpoints.dev – Pastebin for HTTP Requests(endpoints.dev)
201 points by bozly 6y ago|50 comments
17.
Show HN: Retrospectively tag AWS resources so you know who created them(github.com)
6 points by bozly 7y ago|0 comments
18.
Automatically tag existing AWS resources to find out who created them(gorillastack.com)
5 points by bozly 7y ago|0 comments