thatsnothowyoudoit @ thatsnothowyoudoit @lemmy.ca

Posts

1

Comments

184

Joined

2 yr. ago

It’s all hallucinations.

Some (many) just happen to be very close to factual.

It’s sad to see that the marketing of these tools has been so effective that few realize how they work and what they do.

Emotionally.

https://archive.ph/osq2e

Except it’s accidentally stabilizing it. Source am a progressive Canadian living in a (normally) regressive Province. Not like Alberta regressive but still surrounded by Oligarchs.

For the most part Garuda has a GUI for everything. It’s Arch on easy mode and it’s most excellent for new and seasoned users alike.

I tried it only because I wanted to give Linux gaming a try and I struggled to get any other distribution to work with my graphics card - I liked it so much I switched to it permanently for my work desktop as well.

While there are many reasons to dislike (or outright avoid) Apple - if you purchase music from them, it’s DRM-free and useable anywhere.

I believe they were one of the first official channels to do this.

Still, hadn’t heard of Quobuz and will check them out!

You’ve described Ghost. Subscriptions for content are a first class citizen.

It’s primary a writing platform with built-in monetization options and the ability to self host. We switched to it from Substack. It’s been fantastic to use and operate. Super slick.

But that’s exactly my point - we here in this bubble prefer Jellyfin - but it’s not ready for mass adoption. Even plex is a drop in the bucket.

In 20 years I’ve been contacted directly once for a specific bug in an Apple application.

I send feedback a couple of times a year.

I see Jellyfin suggested as an alternative to Plex here. I hope it is one day.

At the moment it’s nowhere close.

I’ve been running Jellyfin side-by-side Plex for two years and it’s still not a viable replacement for anyone but me. Parents, my partner, none of the possible solutions for them come anywhere near close to the usability of Plex and its ecosystem of apps for various devices.

That will likely change because plex is getting worse every day and folks can contribute their own solutions to the playback issues. With plex it’s more noise, more useless features. So one gets better (Jellyfin) and one gets worse (Plex).

But at the moment it really isn’t close for most folks who are familiar with the slickness of commercial apps.

Even from the administrative side, Jellyfin takes massively more system resources and it doesn’t reliably work with all my files.

Again, Jellyfin will get there it’s just not a drop in replacement for most folks yet.

And for context I started my DIY streaming / hosting life with a first gen Apple TV (pretty much a Mac mini with component video outs) that eventually got XBMC and then Boxee installed on it. I even have the forksaken Boxee box.

I’m not defending them because it’s a shit move, but they clearly understand the most valuable feature is not their ad-ridden free content but rather the original value prop of the service to make it easy to share personal media with small groups of friends.

We use NGINX’s 444 on every LLM crawler we see.

Caddy has a similar “close connection” option called “abort” as part of the static response.

HAProxy has the “silent-drop” option which also closes the TCP connection silently.

I’ve found crawling attempts end more quickly using this option - especially attacks - but my sample size is relatively small.

Edit: we do this because too often we’ve seen them ignore robots.txt. They believe all data is theirs. I do not.

Ran WireGuard on a Pi1 and it was fine for two users. Albeit WireGuard was the ONLY thing running aside from a Gitlab Runner.

A 4b should be more than enough for many use cases except things that cause torrents of packets - but even then YMMV. It really depends on the workload.

One bit of advice: if you can, use a storage device other than the micro-sd slot for the 4B. Again YMMV.

You’re right. My bad. Will edit.

You’re right though and I should not have used “totem pole”. Old habits..

I’m with you on all those points. Loblaws is theft of a different kind and to your most important point: these stores have made it impossible for smaller stores to exist - so I also get that you might not have a choice.

And thanks for responding so kindly. Appreciate you.

My perspective here, to share, is that I don’t understand the hard time others are having. Not that I can’t understand - but rather that I am not in their shoes. I’ve been trying to cut all workers slack because they’re also trapped in a system and we’re powerful if we stick together - so forgive me if I also forgot to empathize with you.

I have to ask - how did you think a cashier can help with your request?

I’m not trying to be a jerk here, but cashiers are pretty low on the corporate ladder at Loblaws. If you knew it wasn’t their job, what were you looking for and what did you want in response?

I don’t shop at Loblaws. We’ve been shopping locally since the boycott last May.

But one of the things worth considering is what we expect of each other. Was one person’s rudeness reflective of everyone else who works somewhere?

There are so many way we can work together to make our communities and country stronger. Not shopping at Loblaws can be one of them. But for this reason? I’m sorry, it just seems strained and unusual.

Edited to remove racist euphemism.

I’m sorry but I I have to agree

It depends on many factors including:

• visits of individual sites
• requirements of each site (memory, I/O, persistent storage, ephemeral storage, caching, databases, etc.)

So you’re right that you make an initial guess and go from there.

Many tools/sites/projects will have minimum system requirements and you can get an idea of minimums using those stats. Some frameworks might even have guidelines available. The one I use most often for example has a configurable memory footprint. So that’s a datapoint I personally use.

If they’re all the same type of site (example Ghost blogs) using the same setups then it’s often less intense since you can pool resources like DBs and caching layers and go below minimum system requirements (which for many sites include a DB as part of the requirements).

Some sites might be higher traffic but use fewer resources, others might be the inverse.

Then there’s also availability. Are these sites for you? Is this for business? What kind of uptime guarantee do you need? How do you want to monitor that uptime and react to needs as they arrive/occur?

The best way to handle this is in a modern context also depends on how much and what style of ops you want to engage in.

Auto-scaling on an orchestration platform (something like K8S) or cloud-provider auto-scaling of VMs or something else? Do you want deployments managed as-code via version control? Or will this be more “click Ops”. No judgement here just a thing that will determine which options are best for you. I do strongly recommend on some kind of codified, automated ops workflow - especially if it’s 25 sites, but even with just a handful. The initial investment will pay for itself very quickly when you need to make changes and are relived to have a blueprint of where you are.

If you want to set it and forget it there are many options but all require some significant initial configuration.

If you’re ok with maintenance, then start with a small instance and some monitoring and go from there.

During setup and staging/testing the worst that can happen is your server runs out of resources and you increase its available resources through whatever method your provider offers. This is where as-code workflows really shine - you can rebuild the whole thing with a few edits and push to version control. The inverse is also true - you can start a bit big and scale down.

Again, finding what works for you is worth some investment (and by works I don’t just mean what runs, but what keeps you sane when things go wrong or need changing).

Even load testing, which you mentioned, is hard to get right and can be challenging to instrument and implement in a way that matches real-world traffic. It’s worth doing for sites that are struggling under load, but it’s not something I’d necessarily suggest starting with. I could be wrong here but I’ve worked for some software firms with huge user bases and you’d be surprised how little load testing is done out there.

Either way it sounds like a fun challenge with lots of opportunities for learning new tricks if you’re up for it.

One thing I recommend avoiding is solutions that induce vendor lock-in - for example use OpenTofu in lieu of something like CloudFormation. If you decide to use something like that in a SaaS platform - try not to rely on the pieces of the puzzle that make it hard (sticky) to switch. Pay for tools that bring you value and save time for sure, but balance that with your ability to change course reasonably quickly if you need to.