While I agree shopify has a kind of “mierda touch”, I still see it as if it goes sideways with them someone will just fork the code.

It is true for raid 5 & 6. Raid 0, 1, and 10 are supposed to be production ready. I use raid 10 only with btrfs, anything else and I use zfs or mdadm.

Linus? 'That you?

My only gripe with btrfs is that I’ve had systems come down from a single drive failure in raid quite “often” when compared to other FS.

ZFS is a ram hog but I always could do a live resilvering without downtime.

Intel has not halted sales or clawed back any inventory. It will not do a recall, period. The company is not currently commenting on whether or how it might extend its warranty.

Any evidence of that? Genuinely curious as I can’t really find anything about them being by the same people and forgefed started as mailed-based prior to forgejo existing.

edit: seems like they are funded by different organizations and the main contributors to forgefed never worked on forgejo, they worked on vervis though.

Just to give credit where credit is due, git federation is a Forgefed Initiative

Forgejo is implementing it in their platform.

One of the first interaction I witnessed from the forgejo guys was this PR:

https://github.com/go-gitea/gitea/pull/27455/

The interaction and stubbornness of earl-warren felt like it was just that, provoked drama.

I use owncloud infinite scale and overall its rock solid. The downside is the lack of plugins. Nextcloud has been nothing but trouble for me and every update was a mess so I decided to try OCIS and for my need I was extremely satisfied.

Now, I admit, I’m not one to get carried by the drama in the FOSS sphere (still use Gitea) but I do agree there is an history to the separation of owncloud and nextcloud that can make some people uncomfortable. Having a choice is good I believe.

Should have been called Lignux.

tar -h

Edit: wtf… It’s actually tar -?. I’m so disappointed

There you go:

# Start an infinite loop because True will always be True
while True: 
    # try to run the main function, usually where everything happens
    try:
        main()
    # in the case an exception is raised in the main function simply discard (pass) and restart the loop
    except:
        pass

For those curious about the drama & lack of wide adoption surrounding the walrus operator

https://dev.to/renegadecoder94/the-controversy-behind-the-walrus-operator-in-python-4k4e

It’s a shame because it’s a really nice feature.

I started using hatch lately and really like how I can manage everything from the pyproject.toml file

https://github.com/pypa/hatch

My secret to high uptime:

while True:
    try:
        main()
    except:
        pass

deleted by creator

Edit: something that are not arm based

You want pre-built to run ollama, that’s at least gonna cost you an arm, maybe even a leg.

Easy enough that I could get the car to pass the provincial inspection roughly a month after I got it. How long did it took you to get that Audi S2 road legal?

A lot of the kei trucks and cars have a Suzuki F6A or K6A engine that was also used in some artic cat snowmobile. That kind of commonality makes it easy enough to find parts. Worst case scenario it is a 2 weeks wait time to get the part delivered from Japan. You know what took me more than 2 weeks to get some parts? A 2015 VW golf.

I drive a kei car and I just want to point out that their size makes it less of a burden to see incoming traffic than full size rhd vehicule.

As for the security concerns this would be valid if we were applying the same restrictions on other 25+ years old cars as well as motorcycles.

In Quebec we had the same type of witch hunt against JDM back in 2009 and what came out of it is that we’re the only Canadian province where rhd cars must be 25 years old minimum. So because they said they were not secure enough, they stopped allowing more secure/recent versions of the cars people wanted.

So yeah, I doubt it’s really just a security thing in the end.