qprimed
@qprimed@lemmy.ml
- Comment on Feel the burn 1 month ago:
please! I need to unsee this!
- Comment on Zilog Calls Time on the Venerable Z80, Discontinues the Standalone Z84C00 CPU Family 2 months ago:
ok, thats just really cool. 👍
- Comment on Hyundai pauses X ads over pro-Nazi content on the platform 2 months ago:
well, that escalated quickly. :,-(
- Comment on Instagram will blur nudes in messages sent to minors 2 months ago:
lots of comments about e2e encryption (or the potential lack thereof)
even if it is e2e encrypted (and I mostly believe it is), once its decrypted on your device (in their app) its in the clear. there is nothing technical preventing the app from then inspecting the data or forwardiing the data to another party for analysis - thats a “terms and conditions” issue.
the article claims they are doing some on-device recognition - thats likely computationally non-trivial, with variable accuracy (false positives/negatives, anyone) and probably at least partially circumventable and perhaps even exploitable (more app surface area to attack).
so, ok… its a lead-in to classifying content on your device. I have no idea what comes next, but I am pretty sure there will be a next and this is why I don’t intentially use any meta products.
- Comment on My new Commodore PC-10 III...! ima need some opinions on this one 2 months ago:
that is some.ancient hardware. 200 euro is kland insanely high price. :-/
your “internet connector” is an arcnet network card - not much used to you, but quite a cool little heirloom.
assuming the memory is not soldered, you can swap out SIMMs (like 30 pin), or DIPs/ZIPs if you can even find them. you may have some fun trying to bring this PC back from the dead, but that price is insane for an ancient box in poor shape. good luck.
- Comment on Microsoft’s new era of AI PCs will need a Copilot key, says Intel 3 months ago:
microsoft marketing burning the midnight oil, I see.
- Comment on Stuck on Let's Encrypt certificate issuance due to firewall issue even after opening necessary ports 3 months ago:
heh, forgot about the standalone web server in certbot. thats a good ephemeral option.
- Comment on Stuck on Let's Encrypt certificate issuance due to firewall issue even after opening necessary ports 3 months ago:
if you are able to run a public web server, then certificate issuance via certbot http challenge works pretty well. the web server can serve a really simple static page with little to nothing on it - but of course its another potential vector into your network.
if your public domain DNS makes use of a supported dns provider or you run your own publically accessible dns server, then dns certbot challenges are great and more flexible than http.
others may suggest neat work arounds for the http challenge issue, but if you have access to a supported dns service I would look at that option. certbot has helpers for quite a few public services as well as support for self hosted dns servers. I run my own public dns servers, so thats the option I chose and use certbot hooks, cron and bash scripts to rsync the updated carts to the propr hosts for the various services I run privately and publicly.
- Comment on Stuck on Let's Encrypt certificate issuance due to firewall issue even after opening necessary ports 3 months ago:
if you are using http cert retrieval, certbot needs a place put the temp. token to authenticate your contrrol of the domain your are creating a certificate for. usually that will be the same webserver you want to serve the certificate from.
if you are not running an actual weberver on port 80 that certbot can insert a token for, certbot cannot complete.
this is, of course, in addition to other possible issues such as ISP port blocking - but without a web server listening on TCP/80, you will have to use other authorization methods (like DNS) to generate a cert.
- Comment on Stuck on Let's Encrypt certificate issuance due to firewall issue even after opening necessary ports 3 months ago:
are you actually running a web server on that host? iirc, certbot will place a temporary token to be served by your web server (Apache, etc.) to show that you actually control the domain you are requesting a cert for.
I switched to DNS based retrieval as soon as let’s encrypt offered it, so its been years since I retrieved certs via http.
- Comment on Remembering multi-tasking in MS-DOS: DESQView 4 months ago:
hey there, friend! still running a wildcat BBS on DOS and Desqview here. 5 wildcat instances on a Pentium 133MHz box with 32MiB of RAM and a NETBIOS connection to a fileserver and access to the nodes via a rocketport sio board and a serial server for telnet. gotta admit desqview, when properly tweaked up, really is an amazing bit of magic.
currently trying to get things moved over to freeDOS and virtualize the whole thing on qemu with virtualized serial I/f for the BBS. still gonna use desqview if I can get everything play nice.
oh, the memories!
- Comment on Microsoft revives aggressive Windows 11 upgrade campaign with intrusive popups for Windows 10 users 4 months ago:
Brilliant! TPM as a crappy OS ad blocker… but this is still the worst timeline.
- Comment on Met rejects calls to investigate Prince Andrew after release of Epstein files 5 months ago:
Buckingham Palace declined to comment on the documents as Andrew is no longer a working royal.
I would posit that all of them are pretty broken.