:clap:
", "time": "2024-03-22T05:00:25Z"}, {"author": "Martin D\u00fcrst", "text": "Strange that I can select an emoji in meetecho, but meetecho then just displays :clap:.
", "time": "2024-03-22T05:01:05Z"}, {"author": "Martin D\u00fcrst", "text": "I read it.
", "time": "2024-03-22T05:08:25Z"}, {"author": "Martin D\u00fcrst", "text": "please come to the mic
", "time": "2024-03-22T05:09:28Z"}, {"author": "Jonathan Lennox", "text": "Meetecho there is a software update dialog on the screen in the room
", "time": "2024-03-22T05:10:17Z"}, {"author": "Pete Resnick", "text": "@meetecho: We have a software update dialog on the left hand screen.
", "time": "2024-03-22T05:10:23Z"}, {"author": "Lorenzo Miniero", "text": "You should be able to tap the \"cancel\" option
", "time": "2024-03-22T05:10:55Z"}, {"author": "Lorenzo Miniero", "text": "The touchpad is currently disabled instead
", "time": "2024-03-22T05:11:07Z"}, {"author": "Lorenzo Miniero", "text": "It's the laptop on the chairs desk
", "time": "2024-03-22T05:11:22Z"}, {"author": "Lorenzo Miniero", "text": "Tapping directly on the screen I meant
", "time": "2024-03-22T05:11:55Z"}, {"author": "Lorenzo Miniero", "text": "If it's not working please do let us know
", "time": "2024-03-22T05:12:02Z"}, {"author": "Pete Resnick", "text": "Done. Thx.
", "time": "2024-03-22T05:12:24Z"}, {"author": "Lorenzo Miniero", "text": "Ack!
", "time": "2024-03-22T05:12:29Z"}, {"author": "Darrel Miller", "text": "I have
", "time": "2024-03-22T05:15:18Z"}, {"author": "John Klensin", "text": "fwiw +1 to mark
", "time": "2024-03-22T05:17:51Z"}, {"author": "Jonathan Lennox", "text": "Apparently to speak at the mic your name must begin with M?
", "time": "2024-03-22T05:18:34Z"}, {"author": "Pete Resnick", "text": "I am feeling rather half-empty.
", "time": "2024-03-22T05:19:44Z"}, {"author": "Martin D\u00fcrst", "text": "Sorry about that, Pete.
", "time": "2024-03-22T05:20:08Z"}, {"author": "Mark Nottingham", "text": "https://tess.oconnor.cx/2023/09/polyglots-and-interoperability
", "time": "2024-03-22T05:21:58Z"}, {"author": "Pete Resnick", "text": "Top-level MIME types and Content-Transfer-Encodings were supposed to be the place that described the generic properties of the MIME type. Hiding them in a multi-level MIME subtype has always given me the willies. But we are where we are. \ud83e\udee4
", "time": "2024-03-22T05:23:07Z"}, {"author": "Martin Thomson", "text": "Was that +json+ld ?
", "time": "2024-03-22T05:23:24Z"}, {"author": "Pete Resnick", "text": "Agree that Manu and folks have been put in an untenable and unfair position.
", "time": "2024-03-22T05:23:34Z"}, {"author": "Martin Thomson", "text": "I have basically reached the point where +suffixes are more hazard than value.
", "time": "2024-03-22T05:25:01Z"}, {"author": "Martin Thomson", "text": "This isn't about \"bring me a rock\".
", "time": "2024-03-22T05:27:48Z"}, {"author": "Pete Resnick", "text": "Who is the expert now?
", "time": "2024-03-22T05:33:14Z"}, {"author": "Martin Thomson", "text": "The core problem here is that we don't know how to judge whether a suffix definition is good or not.
", "time": "2024-03-22T05:34:00Z"}, {"author": "Pete Resnick", "text": "I have not been in this discussion, so I don't understand the use case, but surely someone can advise them what to do in their grandfathered use case, no?
", "time": "2024-03-22T05:34:57Z"}, {"author": "Martin Thomson", "text": "Personally, I am increasingly of the view that suffixes are not good, period. But I'm happy to listen to arguments in favour of this.
", "time": "2024-03-22T05:35:00Z"}, {"author": "Alexey Melnikov", "text": "I don't understand why grandfathering is bad. if there is a note saying \"don't do that again\", but allowing existing registrations, surely this would help?
", "time": "2024-03-22T05:35:44Z"}, {"author": "Martin Thomson", "text": "One conclusion here could be that we tell people that the + is not special in any way.
", "time": "2024-03-22T05:35:50Z"}, {"author": "Pete Resnick", "text": "@Manu Sporny Totally agree that we need to give you an answer and then we can get our mess together.
", "time": "2024-03-22T05:36:01Z"}, {"author": "Murray Kucherawy", "text": "@Martin: I'm starting to like this idea.
", "time": "2024-03-22T05:40:19Z"}, {"author": "Murray Kucherawy", "text": "Is that not fully backward compatible with all the registrations that do have them?
", "time": "2024-03-22T05:40:37Z"}, {"author": "Martin Thomson", "text": "It is indeed fully compatible.
", "time": "2024-03-22T05:41:04Z"}, {"author": "Murray Kucherawy", "text": "What if the suffix registry didn't exist? What would be lost?
", "time": "2024-03-22T05:41:07Z"}, {"author": "Murray Kucherawy", "text": "Other than this WG. :)
", "time": "2024-03-22T05:41:15Z"}, {"author": "Murray Kucherawy", "text": "If a thing is JSON-encoded by definition, what benefit does tagging it \"+json\" confer?
", "time": "2024-03-22T05:42:31Z"}, {"author": "Mark Nottingham", "text": "You could also spell it so that the 'primary' (right-most) suffix defines whether the preceding suffixes have semantis
", "time": "2024-03-22T05:42:44Z"}, {"author": "Jonathan Lennox", "text": "Is anything actually using the suffices to automatically feed media to generic parsers, as opposed to humans doing it?
", "time": "2024-03-22T05:43:50Z"}, {"author": "Murray Kucherawy", "text": "Oh come on, we do it all the time.
", "time": "2024-03-22T05:43:56Z"}, {"author": "Darrel Miller", "text": "@murray Historically +json made it likely that a browser would render it as JSON text instead of making you download the file.
", "time": "2024-03-22T05:44:05Z"}, {"author": "Martin Thomson", "text": "Suffixes need to justify their existence. We don't need to justify an objection to them.
", "time": "2024-03-22T05:44:20Z"}, {"author": "Mark Nottingham", "text": "exactly
", "time": "2024-03-22T05:44:37Z"}, {"author": "Mark Nottingham", "text": "getting bad advice is not a reason to change how media types work
", "time": "2024-03-22T05:45:01Z"}, {"author": "Martin Thomson", "text": "it's not really clear that it is bad advice, but we're all still learning
", "time": "2024-03-22T05:45:28Z"}, {"author": "Murray Kucherawy", "text": "\"advice\"?
", "time": "2024-03-22T05:46:39Z"}, {"author": "Martin Thomson", "text": "I don't think that anyway is suggesting that \"+\" == \"-\" in the same way that \"A\" == \"a\".
", "time": "2024-03-22T05:46:45Z"}, {"author": "Pete Resnick", "text": "@Manu Sporny Do you think that dashes are now not possible if we (annoyingly) said that we decided that those are the way to go?
", "time": "2024-03-22T05:46:45Z"}, {"author": "Martin Thomson", "text": "...just that \"+\" does not carry any special meaning for processors.
", "time": "2024-03-22T05:47:11Z"}, {"author": "Murray Kucherawy", "text": "@Darrel: Ah.
", "time": "2024-03-22T05:47:15Z"}, {"author": "Mark Nottingham", "text": "That's what I was asking, Pete - it's a good question.
", "time": "2024-03-22T05:47:17Z"}, {"author": "Pete Resnick", "text": "If we write a message saying, \"Nostra culpa, nostra culpa, nostra maxima culpa. We should have told you that dashes were fine. We were idiots. Forgive us, use dashes, and we promise to stop bothering you\", would that do it?
", "time": "2024-03-22T05:48:28Z"}, {"author": "Murray Kucherawy", "text": "If \"+\" is no longer special, are suffixes moot?
", "time": "2024-03-22T05:49:37Z"}, {"author": "Murray Kucherawy", "text": "e.g., delete the registry?
", "time": "2024-03-22T05:49:42Z"}, {"author": "Martin Thomson", "text": "Murray: it would mean that the registry would go away.
", "time": "2024-03-22T05:49:59Z"}, {"author": "Murray Kucherawy", "text": "Cool.
", "time": "2024-03-22T05:50:19Z"}, {"author": "Murray Kucherawy", "text": "@Darrel: How bad would it be to lose that?
", "time": "2024-03-22T05:50:58Z"}, {"author": "Darrel Miller", "text": "@murray I think we could say + has no special meaning and browsers would still do the same thing.
", "time": "2024-03-22T05:51:55Z"}, {"author": "Jonathan Lennox", "text": "The ability to pretty-print otherwise unknown types seems at least somewhat valuable but I don't know how to formalize that
", "time": "2024-03-22T05:52:16Z"}, {"author": "Murray Kucherawy", "text": "They don't have to change anything, right? Just the suffix loses its special meaning; the media type itself still works as before.
", "time": "2024-03-22T05:52:22Z"}, {"author": "Darrel Miller", "text": "I think the fact that we have +xml and +zip we have already made it almost impossible for suffixes to have single meaning.
", "time": "2024-03-22T05:53:31Z"}, {"author": "Darrel Miller", "text": "@murray Right.
", "time": "2024-03-22T05:53:43Z"}, {"author": "Jonathan Lennox", "text": "+zip I think I understand (jar would have had it had suffices existed) but I don't think +gzip makes sense
", "time": "2024-03-22T05:55:55Z"}, {"author": "Darrel Miller", "text": "I could support saying + has no special meaning.
", "time": "2024-03-22T05:56:37Z"}, {"author": "Murray Kucherawy", "text": "+1
", "time": "2024-03-22T05:57:20Z"}, {"author": "Martin Thomson", "text": "I think that +zip makes even less sense.
", "time": "2024-03-22T05:57:21Z"}, {"author": "Darrel Miller", "text": "I think registering the +zip was the mis-step because it doesn't really describe some generic semantics, it describes some incremental processing step.
", "time": "2024-03-22T05:59:10Z"}, {"author": "Hans-J\u00f6rg Happel", "text": "+1
", "time": "2024-03-22T05:59:30Z"}, {"author": "Darrel Miller", "text": "We can't hear you.
", "time": "2024-03-22T05:59:56Z"}, {"author": "Martin Thomson", "text": "zip is a container type, which has the potential to have media types for each of its content objects
", "time": "2024-03-22T06:01:09Z"}, {"author": "Pete Resnick", "text": "(IMO) Feel free to preface with \"The IETF people know they were idiots.\"
", "time": "2024-03-22T06:01:21Z"}, {"author": "Martin Thomson", "text": "so +zip makes no sense at all
", "time": "2024-03-22T06:01:24Z"}, {"author": "Murray Kucherawy", "text": "Interesting.
", "time": "2024-03-22T06:01:37Z"}, {"author": "Darrel Miller", "text": "Can anyone identify what we value we would lose if we remove the special meaning for + ?
", "time": "2024-03-22T06:01:44Z"}, {"author": "Murray Kucherawy", "text": "Like a multipart/mixed. Never thought of it that way.
", "time": "2024-03-22T06:01:46Z"}, {"author": "Martin D\u00fcrst", "text": "\"What should we do about suffixes?\" Yes!
", "time": "2024-03-22T06:01:56Z"}, {"author": "Martin Thomson", "text": "right
", "time": "2024-03-22T06:02:00Z"}, {"author": "Martin D\u00fcrst", "text": "Now here's something where I really don't know what that means!
", "time": "2024-03-22T06:02:13Z"}, {"author": "Martin Thomson", "text": "As for liaison, I'm happy to facilitate, but I would prefer to do something like put Harald in touch with the right people so you can have a direct conversation. No intermediaries.
", "time": "2024-03-22T06:02:24Z"}, {"author": "Murray Kucherawy", "text": "\"RTP media type\" is defined in 3550
", "time": "2024-03-22T06:07:57Z"}, {"author": "Martin Thomson", "text": "From a brief read of RFC 4855, it looks like it is saying that RTP media types are registered as normal media types. Somehow that turned into a separate registry, but I don't see that in the RFC.
", "time": "2024-03-22T06:08:45Z"}, {"author": "Murray Kucherawy", "text": "And I'm guessing Amanda et al don't have any history?
", "time": "2024-03-22T06:09:07Z"}, {"author": "Pete Resnick", "text": "@Darrel Miller (Just seeing your question) I think it's more of a legacy/backwards-compat problem to get rid of the meaning of \"+\".
", "time": "2024-03-22T06:09:13Z"}, {"author": "Martin D\u00fcrst", "text": "Thanks Harald!
", "time": "2024-03-22T06:09:50Z"}, {"author": "Darrel Miller", "text": "Thanks Harald.
", "time": "2024-03-22T06:10:01Z"}]