Viewing profile — PaoloBarbolini
PaoloBarbolini
HN member- Joined
- Mon, Jul 12, 2021, 5:42 AM UTC
- HN karma
- 99
- Public activity
- 31 items
- HN profile
- View on Hacker News ↗
About PaoloBarbolini
Recent public activity
-
comment
Comment #49037103
They confirmed on LinkedIn that they are working on it. Also, they have a feature request that has been getting many votes recently: https://feature-request.scaleway.com/posts/1251…
-
comment
Comment #47886766
Why do we still put up with GNOME? I've spent the last 10 years off and on from Linux. Had I used something other than GNOME, I believe my experience would have been better. I've b…
-
comment
Comment #46202639
There are many things they don't seem to understand about their own product. https://github.com/nats-io/nats.rs/issues/1253#issuecomment-...
-
comment
Comment #46118959
The repo link goes to a 404 page.
-
comment
Comment #46005049
The image could have been encoded with a high compression ratio, or even something like OxiPNG. In that case, while re-encoding it wouldn't lose quality, it could still have the si…
-
comment
Comment #44793581
A few years ago I convinced a friend to make their blog using Ghost 4. Very bad decision. I haven't kept up with it but at the time they supported only 1 mailing list service. What…
-
comment
Comment #44754345
That's "easy" when all they have to do is to package https://github.com/raspberrypi/linux
-
comment
Comment #44529863
I've had the same experience and I fixed part of the problem by writing my own Rust client, Watermelon. It's still missing a lot of features but at least I'm not blocked by weird d…
-
comment
Comment #43794833
See also the issue: https://github.com/nats-io/nats-server/issues/6832 Archived version: https://web.archive.org/web/20250425154144/https://github.co...
-
comment
Comment #43380581
I'm also finding that this has happened already in the past and GitHub didn't cleanup the spam entirely, like: https://github.com/Xyntax/1000php/issues/1#issuecomment-2318...
-
comment
Comment #43380136
Before this event, I've has another encounter with GitHub. What happened is that an AI coding assistance startup seemed to have created bots that would: 1. find new GitHub issues o…
-
comment
Comment #43380015
Amazing work! This is the first time I've seen this kind of issue fixed so quickly. GitHub should learn from this.
-
comment
Comment #43379899
Link to search results: https://github.com/search?q=%22We+have+detected+a+login+atte...
-
story
GitHub Phishing Campaign making use of OAuth and render.com hosted site
A phishing campaign has been ongoing in the last 4 hours, opening more than 11.5k issues containing the wording "We have detected a login attempt on your GitHub account that appear…
- story
-
comment
Comment #43257063
`curl https://myip.wtf/json ` too is nice to use when debugging things
-
comment
Comment #39904030
Same for Rust. In the short term we're trying to solve it on the user's side with https://crates.io/crates/cargo-goggles , but in the long term the registry should probably do it.
- story
-
comment
Comment #39533172
Could you provide an example?
-
comment
Comment #39520996
It means they protect themselves from layer 3 and 4 DDoS. For layer 7 you're mostly on your own. That's what most companies mean when they talk about DDoS anyway.
-
comment
Comment #39520962
This is the reason I've never used all of these user-facing serverless services. The price depends on the usage, but if anything goes wrong they are the ones to decide what you pay…
-
comment
Comment #39213062
Certificates can be issued for IPs too, CAs don't usually do it though.
-
comment
Comment #38923367
According to the documentation[1] Kafka is just one of the supported inputs for ingestion, so it should be possible to run Quickwit without it if you're not intending to write logs…
-
comment
Comment #36369106
I've been trying their Arm servers for a while and I've noticed some differences in the colors in htop for Debian 12, as if there were a slight difference between the x86_64 and th…
-
comment
Comment #36148289
Also if you're worried about the server having a different timestamp and possibly not having configured the connection timestamp correctly, as the following test shows Postgres alw…