HN user

zertrin

296 karma
Posts3
Comments38
View on HN

GW and TWh are not the same unit. You need to multiply by the hours of effective sun in a year (and applying some reduction factor for the fact that there isn't 24h of sun every day, nor that the full production capacity is reached)

Even if that doesn't cover the energy demand, the number is not negligible for 438 GW of capacity. Assuming that the effective full sun equivalent in terms of energy production is only 10% of a day in average, we get: 24 h/d × 365 d × 0.1 × 0.438 TW = 384 TWh

I have no idea about the 10% factor, someone more knowledgeable can coreect me, but, we are not speaking thousands of years if the growth continues before the full energy production value is getting close to the energy demand.

Priceless quote:

With Legacy Support, organisations running their systems on top of Ubuntu 14.04 LTS can obtain an additional two years of expanded security maintenance and phone and ticket support. This enables IT managers to prepare a detailed upgrade plan for the next LTS

Yeah sure... Couldn't make that plan over the last 8 years, but two more will surely do it.

JSONB has landed 3 years ago

Yeah, learned about it while reading the documentation of Fossil (from the same SQLite people). Their approach certainly has its own merits (and drawbacks).

Just wondering how they will transition once the original few people at the top of the hierarchy need to retire, eventually it will happen.

I guess they need to find younger trusted committers with the same dedication and spirit. That's not necessarily easy. But for a piece of software as important as SQLite, I have a feeling they will find those.

I don't know about the percentage of affected stars in a typical galaxy collision but note that you don't need a collision for two stars to affect each other. We're not speaking of interaction like on a pool table. The gravity will significantly affect star systems that pass significantly close from each other.

I had the same experience, trying to self-host my VPN or other evasion solutions only served to get my server and domains banned for all other purposes from inside the GFW. The symptoms were exactly the same as you described (at first, they "sort of work, but unreliably, with extremely minimal bandwidth and would suddenly stop working after some time").

In the end, I'm not going to try that anymore, I haven't been in China for 2+ years now due to COVID, but next time, I'll hope my server is out of the blacklist again and hope I can access my (self-hosted) emails and other normal services that don't try to evade it.

The student VPN of another Asian university or the employee VPN of a well established company seemed to work last time. Not sure if that can be counted on reliably though...

I also feel the same. Unfortunately there's no way back for pgAdmin. But also no way forward to look for. I am convinced the Web based version won't be able to match pgAdmin3 usability ever.

I just forget about it and use DBeaver instead.

Same experience here, used the workaround.org tutorial as strong inspiration (not blindly copy pasting, but to serve as guided path to follow and learn).

Steep learning curve indeed, but after initial setup it's just working and necessitate no tending except when I do major upgrades (of Debian so every 2.5 years on average), in case some config needs updating.

But this is really a private email server with no users except me, thus probably not encountering the issues related to mail servers with many users that might or might not have a good email hygiene.

Not doubting any of your statements, but why have I never heard of it before? If it is good why hasn't it displaced ethereum and become more mainstream? Are there any cons that prevent it to become more prominent?

(sincere question from me, I am curious to know more)

Octet is the word used for bytes in French. Data sizes in French locale are expressed most often in ko, Mo, Go, To ...

I do this too (running it in a docker container on my server to mutualise usage across several devices) and it suffice for catching the main errors and typos. Quite happy with it.

Can indeed be recommended as substitute to grammarly free.

If only 3 words wasn't a proprietary black box, which demands that you use their service / api and that you are not allowed to reproduce it without their assent. Plus there's a bunch of other drawbacks to w3w if you just search a bit online.

At least the algorithm for plus codes is known and can be reused even if Google decides to drop it in the future.

Yeah, I was an avid user of self hosted gitlab previously, but the pace of added bloat^Wfeatures was just too much and I ditched it for gitea about 1 year ago.

I feel gitlab's is now mainly aiming at large enough companies which actually use all of these features.

They discussed a lot about their own internal bottlenecks. I'm wondering about the external bottlenecks they might encounter, such as the requirement for sending all certificate requests to CT logs prior to issuing a certificate. Could it be that the amount of data and requests per seconds sent to external entities to fulfil CT obligations is deemed negligible or already manageable?

I have been self hosting my emails for many years on cheap dedicated servers (previously kimsufi by OVH and now Hetzner).

Never had any issues with sending mail. But I've been careful with the initial setup and have all the expected requirements covered : no open relay, SPF, DKIM, reverse ip, TLS,...

Been using the tutorial at workaround.org as basis for building the stack (postfix, dovecot, rspamd,...) and, while the initial learning curve was high, once its been set up, its been a really very stable setup requiring practically no maintenance whatsoever.

Not saying that's for everyone, just saying it works for me.

I guess I was lucky at the dice roll mentioned by other comments.

Ah yeah, and testing your outgoing emails using a service like mail-tester.com is very very useful. I aimed for and reached a perfect score 10/10.

Even if everything is HTTPS as you claim (spoiler, it is not, there's still plenty of other protocols in use today) subdomains are still relevant information used in SNI to serve virtualhosts.

There is no reason that imposes www.example.net to serve the same content as example.net. Whether or not it does is left to decide by the website operator.

Yeah in E2EE key distribution is always the tricky part.

For "good" UX, usually it is based on trust that the peer keys are exchanged with help of the centralised service as middle man but that it does not alter the keys.

For good security, each party should ideally check public key fingerprints with each other party via another mean of communication to ensure that there was no man in the middle. But that's poor UX and might be unpractical for large meetings of participants that do not know each other.