Here's mine: https://github.com/foundata/hugo-theme-govanity (e.g. used at https://golang.foundata.com/ )

And yes I'm aware of the irony of hosting this on GitHub... still figuring out a good workflow for maintaining our OSS on Codeberg and GitHub in parallel fed from the internal forge. The dependency on our own domain is real but we favor it.

Comments URL: https://news.ycombinator.com/item?id=49705394

Points: 2

# Comments: 2

It has a similar workflow for taking screenshots and then immediately annotating or editing them, without having to open a separate image editor. And: it provides also an local OCR feature (which is why I comment this here), you can extract text from a screenshot with on-screen OCR using Tesseract with the small button beside the "Crop Image" one.

Combined with the syntax-highlighting feature for screenshots of code snippets, the OCR is surprisingly useful in combination if you e.g. quickly discuss some code in a chat when copy is blocked for whatever reason (e.g. somone sent you a screenshot in the first place).

[1] https://gradia.alexandervanhee.be/

[2] https://flathub.org/en/apps/be.alexandervanhee.gradia

Edit: fixed wrong link index numbers

Completely ditched VS Code and never looked back.

Maybe some Ubuntu-specific issue?

  Internal error: Usage credits are required for this model.: {
    "errorKind": "rate_limit"
  }

[Edit] Update from https://status.claude.com/

> We are aware of an issue preventing users from selecting Claude Fable 5 within Claude.ai, Claude Code, and other surfaces, and are working to resolve this issue. Jul 17, 2026 - 18:36 UTC

1. For generic TLDs like .com/net/org/., the rules mostly come from ICANN, the registry, and the registrar.

2. For country-code TLDs like .de/io/to/io/ai/ly, the rules come from that ccTLD's own registry. Best example AFAIK: .ly domains must not contain obscene contents contrary to Libyan law or Islamic morality (which was a driver for bit.ly's domain change)

So ccTLDs are not simply "generic TLD rules plus country rules." They are their own category with their own policies. Trademark violations are one way to lose a domain, but not the only one. The risk is MUCH higher when using a country TLD.

    There are two major problems with .io domains:

    The first is that the islands which should own the domain suffix, don't, thanks to a wonderful piece of modern day British Imperialism. If you ever feel the need to donate to us, please give it to a more worthy cause.

    Secondly, there was a security issue with the .io domain. In 2017, a researcher managed to take control of four of the seven authoritative name servers for the .io domain. We accept that mistakes can happen, strong processes limit the chances of them happening, but they still can.

https://www.passbolt.com/pricing/pro

https://www.passbolt.com/vs/bitwarden/overview

https://www.passbolt.com/docs/hosting/install/

PHP backend (IMHO a downside): https://github.com/passbolt/passbolt_api. But There appears to be a significant amount of auditing behind Passbolt's security claims, assuming the information on https://www.passbolt.com/security is accurate.

I think the same: Small service businesses care most about Time To Recovery (TTR) when doing services. As long as they communicate at least by phone and the website is up, they usually tolerate downtime when they know when their backoffice services are back online.

This is classic Business Continuity Management, 5-10 questions usually make clear what must work in every case when and what has to be available for supporting this process. Example: I got a customer which prints all logistics / distribution labels in batches. They can still work where money comes in (=shipping stuff) for quite a long time (4h min, 8h max) if the next batch of labels cannot be printed / some system is going down needed to support shipping. So no need for expensive HA around legacy software, but enough time for a good process to get back online with the latest backup on replacement hardware which is already there on-site.

The thing is: HA is FAR more expensive and complicated than e.g. getting another stand-by server as fast replacement, maintain the hypervisor on this second server e.g. every six month and test restoring backups on it once a month (best: automated: IMPI boot, restore without VM networks, testing, shutdown). Same with a firewall; two used Enterprise Servers + Proxmox VE Subscription, OPNSense + 2 x N150 Hardware and two consumer WANs (e.g. Cable and VDSL) is really not that expensive if only the WAN is a bit more complicated from the POV of a SME admin because of failover. Classi VLANs+ACL and services like surveillance as needed...

> Businesses with <10-20 employees are often viewed as not being worth the effort of having as a customer, so they end up with self-serve, unsupported, non-discounted, over priced, trash subscriptions. By the time they grow enough to be a valuable customer their only experience with some products is misery.

Exactly. This is why I do SME IT since ever, no matter for which $BigCorp I've done consulting and DevOps. I automate them. I consult them. My company (plug: https://foundata.com) does it for a few bugs per month (Hypervisor, Groupware (Calendar, Mail) Firewalling, VPN, Directory Services, Jitsi/OpenCloud/BBB) if they understand that they finance the high quality of the managed services ON THEIR HARDWARE with all other customers and we do not work per-hour but per-service + we run Open Source also for other reasons than "no or fewer licensing costs".

And I like it even this does not make you rich. Because I REALLY share your concerns ("owning all the small businesses of certain types; family doctors, dentists, optometrists, vets" -> I don't know where you are from, but it is the very same here in Germany... example: https://www.ndr.de/fernsehen/sendungen/panorama3/Spekulanten...)

I just read:

> If I had learned one thing from my past life was that if you see the signs of an abusive relationship, you have the option to walk out, and you don't, all that follows is your own fault.

so... :)

  ~/.local/bin/hugo0.145.0
  ~/.local/bin/hugo0.148.0
  ~/.local/bin/hugo0.149.0
  ~/.local/bin/hugo0.150.0
  [...]

And this is really not a production problem. As stated in the comments before, just don't upgrade if you don't want to / have no time yet. It is a self-contained static site generator without external dependencies. It won't break. And the security of an old Hugo binary is mostly a non-issue if you do not load remote content.

And, if you have some time: Their changes are really well documented. The changelogs are really good.

The main problem is sticking with an unmaintained template of a third party which breaks when you finally want to upgrade and don't want to fork / don't know when a an template update comes along. But that's the reason I write my own. It was worth the effort.

> Low maintenance[...]A single Docker container, using SQLite as database. Automated migrations, zero breaking changes.

sounds nice. How does this compare to Linkwarden or Karakeep (formerly Hoarder) in terms of features? A comparison would be useful.

Comments URL: https://news.ycombinator.com/item?id=47365416

Points: 1

# Comments: 0

Sadly, LinkedIn has replaced email for initial contact after fairs or in-person client meetings. New real-world contacts look you up on LinkedIn and then use it to ask for things like your email address or mobile number. Because of this, I'm even verified :-(.

Even though I use LinkedIn basically the same way Internet Explorer was used in 2009 (purely as a Firefox or Chrome downloader but not for browsing). LinkedIn is my initial contact details exchange, but not the platform to communicate.

> Isn't that just all ai slop?

It is. I basically get zero useful input. Just biased, shallow rubbish. If there is valuable content it is usually cross-posted from authors who also run blogs I already follow.

Edit: Spelling, grammar, style

LinkedIn does not support smaller companies; it appears to rely on some kind of whitelist or known-enterprise system. This option is simply not available for at least 90% of users.

We're planning to roll it out at our company (foundata) in Q4, so you’ll get at least a few bucks from us. I'll also happily recommend it to our customers. As an OSS company and service provider, I can very much relate to the lack of marketing budget and the constant SEO spam.

The concept that every message belongs to a topic and the async communication focus makes so much sense to me. I read conversations, not timelines.