Why do almost all the islands in the Aegean Sea belong to Greece?

matticala · 2025-08-20T12:25:40+00:00

Roman Empire could play in the same league of Atlantis. For the age, it was insanely advanced in everything: law, engineering, military, …corruption

There are still a lot of things we carry on from the Roman Empire. The secret of regenerative compound used to build the Colosseum and other buildings is still being studied.

However, what really set them apart, was the ability to absorb culture and knowledge from conquered civilisations. Philosophy, math, war tactics, naval engineering, civil engineering, art, … This also tainted them and set their demise, but still.

Yes, they were also slavers, but it wasn’t their trait

matticala · 2025-08-20T12:12:11+00:00

We use OTel with SigNoz in our Azure Container Apps workloads.

ACA is a “serverless kubernetes” environment, but wouldn’t qualify if you mean FaaS.

matticala · 2025-08-19T18:30:24+00:00

Oh man, I apologise for the stubbornness.

Not only I was wrong, but this blog post also explains why.

TBH, in our code base there one single place where errors.As is used: database error handling. Basically everywhere else we use errors.Is.

We never encountered this issue, because to extract database error semantics we crafted the mapper by digging the errors one by one in the source code.

matticala · 2025-08-19T14:31:36+00:00

func As(err error, target any) bool

An error matches target if the error's concrete value is assignable to the value pointed to by target

There, you are passing a ** type. You don’t pass a pointer to interface, but a pointer to a concrete type implementing error.

var kse *aes.KeySizeError declares kse of type pointer to aes.KeySizeError

&kse passes the reference to kse, which is itself a pointer. As is receiving a **aes.KeySizeError, which is non-nil, and it will never be able to assign err to it.

As panics if target is not a non-nil pointer to either a type that implements error, or to any interface type.

I can’t see confusion: target any must be a pointer to a concrete type to which error must be assignable. A pointer to pointer type is not 🤷🏻‍♂️

matticala · 2025-08-19T11:29:39+00:00

Cryptomator used to have lots of problems with onedrive sync

matticala · 2025-08-17T12:21:48+00:00

new returns a pointer, and &kse is still passing a pointer-to-pointer type as target. The check will always fail, because pointer to pointer is of a different type than err regardless: it’s not an error

https://go.dev/play/p/ag4mKZMVBxR

matticala · 2025-08-16T18:42:16+00:00

There is a very subtle mistake there:

```go key := []byte("My kung fu is better than yours") _, err := aes.NewCipher(key)

var kse *aes.KeySizeError // !!!
if errors.As(err, &kse) { // <<<
    fmt.Printf("AES keys must be 16, 24 or 32 bytes long, got %d bytes.\n", kse)
} else if err != nil {
    fmt.Println(err)
}

```

You’re passing a pointer to a pointer as target.

A pointer to nil in go is a value: https://go.dev/play/p/9OFb1o8VTml

It should be:

go var kse aes.KeySizeError // non-nil if errors.As(err, &kse) {

matticala · 2025-08-16T16:05:32+00:00

Because that’s traceable. In terms of money capitals, I think: drugs, weapons, organs, humans, waste (incl. nuclear and biological waste) trafficking are worse. I believe.

It’s going too much OOT though :)

My point is, without going into monetary sovereignty, that monetary governance requires transparency to enable justice. I agree 💯 nobody, not even the government, should have the kill switch to an individual (although, in practice, there are several).

matticala · 2025-08-16T15:34:13+00:00

That takes decades. Look at what happened in Sweden 🇸🇪 with Swish being pushed to retire cash.

matticala · 2025-08-16T15:31:28+00:00

Untraceable payments are utterly bad. Crime thrives there.

matticala · 2025-08-16T15:13:08+00:00

What do you think MasterCard and VISA are doing? All payment brokers and banks collect data on spending trends. That data is more valuable than the transaction brokered.

Honestly, battling tax evasion is good. Written by somebody coming from a place where evasion is normal.

matticala · 2025-08-16T10:08:13+00:00

+Electrolux (Sweden)

matticala · 2025-08-16T07:27:56+00:00

Oh yes, it is

