Websites prove their identity via certificates, which are valid for a set time period. The certificate for www.app.gov.pt expired on 3/11/2025.
Websites prove their identity via certificates, which are valid for a set time period. The certificate for www.app.gov.pt expired on 3/11/2025.
Websites prove their identity via certificates, which are valid for a set time period. The certificate for www.app.gov.pt expired on 3/11/2025.
i18n-puzzles.com has been a blast, but I don't like having to think about puzzles on weekends. Like with exercise, doing it every day without rest doesn't sound healthy.
I'd rater have a weekly challenge, at most three.
Jokes aside, I like IaaS as a middle ground. There are IaaS hosters who allow you to spin up VMs as you wish and connect them in a network as you wish. You get direct access to all those Linux boxes and to a layer 2 network, so you can do all the fun networking stuff like BGP, VRRP, IPSec/Wireguard, whatever. And you never have to worry about failing disks, server racks getting full, cable management, all that. 😅
I’m confident that we will always need people who do bare-bones or “low-level” stuff instead of just click some Cloud service. I *guess* that smaller companies don’t use Cloud services very often (because it’s way too expensive for them).
Jokes aside, I like IaaS as a middle ground. There are IaaS hosters who allow you to spin up VMs as you wish and connect them in a network as you wish. You get direct access to all those Linux boxes and to a layer 2 network, so you can do all the fun networking stuff like BGP, VRRP, IPSec/Wireguard, whatever. And you never have to worry about failing disks, server racks getting full, cable management, all that. 😅
I’m confident that we will always need people who do bare-bones or “low-level” stuff instead of just click some Cloud service. I *guess* that smaller companies don’t use Cloud services very often (because it’s way too expensive for them).
I cast a test vote. Did it work? :-)
I cast a test vote. Did it work? :-)
#running #treadmill
#running #treadmill
#running #treadmill
https://yewtu.be/watch?v=XoooX3OVGoI
https://yewtu.be/watch?v=XoooX3OVGoI
https://lwn.net/Articles/989272/
In my case, it was mpd which triggered this:
https://github.com/MusicPlayerDaemon/MPD/issues/2241
mpd doesn’t actually do anything, it just sits there and waits for events. To my understanding, this is similar to something blocking on
read(). I’m not quite sure yet if displaying this as I/O wait (or “PSI some io”) is intentional or not – but it sure is confusing.
https://lwn.net/Articles/989272/
In my case, it was mpd which triggered this:
https://github.com/MusicPlayerDaemon/MPD/issues/2241
mpd doesn’t actually do anything, it just sits there and waits for events. To my understanding, this is similar to something blocking on
read(). I’m not quite sure yet if displaying this as I/O wait (or “PSI some io”) is intentional or not – but it sure is confusing.
https://github.com/TecharoHQ/anubis/issues/16
https://github.com/TecharoHQ/anubis/issues/16
The rabbit hole is an interesting concept.
Chapter 11 with Alan:
I knew of twtxt in Gemini Antenna, so at least the 2017 spec might work on that protocol. I think the main issue with extensions is that they weren't designed with many URLs and protocols in mind.
Also I have to admit that the Gemini community significantly reduced in the last few years. I don't know how worth it is to add support for Gemini now.
https://eapl.me/rfc0001/
Help me to play with it a bit and report any vulnerability or bug. Also any idea is welcome.
Also, could you elaborate on how you envision migrating with a script? You mean that the client of the file owner could massively update URLs in old twts ?
$ curl -sI 'http://movq.de/v/8684c7d264/.html%2Dindex%2Dthumb%2Dgimp11%2D1.png.jpg'
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 2615
Content-Type: image/jpeg
Date: Wed, 19 Mar 2025 19:53:17 GMT
Last-Modified: Wed, 19 Mar 2025 17:34:08 GMT
Server: OpenBSD httpd
$ curl -sI 'https://movq.de/v/8684c7d264/gimp11%2D1.png'
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 131798
Content-Type: image/png
Date: Wed, 19 Mar 2025 19:53:19 GMT
Last-Modified: Wed, 19 Mar 2025 17:18:07 GMT
Server: OpenBSD httpd
$ telnet movq.de 80
Trying 185.162.249.140...
Connected to movq.de.
Escape character is '^]'.
HEAD /v/8684c7d264/.html%2Dindex%2Dthumb%2Dgimp11%2D1.png.jpg HTTP/1.1
Host: movq.de
Connection: close
HTTP/1.1 200 OK
Connection: close
Content-Length: 2615
Content-Type: image/jpeg
Date: Wed, 19 Mar 2025 19:53:31 GMT
Last-Modified: Wed, 19 Mar 2025 17:34:08 GMT
Server: OpenBSD httpd
Connection closed by foreign host.
$
$ curl -sI 'http://movq.de/v/8684c7d264/.html%2Dindex%2Dthumb%2Dgimp11%2D1.png.jpg'
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 2615
Content-Type: image/jpeg
Date: Wed, 19 Mar 2025 19:53:17 GMT
Last-Modified: Wed, 19 Mar 2025 17:34:08 GMT
Server: OpenBSD httpd
$ curl -sI 'https://movq.de/v/8684c7d264/gimp11%2D1.png'
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 131798
Content-Type: image/png
Date: Wed, 19 Mar 2025 19:53:19 GMT
Last-Modified: Wed, 19 Mar 2025 17:18:07 GMT
Server: OpenBSD httpd
$ telnet movq.de 80
Trying 185.162.249.140...
Connected to movq.de.
Escape character is '^]'.
HEAD /v/8684c7d264/.html%2Dindex%2Dthumb%2Dgimp11%2D1.png.jpg HTTP/1.1
Host: movq.de
Connection: close
HTTP/1.1 200 OK
Connection: close
Content-Length: 2615
Content-Type: image/jpeg
Date: Wed, 19 Mar 2025 19:53:31 GMT
Last-Modified: Wed, 19 Mar 2025 17:34:08 GMT
Server: OpenBSD httpd
Connection closed by foreign host.
$
ptxsca), which you seem to be using to reply to @movq is not the right one.
#running #treadmill
#running #treadmill
#running #treadmill
Regarding the hash, you're right. I'll have to investigate what's going on. I'm having a hard time getting the hash generation to work properly.
Regarding the hash, you're right. I'll have to investigate what's going on. I'm having a hard time getting the hash generation to work properly.
What does look strange, though, is that your client came up with the hash
pqsmcka, while it should have been te5quba. 🤔
What does look strange, though, is that your client came up with the hash
pqsmcka, while it should have been te5quba. 🤔
- Is active?
- Extensions compatibility
- Language
- Multiaccount.
- Mutiuser
And so on...
- Is active?
- Extensions compatibility
- Language
- Multiaccount.
- Mutiuser
And so on...
1. It is only long for humans. Clients can only leave a hyperlink.
2. The nickname is just a decoration, only the date that acts as the id and the URL matter. The nick is used for humans reading the feed.
3. It can be migrated with a script, if the feed exists.
1. It is only long for humans. Clients can only leave a hyperlink.
2. The nickname is just a decoration, only the date that acts as the id and the URL matter. The nick is used for humans reading the feed.
3. It can be migrated with a script, if the feed exists.
https://docs.google.com/spreadsheets/d/1KOUqJ2rNl_jZ4KBVTsR-4QmG1zAdKNo7QXJS1uogQVo/edit?gid=0#gid=0
Feel free to propose another collaborative platform (for those without a G account), and also share your comments and analysis in the spreadsheet or in Gitea.
[](https://movq.de/v/8684c7d264/gimp11%2D1.png)
[](https://movq.de/v/8684c7d264/gimp11%2D2.png)
[](https://movq.de/v/8684c7d264/gimp11%2D3.png)
[](https://movq.de/v/8684c7d264/gimp11%2D4.png)
[](https://movq.de/v/8684c7d264/gimp11%2D1.png)
[](https://movq.de/v/8684c7d264/gimp11%2D2.png)
[](https://movq.de/v/8684c7d264/gimp11%2D3.png)
[](https://movq.de/v/8684c7d264/gimp11%2D4.png)
At the 26th of February Mozilla presented a few changes - Terms of Use for Firefox - as a done deal, asking for feedback only about the already decided move. Feedback came, and two days later February 28th, they decided to make cosmetic changes to "provide clarity", changing nothing. At the same time, they were again open for a new round of post-fact comments, only this time they didn't even bother to try to answer to any of those. Four pages later, and the flux of comments died down - there's no argument to be had when the other side does not show any signs of listeinng. The last comment there (at this moment) is from the 16th of March.
Twenty days, it was all it took for us to absorb the shock, accept the bad news, consider it 'old news' now. Mozilla made the change they wanted anyway, and #Firefox users will just suffer the consequences.
The last comments thread: https://connect.mozilla.org/t5/discussions/an-update-on-our-terms-of-use/m-p/88320/page/4