azdle

This is just a guess, but I'd imagine that happens because the websites use JavaScript to load the actual content of the page, but Lemmy is just parsing the HTML that is returned.

Also, I really doubt you'd have much luck convincing website authors to completely change their architecture just to get previews to work on Lemmy.

You're an Agnostic.

Agnosticism is the view or belief that the existence of God, the divine, or the supernatural is either unknowable in principle or unknown in fact.

The repo owner claims to have permission from contributors to relicense (and rewrote some other parts where they couldn't get permission?): https://github.com/stenzek/duckstation/pull/3295#issuecomment-2348988362

I don't really understand the rest of that comment though...

Point to point wireless network link: https://store.ui.com/us/en/category/all-wireless/products/af-24

As for what it's for, it could be anything. Possibly just for the camera that's also on that pole?

Yeah.

Yep, I'm genuinely unsure if the conversations actually happened or not. I've gotten different answers to that from different people.

As someone who is currently hiring: Anything

Beyond that it depends on what you know and what kind of work you want to do.

At work we have a contractual design deliverable that was due yesterday, I still can't get anybody to tell me what I'm supposed to be designing/building. I've got the contract, but its so vague that it's more unhelpful than it is helpful and there's apparently been 9 months of conversations with the customer, none of which have included engineering, nor has anything from them been written down. So we're designing something just based on rumors.

So we're in crunch mode, but also we don't know what we're trying to accomplish... 😩

They may block IP addresses associated with consumer ISPs. Assuming that's the case, I would guess you're seeing that as an HSTS/TLS error because their network is trying to trick your browser into redirecting to/displaying an error page hosted by some part of their network.

Hey, this might be something I'm interested in, but I'm not sure because there aren't many details in your readme.

Some questions I'd suggest you answer in the readme:

[Edit: after looking through the code quickly, some of my questions probably don't male sense because this seems to be an alerting style monitoring tool, not a observability style monitoring tool. Answering my own questions for others that are curious:]

What does it monitor?

[Disk space and CPU use]

What is the interface? Web? It does compare itself to grafana, so maybe. TUI? Maybe that's what makes it more light weight?

[It doesn't have one, it sends telegram messages when alarm thresholds(?) are hit.]

Does it only work on Debian? If not, are there deps that are required that are installed as dependencies of the deb?

[Looks like it should work anywhere, the 'watchers' use the nix crate and read procfs, so I assume that means it should work anywhere without depending on anything besides the Linux kernel.]

Is there history or is it real time only?

[Realtime only, well I guess there's the telegram history.]

What does it look like? (Honestly, a screenshot could possibly answer most of these questions and a whole lot more.)

[It doesn't look like anything. There's no screenshot because there's nothing to screenshot.]

[edit: To be clear, I assume the part that OP is not sure if it's satire or not is "or switching to a more privacy-conscious browser such as Google Chrome."] The emphasis in

Firefox is worse than Chrome

is in the original. To me that clearly implies that they are of the opinion that in general Google & Chrome are worse on privacy than Mozilla & Firefox. The comment at the end is just tongue in cheek snark alluding to the fact that in this particular case google did better for privacy in Chrome than Mozilla in Firefox.

or switching to a more privacy-conscious browser such as Google Chrome.

Definitely satire, the context from earlier:

2. Firefox is worse than Chrome in their implementation of ad snitching, because Chrome enables it only after user consent.