@eshol@lemmy.world

One thing I’d note is what sourcehut has done is far beyond what codeberg has, specifically this part:

original content written with or which facilitates the use of LLMs (large language models) or other generative AI technologies

What codeberg did was the first part - content written with LLMs, though even that is “mostly”. Sourcehut goes way more restrictive.

And a shot out to @alam@lemmy.world for BentoPDF! Glad to have you here and an awesome tool to boot.

I generally don’t ever look at dashboards, only historical data, and only after an issue.

I get an alert that there is an issue, and if its an issue thats happened before, there is an automation to address (this is why I look at historical data, to determine indicators).

So I never need to look on a mobile dashboard, because the only thing I’m interested in is the notification. The only way that isn’t going to work is if I have a larger outage, but I get a notification through work for that - I have a site-to-site setup so I could attach a switch to my work network for work reasons, and if that goes down I get a notification through my work setup (and vice-versa, which was a fun morning when that side went down).

You can, I’m just saying be prepared for disappointment. The amount of effort you need to put in, imo, you could have had a spreadsheet and been done. And then used that with a script to autogenerate some mermaidml to get a purdy drawing out of it (which I highly recommend leveraging Beautiful-Mermaid ).

And then you can feed that to an llm and make your queries about ports or other uses, to me thats a much better use/approach. To each their own though.

Nope, and I wouldn’t recommend it either. They are generally not great with mapping IMO, no matter the model.

And really this is better managed with a quick diagram and a spreadsheet. If you want some software, look at netbox for this, you can add in validation rules and all kinds of automations as well.

But really, use a spreadsheet.

My workstations are Debian, my laptops are a mix of Debian and Arch, same with test hardware.

They all look the same - KDE as my desktop environment, no generic software added at install, just adding what I want. If you were to use any one of them purely from the GUI (KDE), I doubt you’d know which was which without checking version info.

Linux is a kernel. A desktop environment is the GUI. The distro is packaging.

The difference between distributions is predominantly what is packaged up, the tool used to install/update, and an overarching philosophy on those tools.

Debian is about being stable. This means more dated packages, but running into issues from an update is (mostly) not even a question when running the stable branch. Amazing for workstations and older hardware IMO.

Arch updates constantly. Updates can introduce breaking changes, even minor ones, which can interrupt workflow. It also means the latest and greatest features are right there and ready quickly. I like arch for testing and making use of recent hardware that may not have support elsewhere yet.

You could also build entirely from source, use a downstream from Debian like Mint (Debian Edition) or Kubuntu, or downstream of Arch like SteamOS or EndeavourOS. Downstream distributions add more opinion under a more particular approach to their upstream counterparts. For some its to make the system easier to install (EndeavourOS vs Arch), add more recent features (Kubuntu vs Debian), or to make something incredibly specialized (SteamOS, formerly based on Debian and now based in Arch, highly focused on gaming).

The only thing thats “pure” Linux is the kernel. Everything else comes down to purpose and preference.

I’ve gone this route! Anything with a busted screen is fair game to me, though I haven’t picked up any recently, mostly just tiny/mini/micros (and heavy on the lenovo tiny).

But a custom hacked up laptop can be a great option especially with tight space to work with

Edit: I’m surprised I missed your original post! I did the same, though what I reused was first a lenovo tiny, more recently updated with a digital signage player I picked up that I swapped parts out on - way more fun than a standard console imo!

Could be a 20s clip! 😀

I read the original differently than you, but it seems its been edited in the meantime (and I’m on mobile at the moment)

Either way, I think all is well currently

Testing, test plans, and QA is not “mostly all”.

Let’s also stay on topic please. Its tagged appropriately and the relevant disclosure is present.

That really isn’t the issue, and no, that would not be permitted here. It would be one thing to note that an LLM was used in some part of the project, it would be entirely different to criticize the poster based purely off whether or not there were any contributions involving LLM.

That would be a rule 1 violation.

If you want to comment on a known vulnerability, thats one thing. Commenting that its vulnerable because an LLM had a pair level patch is not.

Ah, got it, I misunderstood from the post, sorry about that

deleted by creator

deleted by creator

between your device

Thats the part right there. Its for not your device to access.

Like a self- hosted website/blog for example. Or taking the complexity of “start this before you try to connect to my eBook server” for your BIL, or “OK mom, when you want to watch the home videos I converted to digital you have to do it only from your phone, press this first, then share to your TV”.

That is the part I think you are missing. Use other than yourself and your own managed devices.

Also please add the appropriate tag - [AIP] in this case - to the title

If you have internal DNS (technitium, pihole, bind, whatever), split DNS is easier (and, imo, better for long-term use). Your local DNS serves local IPs, public DNS serves public IPs.

And it can tie in pretty darn nicely with Jellyfin

That wouldn’t count as anything other than CBH, since it wasn’t involved in any stage of programming/documentation/etc - more like testing samples, which is no different than users sending crappy pdf’s along imo.

@alam@lemmy.world Please update your post with a tag and disclosure as needed per rules 7 & 8.

See disclosure at the bottom - Implementation lists pair.

Thats 50/50 per our rules here.