Searching We Love Privacy Club

Twts matching #tag
Sort by: Newest, Oldest, Most Relevant
cncf
feeds.twtxt.net
 (1y ago)

TAG Environmental Sustainability Week is here: a global call for green tech
By TAG Environmental Sustainability Get ready for the CNCF Cloud Native Sustainability Week 2024, which will take place from October 7th to 13th, 2024. This global event, organized by the CNCF Technical Advisory Group for Environmental Sustainability (TAG… ⌘ Read more

⤋ Read More
cncf
feeds.twtxt.net
 (1y ago)

Achieving collaboration and impact for end users: introducing the CNCF’s End User Technical Advisory Board (TAB), its mission and initiatives
End user post by Alolita Sharma, Engineering Leader at Apple, CNCF Board & EndUser TAB, OpenTelemetry GC, CNCF Observability TAG Co-Chair The CNCF End User Technical Advisory Group (TAB) was formally announced at KubeCon + CloudNativeCon North America… ⌘ Read more

⤋ Read More
quark
ferengi.one
 (1y ago)
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

More:

Subject: The [tag URI scheme](https://en.wikipedia.org/wiki/Tag_URI_scheme) looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be
        somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick? Instead of using `tag:` as the prefix/protocol, it would more it clear
        what we are talking about by using `in-reply-to:` (https://indieweb.org/in-reply-to) or `replyto:` similar to `mailto:` 1. `(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)' 2.
        `(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)' 2. `(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)' I know it's longer that 7-11 characters, but it's self-explaining when looking at the
        twtxt.txt in the raw, and the cases above can all be caught with this regex: `\([\w-]*reply[\w-]*\:` Is this something that would work?

Subject: The [tag URI scheme](https://en.wikipedia.org/wiki/Tag_URI_scheme) looks interesting. I like that it human read- and writable. And since we already got the timestamp in the twtxt.txt it would be
        somewhat trivial to parse. But there are still the issue with what the name/id should be... Maybe it doesn't have to bee that stick? Instead of using `tag:` as the prefix/protocol, it would more it clear
        what we are talking about by using `in-reply-to:` (https://indieweb.org/in-reply-to) or `replyto:` similar to `mailto:` 1. `(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)` 2.
        `(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)` 3. `(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)` I know it's longer that 7-11 characters, but it's self-explaining when looking at the
        twtxt.txt in the raw, and the cases above can all be caught with this regex: `\([\w-]*reply[\w-]*\:` Is this something that would work?

Notice the difference? Soren edited, and broke everything.

⤋ Read More