trufas

s3proxy has a filesystem backend [0].

Possibly of interest: s3gw[1] is a modified version of ceph's radosgw that allows it to run standalone. It's geared towards kubernetes (notably part of Rancher's storage solution), but should work as a standalone container.

[0] https://github.com/gaul/s3proxy [1] https://github.com/s3gw-tech/s3gw

You're conflating git with git forges. Most popular forges use a centralized model. Git was built as distributed from the start and it's original mode of collaboration was through a federated protocol.

Apache doesn't enforce copyleft, so the Pear authors can license whatever changes they made to Continue with any license they want.

What isn't ok is to change the license of the existing code. They seemed to have corrected this since[0]. I think it's very hard to argue they didn't comply with the Apache license in this case, especially since the license is technically included in the forked git history.

On the surface this just seems like it was a naive and sincere mistake. I doubt that the Pear people were trying something nasty.

It also seems one of the founders has a fairly popular YouTube channel, so he's probably aware that this sort of nothingburger drama is great for business if handled competently.

[0] https://github.com/trypear/pearai-submodule/commit/335436b47...

I guess it makes sense but still, brave to be running all the infra on Arch ;)

This is really clean! I'll definitely be using it as a reference for IaC done right. Congrats on the migration.

They're using Gitlab CE. I assume the whole thing is running on their own servers.

How is setting up a Dockerfile and then a docker-compose file any simpler than just writing a unit file?

This seems like a perfect application of the init system.

I use it a lot for personal homelab infrastructure. I find it feels a lot more natural than single process containers for the workloads I use (torrent clients, game servers, plex...). I've unfortunately never used it for production workloads, and likely never will after recent news.

I also find lxc system containers better than OCI style immutable containers for dev environments for my personal projects, and LXD is the best way to manage them AFAIK.

LXD is great tech and a pleasure to work with. This blows. Hopefully an actually open alternative pops up.

Canonical's general bad attitude towards FOSS is just appalling.

SLUB is a nice story of a simpler implementation winning out, even when SLAB may have been more technically sophisticated.

CentOS 7 is supported and will be EOL at the same time as RHEL 7.

Stream does have major versions so you can continue to use CentOS Stream 8 and get backports. You only lose anything if you're tied to some minor version of EL for some reason.

product-market fit

Plugging a llm into dbus may take you surprisingly far.

It's happened before[0]

[0] https://en.wikipedia.org/wiki/New_Nintendo_3DS

There's no guarantee the boilerplate an LLM spits out will be up to date. It'll almost definitely have some outdated code in it's dataset that it can reference.

Only if you ignore the flawlessly at 60 fps part.

The one with the turtle[0]

[0] https://en.wikipedia.org/wiki/Logo_(programming_language)

If any other alacritty on macos users were looking for a workaround: https://github.com/alacritty/alacritty/issues/93#issuecommen...

Apparently an option_as_alt option should also be introduced in the next release.

That's what I thought too, but seems like that happened over a year later.

The data seems very questionable in general, so who knows.

For the UI part cockpit [1] lets you manage containers (amongst many other things). I use it with fedora for my home server and rarely feel the need to drop into the command line in my day to day.

[1] https://cockpit-project.org/

Ceph is the big one

Possible violations of the terms of use [1]?

> Engaging in automated uses of the site that are abusive or disruptive of the services and have not been approved by the Wikimedia community;

> Disrupting the services by placing an undue burden on a Project website or the networks or servers connected with a Project website;

I hadn't used wikiless much, but taking it down seems very against wikipedia's stated purpose.

How hard would it be to "fork" wikipedia? The content is already CC. I imagine the hardest part would be social momentum.

[1] https://foundation.wikimedia.org/wiki/Terms_of_Use/en#4._Ref...

The fzf plugin is really nice for navigating through files and for code search, but not really necessary.

The editing plugins I use most heavily are probably vim-surround and vim-commentary. My development would definitely slow down without them.

I doubt they'll want to compete in the consumer OS space after the ubuntu phone mess.

To be fair, you almost never should use the map builtin instead of the pythonic equivalent, list comprehensions.

`print([x + 1 for x in [1, 2, 3])`

I agree that the ruby approach is better in terms of consistency, but most developers will be aware of the conventions python uses.

The tradeoff here is that you don't have to explicitly declare new variables (something like `var` in js). Most people who work with python on a daily basis know you need the `global` keyword to avoid shadowing.

I think it was a good choice in the sense that it discourages mutable global state and makes the most common case more concise.

The idea isn't entirely new. The TGR Alice is a popular board that has two b keys [0].

The more straightforward approach to get a full extra column would be to just grab a keyboard that already has 7+ columns per side (ie the chimera[1]) and repurpose those to be duplicate keys.

[0] https://i.redd.it/9kyeyht1eqy11.jpg

[1] https://github.com/GlenPickle/Chimera

I don't think the GP was arguing against that. If you're already committed to an existing build process building new components as web components doesn't really have many advantages vs a component built in react. It's just adding needless complexity.

I found this to be a very good explainer. I particularly found the diagrams to be very illustrative. Congratulations on a great post!

Every couple years they'll define an edition of a language (e.g. rust 2015, rust 2018), the idea being that if you choose to stick to one of them, the latest rust will still compile your code as long as you tell it what version you're targetting.

Allegedly there's already an exploit in the wild that lets you open a popup in game to all other players in a server. You can find screenshots if you look around the /r/tf2 subreddit.