On the tower defense, upgrading the Laser Tower (to Beam Emitter) breaks the game.

Yeah but that’s why the cross-post feature exists in lemmy, so users can be part of similar communities without seeing the same story duplicated on their feed or having the conversation split in multiple places.

This is exactly what I was talking about, thanks!

Someone should make a service like this except you actually upload the file directly to the other user rather than uploading it to a 3rd party (encrypted or not). Yes I get you would have to wait for the user on the other end to connect to you before the transfer starts but if you’re uploading 100+GB of data you’re going to be leaving that browser tab open for awhile anyways.

Haven’t used the original but I do enjoy letting pipes-rs run on idle terminals.

I do use helix but haven’t taken advantage of the git integration. Maybe I’m unaware of its power. For fish, I defined my own fish_prompt function with an indicator if there are uncommitted changes. It’s just running git status under the hood. I have a TODO in that function to run a pijul diff in the directory if git status returns nothing…

The 1.0 is in beta. There has been a lot of refactoring to get it to this point. I would say there’s still many quality-of-life features missing that would stop me from using it in a professional setting but for hobby projects it’s meeting my needs (and gets better with each new beta build). They only have a few project backers but the main developer has been working very steadily on it.

This is actually why I prefer using pijul. I don’t want to commit my secrets to a git repo and nix will refuse to build because I’m pulling in files that aren’t tracked. Simple solution is to not make the flake directory a git repo and it won’t complain. That’s my solution at least. I also prefer using git (and therefore pijul) via cli rather than as a text editor integration so my experience differs.

I use it for self hosting because all I need installed is sshd and the pijul package. Then I can set my server’s ;p as my remote. The “nest” web UI (the Pijul equvivalent to git tea) is in development and not open source yet, but you can use the hosted version at https://nest.pijul.com/ if you’re curious.

https://pijul.org/

I like deadbeef because it reminds me of the foobar2k days. Very simple interface but behind the context menu is hidden tagging, replaygain editing, a robust plugin system, and all the more advanced features I need to keep my collection well groomed.

Just a grammatical nitpick in the readme but as a compound adjective it would be 13-foot Ladder. “That ladder is 13 feet tall” vs “That is a 13-foot tall ladder”.

What exactly are you removing from urls? It sounds like you need a tailored script that does a simple string replacement for you.

Gotta love the heavy use of buzzword technologies and no actual information on what is actual is. Then you click the “How does it work?” button and it takes you to a Google powerpoint… so much for the sleek website design.

Have you tried Immich? It has a very similar feel to Google Photos but with the advantage of owning your storage.

peer-to-peer, as opposed to?

I will say it took a bit of warming up to the composition API but referencing the static variables as opposed to this.variableName made it easy to spot a bunch of dead code in our components. I also don’t have to think about reactivity like I used to. Vue.set and Vue.observable just aren’t necessary any more. So from a surface level it seems you’re more abstracted and removed from the target browser code it outputs but from a cognitive overhead standpoint it’s been a simpler, cleaner experience using the composition api and build toolchain.

My only complaint is inside the script block you have to reference computed values as variableName.value instead of just variableName. If it wasn’t for eslint to tell me I forgot to type “.value” when referencing a computed value in the script block I’d probably screw this up a lot. Having to depend on eslint to address a shortcoming in the api feels wrong to me.