Honestly, I wouldn’t be surprised if the inclusion of some small AI feature is what justified the rest of this work being done. As in, someone got approval for tab groups only because they were smart enough to describe it as “AI powered tab groups“. Just speculation
Oh I forgot to mention this part. They have a free demo on Steam with ~1/3 of the playable content. That alone is great. The full game is reasonably priced too and they’re still rolling out content updates frequently
Backpack Battles! Fantastic little inventory management game with a load of replay value.
There’s cryptpad though I don’t have a clue how complicated it is to manage. But it’s a decent user experience.
I’m really not sure if “Failed to load media” is a voyager error or the real post 🫠
This isn’t exactly a rogue like but there are some similar aspects and I find that it satisfies in the same way. The game is Backpack Battles. Available on Steam. There’s a free demo available too with full mechanics but limited character options.
This is my default game more for when I have a few minutes to relax and nothing more pressing to do
I had to look up the releases for this one 😂. It must have been v1. I last used flux maybe 2+ years ago. That predates flux v2.
Have you used v2? If so, what do you think about it?
Oh I could easily be wrong about forgo having integrated ci/cd already. It’s the only tool I mentioned shove that I have never used before. I’m not a good source on this one.
But I have used both flux and argo quite a lot. I’ll admit that it flux implementation was bad, but it was just a bad experience for everyone using it with me. It was a memory hog and often created. Very few people understood how to use it correctly. When there were errors with e.g. a helm template, you just had to go looking for issues and read through the log. It moved git tags around so you don’t get a history of what flux was doing. I could probably remember more issues if I tried.
But none of that was a problem with Argo. We just started using it successfully on day 1. Plus its UI is fantastic and a huge advantage. It’s easy to navigate, spot issues, troubleshoot, etc. It also exposes users to resources they unknowingly create because Argo displays owned resources. This part really helped people understand what was going on in k8s. Oh and argo is very extensible. Maybe flux is too but I haven’t tried.
They’re both good and quite similar on the surface. But I find that larger, more complicated uses tend to get messy with gitlab because of the heavy use of bash. However, actions are (always?) written in typescript. If your automation needs a lot of logic to handle varying uses, then it’s nice to avoid bash and code with a more language.
In other words, I’ve seen a few monstrosities that large companies build into gitlab and yikes!
Nope. I’m using a mobile app (voyager). No browsing history available
I would have liked to but I can’t access the deleted post now. Does Lemmy provide a means of seeing deleted posts?
I use proton vpn and Firefox Focus on iOS. I’m not sure which of them is doing the heavy lifting, but I rarely see ads on my phone.
If you’d like to learn more about Haptic, why it’s being built, what its goals are and how it differs from all the other markdown editors out there, you can read more about it here.
As others have noted, the app doesn’t work on mobile yet. Anybody willing to share the content here for mobile users?
That basic idea is roughly how compression works in general. Think zip, tar, etc. files. Identify snippets of highly used byte sequences and create a “map of where each sequence is used. These methods work great on simple types of data like text files where there’s a lot of repetition. Photos have a lot more randomness and tend not to compress as well. At least not so simply.
You could apply the same methods to multiple image files but I think you’ll run into the same challenge. They won’t compress very well. So you’d have to come up with a more nuanced strategy. It’s a fascinating idea that’s worth exploring. But you’re definitely in the realm of advanced algorithms, file formats, and storage devices.
That’s apparently my long response for “the other responses are right”
deleted by creator
A complicated plugin ecosystem (e.g. Jenkins) makes for a terrible use experience. It’s annoying to configure a bunch of config files. Managing dependencies can be a complete nightmare. these problems also complicate your ci/cd.
So I’ll offer a slightly different answer. I prefer a single file instead of splitting up the config. And I’ll use OpenTelemetry as an excellent example of why. the plugins are compiled right into the app binary. This offers a ton of advantages, including a great reason to merge all of your app configs in a single file.
This really only works well if you have a good app though.
Open source software literally means that the source code is available to anyone. In GitHub, that just means that your repo is public rather than private. But your method technically doesn’t matter. You could publish to a forum if you wish. That’s still open source!
Free OSS just means that anyone is free to use and modify the source code for any purpose. The details are usually defined in a LICENSE file.
I feel like you’re really asking about the common practices and methods used in FOSS. Right? If so, that’s entirely up to you as the maintainer. As the project matures, you may attract other contributors which will in turn will motivate change to your tools and methods.
Start with what works for you. Model after similar projects if you wish. Adjust as change is needed.
lol got it. Definitely not email then
Uh email? It’s not exactly exciting but there are loads of tools available for automating emails. Definitely asynchronous. Does it fit your needs?
That would be great. I frequently have to click the link and navigate to a home page for a meaningful description. Here’s the opening statement from Koto’s README on GitHub.
This is the first thing I need to read to understand if I should or should not care about the project and its new release.