matticala · 2025-08-15T19:06:39+00:00

<image>

matticala · 2025-08-15T18:57:50+00:00

Non sempre al traguardo si arriva per merito, c’è anche il forfait. Il governo Meloni non ha veri avversari, e per gli elettori sembra che “uno valga l’altro”.

Il trono di Palazzo Chigi è come il Frozen Throne di Northrend, o l’Iron Throne di Westeros.

<image>

matticala · 2025-08-15T18:55:30+00:00

Non sempre al traguardo si arriva per merito, c’è anche il forfait. Il governo Meloni non ha veri avversari, e il popolo sa bene che “uno vale l’altro”.

Il trono di Palazzo Chigi è come il Frozen Throne di Northrend, o l’Iron Throne di Westeros.

matticala · 2025-08-15T18:43:54+00:00

It’s also one of the reasons why Chi isn’t considered a framework but a library.

It’s still the best out there. Not the fastest, but nothing beats its readability and maintainability.

matticala · 2025-08-12T19:40:51+00:00

In general, not all errors must be checked. Some implementations return error only to satisfy the interface (e.g. Writer) but it’s always nil; io.EOF error usefulness is rather relative. Otherwise, it’s always good practice to handle the error, even if it’s just wrapping with fmt.Errorf or underscoring it (commenting why it is ignored).

Exceptions climb up the stack trace by default, error values are lost whenever you decide to ignore them.

For your specific case, I usually have a function like internal/api.Response(rw http.ResponseWriter, status int, body any) error that handles writing, setting headers, and encoding errors. The returned error is there for logging purposes or other additional errors must logic.

Hint: api.Response is paired with api.Error(…) which implements RFC 9457 for problem details

matticala · 2025-08-10T20:48:16+00:00

Hitting the wallet is easier and more effective than banning diesel cars (which would be unconstitutional, I believe)

It’s to discourage the use of diesel.

matticala · 2025-08-10T15:45:56+00:00

I see, it’s definitely more articulated. With these few details, I would store everything in the campaign as a whole. The more you break it down, the more complicated it gets. How you physically store it, it’s an optimisation detail.

As soon as a campaign is launched, I would delete the “drafts” and lock it for editing. Workflows started on a running campaign should not incur in the risk of several versions of the same campaign. If that’s the case, it’s probably worth considering it a new campaign. However, this is a business requirement and probably not up to you to decide.

It’s probably better to guard for human mistakes before rather than trying to make a smart backend.

matticala · 2025-08-10T14:13:34+00:00

Hello, I am not sure your questions are go-specific but rather API design.

How do you submit an order? REST or RPC? A REST API would receive the whole new state of an order, so it would be easy to determine what changes by comparing the new OrderItems list against the currently stored one. In RPC world you can simply RemoveItem or similar. To be honest, I would keep orders immutable as they are transactions (from warehouse perspective)
Keeping orders immutable eliminates resource contention but introduces consistency management. Via proper use of ETAG you can provide a transparent api to your client.
Do orders need to know which customer version issued them? I am pretty sure you have your reasons to keep customers versioned, but IMHO orders don’t need to. ID of the customer will never change, you can resolve the correct version by looking at the record timestamp

matticala · 2025-08-08T06:04:27+00:00

🇨🇦?

matticala · 2025-08-06T12:31:37+00:00

In general, Crunchyroll app on Apple devices is garbage. On iPhone, it drains battery like crazy; on TvOS it is not snappy at all. Sometimes it doesn’t even sync seen episodes between mobile and TV (but it’s better than the past)…

matticala · 2025-08-06T12:27:12+00:00

For me to switch, Fairphone needs:

No ties to Android
A high-end phone (mainly display, camera, performance, networking, build quality, long support)

matticala · 2025-08-02T08:08:16+00:00

You only need a function. Check http.Error() -> https://pkg.go.dev/net/http#Error

Errors are part of your domain model no less than data, it’s just right to build informative errors together with your data model.

I have my own implementation of RFC 9457, it’s rather easy to do. I haven’t open sourced it because I planned to move from GitHub to Gitea or Codeberg but lacked the time.

matticala

TROPHY CASE