Did we have web forums back then? I know Usenet was a thing.
5,638 karma · joined April 24, 2009
"Let's go with a word that looks a bit like 'Insolvent' when you glace at it in a hurry."
It what I now realise was a bad idea, I was writing code by web server code using C with CGI. I was supposed to use Perl, but I didn't want to spend time learning that as I already knew C.
Yes, I know all Turing machines are equivalent so it shouldn't be surprising it was possible but still, cool.
1. Emails from everyone (including you) go into the spam folder. 2. I identify senders I do actually want to receive messages from.
The industry isn't doing item 2 very well, but default-deny for new senders is exactly what I want from a mailbox service.
I saw a fridge that had an app so you could control it from anywhere.
My requirements for a fridge are remarkably simple, to the point the only practical use I could think of an app was alarm that I'd left the door open or something.
(If this particular app did have a door-open alarm, it wasn't on the list of features. It did say you could adjust the temperature from your office. A location I'm often worrying about the fridge.)
That's fantastic. Anyone developing ATOM/RSS, please use this mechanism.
(I'm looking at you, podcast with over 100 episodes.)
Am I going to have to download a file with references to all one million items again?
If the answer is to have a separate feed with only the most recent n items, I'm afraid that's not going to work unless there's additional details. There might have been n+1 items turn up since the last time I polled. Also, someone else might want to start handling those one million records from the start and we should be able to co-ordinate by having a common canonical URL.
(I'd also mention pull-vs-push, but that's a thread elsewhere in these comments.)
If we could agree that ATOM is RSS 2 (or whatever MAX(version)+1 is) that'd be great.
As this is still a public draft and not an established standard, I hope discussion will bring a consensus that one way of responding is better and a future draft will only specify that way.
If I may rewrite your scenario to check I understand it...
An attacker sets themselves up as an Initiator and registers https://evil.example/TimeOut/ as their URL to receive the TokenIssue POST requests. The attacker then makes a TokenCall request to which the Issuer responds by making the TokenIssue POST request to the malicious "time out" endpoint. As this never responds, that initial connection is kept open.
That's a scam, right?
"I have encrypted your files. Send (amount) and I'll decrypt them for you."
Not a scam?
"Bob died. Ten years ago."
This was going to be part of a larger project implementing libraries for all the email protocols, but I lost enthusiasm for it when I realised how broken email itself is in this day and age.
Nitpick, but Watt-Hours is energy, not power.
Why yes, I am very clever. Thank you for noticing.
"Re-joining the EU would give the UK all the benefits of EU membership as well as all the benefits of Brexit too."
Oh dear.