Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
talboren
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
by
talboren
3y ago
check out the "Choose an open source license" website [1] [1] https://choosealicense.com/
62.
▲
Bird Has Filed for Bankruptcy
(prnewswire.com)
1 points
by
talboren
3y ago
|
0 comments
63.
▲
Snowflake Announces Agreement to Acquire Samooha
(snowflake.com)
2 points
by
talboren
3y ago
|
0 comments
64.
▲
Intel launches Core Ultra processors
(techradar.com)
164 points
by
talboren
3y ago
|
276 comments
65.
▲
GraphQL Is Finally Boring
(wundergraph.com)
1 points
by
talboren
3y ago
|
0 comments
66.
▲
Valve squashes a decades old Half-Life bug
(theverge.com)
2 points
by
talboren
3y ago
|
0 comments
67.
▲
by
talboren
3y ago
i assumed it's due to bc but does that mean that bc > security? question is how hard do they push/expose the risks of using soon-to-be deprecated tech
68.
▲
by
talboren
3y ago
why just now? there are many known attacks (SSRF[1] for example) that are based on IMDSv1. maybe i'm missing something but feels like this should have been done a long ago? [1] https://www.cyberbit.com/uncategorized
69.
▲
by
talboren
3y ago
companies often find themselves using more than 1 tool that generates alerts, for instance when Datadog is not sufficient (lacking some integration, need some other dashboard capability, etc.). Grafana Observability survey mentioned that 52
70.
▲
by
talboren
3y ago
Paul Ganssle released a great article[1] explaining why you shouldn't use utcnow in 2019. [1] https://blog.ganssle.io/articles/2019/11/utcnow.html
71.
▲
by
talboren
3y ago
gonna give it a try today, been wondering how come i never came across anything like that actually (been using the different clients tools)
72.
▲
by
talboren
3y ago
st2 reminds me a lot of what we're building at https://github.com/keephq/keep (i maintain this oss), there are a few concepts that i really love but the video in the repo really gives me a 90s feelin' i can&#
73.
▲
by
talboren
3y ago
they surely doesn't help with the "migration" (application layer) part but they help you manage things with code, which is better than nothing (you can do some heavy-lifting to make it work in another provider afterwards) tha
74.
▲
by
talboren
3y ago
is things such as alerts/dashboards/proprietary data is easily exportable with SigNoz? For instance if I’d like to manage them with terraform
75.
▲
by
talboren
3y ago
Like other things around, there’s always the people’s problem but when vendor locked, that’s yet another big issue to address
76.
▲
by
talboren
3y ago
Was and still is one of the biggest problems orgz have without even knowing they have them. until it hits. I think architects should give that thought from a very early stage of a company and often don’t
77.
▲
Vendor lock-in in the observability space
(keephq.dev)
103 points
by
talboren
3y ago
|
38 comments
78.
▲
Source Code at Risk: Critical Code Vulnerability in CI/CD Platform TeamCity
(sonarsource.com)
1 points
by
talboren
3y ago
|
0 comments
79.
▲
Openv0 – Open-source generative UI component tool inspired by Vercel's v0
(github.com)
4 points
by
talboren
3y ago
|
0 comments
80.
▲
by
talboren
3y ago
YAWS - yet another web server
81.
▲
by
talboren
3y ago
tough one. can’t say how much i don’t envy him as a founder. stay lean, stay humble, appreciate the honesty and feeling bad for folks who got the message
82.
▲
by
talboren
3y ago
Wow this is fun.
83.
▲
by
talboren
3y ago
"open source visual editor" doesn't really comply with "The self-hosted drag and drop editor for React."
84.
▲
by
talboren
3y ago
looks awesome, a small screenshot in your readme would have helped understand that it's more of a drag and drop component
85.
▲
by
talboren
3y ago
and your feedback is much appreciated! noted for next time. (i actually did the demo in a rush so it was more just showing a simple usage of the platform) we'll think about some changes to the README asap! thanks!
86.
▲
by
talboren
3y ago
wdym by "Rollup's"? I answered re:stackstorm st2 in another comment: > i think a few major points would be: 1. we're much more integrated and focused on the tools (and even more specifically on the monitoring tools),
87.
▲
by
talboren
3y ago
i think a few major points would be: 1. we're much more integrated and focused on the tools (and even more specifically on the monitoring tools), we actually integrate with their APIs and not only receive events from. 2. trying to be a
88.
▲
by
talboren
3y ago
well actually documentation around that is still under construction ( https://docs.keephq.dev/development/adding-a-new-provider ) but adding a new integration (provider in our terms) to Keep is a piece of cake! happy to
89.
▲
by
talboren
3y ago
Datadog or us? ^^'
90.
▲
by
talboren
3y ago
thanks! happy to help your team migrate to Keep and send out a few complimentary monitors ;)
More ›