I have to say, after the recent Performative UI post here on HN, I was not expecting an apache foundation project to have gradient words on the landing page.
if, like me, you're a non-native english and speaker don't immediately understand what this is about: the page shows for each `n` what's the minimum `s` such that `n` squares with side of length 1 fit in a square with side of length `s`.
what I'm curious about though is what a proof for something like this looks like. and why does it need a proof? not to mention the randomness of some of the `n`s. Math is most of the time beatiful and whenever I see something like `n=11` I think "it looks wrong so it must be wrong" yet it has a proof.
Do you want the graphs with 300 squares to be bigger than your screen, or do you want the graph with 1 square to be 30x30 px for no reason? They're just zoomed.
That's what I mean, I can't imagine why anyone would argue the same thing of graphs in general so I'm curious what the difference makes it so they find it so odd in this specific case.
Hi, sorry for not responding sooner, didn't realize this post existed.
Traceway is fully OTel compliant.
Go: The original version started with Go SDKs. I've since moved to using Go OTel. I haven't updated those docs yet because the Go SDKs still work and are used in the wild, but they're on the deprecation track. Thanks for pointing it out.
Symfony: There were no good one-line OTel integrations out there for Symfony, so we wrote one. It is not a custom SDK, it's an OTel configurator. You can use it with any backend, not just Traceway. We're firm believers in contributing back to the OpenTelemetry community.
Frontend / mobile: This is more complicated. The current frontend and mobile OTel spec does not allow session replays to be sent, so for those platforms we still keep SDKs with a custom protocol alongside OTel. As soon as the spec matures I'm hoping to move it fully to OTel.
At this point it must be intentional that there's always something uncanny about these fake pages. That google logo is so old that if I see it I immediately know to get out of there.
So I find it fascinating how there's always the odd typo, the old logo, the impossible combination of iPhone needing an antivirus, etc and I refuse to believe is incompetence.
Entirely intentional because they want to filter out anyone who can see how scammy it looks, so they don't waste their time. This is bulk spam stuff. If they are actually targeting you, it will look very real.
I don't buy it. The actor running the website likely gets paid for every user that installs the app or possibly even every user they direct at the app.
Even in the unlikely case that they get paid for achieving some later payoff, the "work" on the way there is almost certainly 100% automated so there is no harm in spraying the attack more widely (as opposed to Nigeria scams where pre-AI, pre-slave-farm, the scammers would have to invest significant amounts of a very limited resource - their time - on each victim).
https://news.ycombinator.com/item?id=32023863
https://wso2.com/engineering-platform/developer-platform/doc...