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
Docker Best Practices: Using Tags and Labels to Manage Docker Image Sprawl
Learn best practices for using tags and labels to manage image sprawl in Docker container workflows. ⌘ Read more
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
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.
↳
In-reply-to
»
(#2qn6iaa) @prologic Some criticisms and a possible alternative direction:
⤋ Read More
The 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:
(reply:sorenpeter@darch.dk,2024-09-15T12:06:27Z)
(in-reply-to:darch.dk/twtxt.txt,2024-09-15T12:06:27Z)
(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?
↳
In-reply-to
»
(#2qn6iaa) @prologic Some criticisms and a possible alternative direction:
⤋ Read More
HTTPS is supposed to do [verification] anyway.
TLS provides verification that nobody is tampering with or snooping on your connection to a server. It doesn’t, for example, verify that a file downloaded from server A is from the same entity as the one from server B.
I was confused by this response for a while, but now I think I understand what you’re getting at. You are pointing out that with signed feeds, I can verify the authenticity of a feed without accessing the original server, whereas with HTTPS I can’t verify a feed unless I download it myself from the origin server. Is that right?
I.e. if the HTTPS origin server is online and I don’t mind taking the time and bandwidth to contact it, then perhaps signed feeds offer no advantage, but if the origin server might not be online, or I want to download a big archive of lots of feeds at once without contacting each server individually, then I need signed feeds.
feed locations [being] URLs gives some flexibility
It does give flexibility, but perhaps we should have made them URIs instead for even more flexibility. Then, you could use a tag URI,
urn:uuid:*, or a regular old URL if you wanted to. The spec seems to indicate that theurltag should be a working URL that clients can use to find a copy of the feed, optionally at multiple locations. I’m not very familiar with IP{F,N}S but if it ensures you own an identifier forever and that identifier points to a current copy of your feed, it could be a great way to fix it on an individual basis without breaking any specs :)
I’m also not very familiar with IPFS or IPNS.
I haven’t been following the other twts about signatures carefully. I just hope whatever you smart people come up with will be backwards-compatible so it still works if I’m too lazy to change how I publish my feed :-)
↳
In-reply-to
»
@movq Is there a good way to get jenny to do a one-off fetch of a feed, for when you want to fill in missing parts of a thread? I just added @slashdot to my private follow file just because @prologic keeps responding to the feed :-P and I want to know what he's commenting on even though I don't want to see every new slashdot twt.
⤋ Read More
@prologic@twtxt.net How does yarn.social’s API fix the problem of centralization? I still need to know whose API to use.
Say I see a twt beginning (#hash) and I want to look up the start of the thread. Is the idea that if that twt is hosted by a a yarn.social pod, it is likely to know the thread start, so I should query that particular pod for the hash? But what if no yarn.social pods are involved?
The community seems small enough that a registry server should be able to keep up, and I can have a couple of others as backups. Or I could crawl the list of feeds followed by whoever emitted the twt that prompted my query.
I have successfully used registry servers a little bit, e.g. to find a feed that mentioned a tag I was interested in. Was even thinking of making my own, if I get bored of my too many other projects :-)
This $18,000 bottle of Australian wine sold out before it was released
Ultra-premium wine collectors have snapped up a new commemorative bottle of Penfolds, but what is driving the hefty high price tags for luxury drops? ⌘ Read more
Lessons from CrowdStrike’s Buggy Update: The Critical Importance of Robust Release Processes
Community post by Andrés Vega, CNCF TAG Security Recent events involving CrowdStrike’s Falcon security software have underscored a critical lesson across the industry : the importance of having a robust, secure release process. This incident serves as a… ⌘ Read more
A new App Development WG has now been launched!
TAG post from TAG App Delivery Calling all developers! We’re excited to announce the launch of the new App Development Working Group within the TAG App Delivery. This group is dedicated to bridging the gap between developers and… ⌘ Read more
↳
In-reply-to
»
Yeah sorry just realised, but just checked again and the referrer is the same (
⤋ Read More
/post) on either the POST or the GET 🤔
@prologic@twtxt.net Sorry, my messages don’t get included in the current convo unless I tag you. Guess something gets lossed in translation with this weird posting issue. ANYWAY, it is rather perplexing. Clearly only an issue on my Pod, but what could the source of it be 🤔
Skal du på #bornhack i år?
Ja, selvfølgelig!
Næh- jeg er helt vildt kedelig.
Øh, hvad er Bornhack? ⌘ Read more
Hey remember this thing I made?
I still think it’s pretty cool.
Erlang Solutions: Instant Scalability with MongooseIM and CETS
The main feature of the recently released MongooseIM 6.2.1 is the improved CETS in-memory storage backend which makes it much easier to scale up.
It is difficult to predict how much traffic your XMPP server will need to handle. Are you going to have thousands or millions of connected users? … ⌘ Read more
Totalt problemfri idé: omvendt pension.
1. Tag et kæmpe lån som 20-årig.
2. Hold fri indtil du fylder 30.
3. Arbejd indtil du dør for at betale lånet af.
Så har man fri mens man stadig er ung og rask og frisk og færre af ens venner er døde. ⌘ Read more
Hey #Fælleshjerne - Hvor fås Københavns bedste croissanter?
(Bonuspoint hvis det ligger tæt på cykelturen fra Nørrebros Runddel til Kongens Nytorv) ⌘ Read more
Even though the bridges that #beeper use are AGPL licensed, the beeper client is proprietary software 😭
This is big sad.
They almost had it.
It is also kind of limited on google-free android phones, since the QR code scanner for device verification key-signing depends on a google play services API (which microg doesn’t implement). This means that you can’t share message history between your google-free android and the beeper desktop client. ⌘ Read more
it’s a chat app that bridges to a bunch of networks seamlessly.
they bridge to signal, discord, whatsapp, fb messenger, instagram, linkedin, telegram, slack, sms, google chat, and IRC
it’s a #Matrix client, so you just get a @username:beeper.com matrix user, which works on matrix too.
the bridges are all open source. they hired tulir, who does the mautrix bridge stuff a couple of years ago.
beeper has people working on the open-source matr … ⌘ Read more
ok so #beeper is extremely cool, and I recommend that you try it out.
Added support for #tag clouds and #search to timeline. Based on code from @dfaria.eu@dfaria.eu🙏
Live at: http://darch.dk/timeline/?profile=https://darch.dk/twtxt.txt
[Updated] Free Mobile-Friendly Layout Wizard
Updated: The
Free Mobile-Friendly Layout Wizard
has been updated. It will now place the meta charset tag before the title in the head section (so that it will
be in the first 1 KB of your page even if you have a long title). In addition, if you select HTML5 as the output type,
the shorter meta charset tag will be used. ⌘ Read more
Så kom der en ny PB single igen: 13.11 sekunder #speedcubing ⌘ Read more
PSA: hvis du har en underlig ikke-rooted android (feks en google-fri android eller lineage OS) og gerne vil have det nye #mobilepay til at virke, kan du bruge det her workaround til en bug i deres elendige root-detection software
https://github.com/scottyab/rootbeer/issues/181#issuecomment-1735171558 ⌘ Read more
Gaining kernel code execution on an MTE-enabled Pixel 8
In this post, I’ll look at CVE-2023-6241, a vulnerability in the Arm Mali GPU that allows a malicious app to gain arbitrary kernel code execution and root on an Android phone. I’ll show how this vulnerability can be exploited even when Memory Tagging Extension (MTE), a powerful mitigation, is enabled on the device.
The post [Gaining kernel code execution on an MTE-enabled Pixel 8](https://github.blog/2024-03-18-gaining-kerne … ⌘ Read more
Nårh ja og anbefaling:
Tag lige og hør Mount Eerie’s album Lost Wisdom.
Det gør noget ved mit indre liv.
Er Phil Elverum århundredets
sangskriver? Ingen ved det. Men det rammer nogle resonansfrekvenser i mig. ⌘ Read more
Gad vide om nogen af de store næsten-gatekeeper tjenester kommer til at implementere interop med WhatsApp og Messenger efter #DMA
Kunne iMessage eller Discord finde på det? Det ville nok styrke deres reach, men også svække deres monopolagtige netværkseffekt 🥴 ⌘ Read more
@lyse@lyse.isobeef.org its a hierarchy key value format. I designed it for the network peering tools i use.. I can grant access to different parts of the tree to other users.. kinda like directory permissions. a basic example of the format is:
@namespace
# multi
# line
# comment
root :value
# example space comment
@namespace.name space-tag
# attribute comments
attribute attr-tag :value for attribute
# attribute with multiple
# lines of values
foo :bar
:bin
:baz
repeated :value1
repeated :value2
each @ starts the definition of a namespace kinda like [name] in ini format. It can have comments that show up before. then each attribute is key :value and can have their own # comment lines.
Values can be multi line.. and also repeated..
the namespaces and values can also have little meta data tags added to them.
the service can define webhooks/mqtt topics to be notified when the configs are updated. That way it can deploy the changes out when they are updated.
So the six #DMA gatekeepers are Alphabet, Amazon, Apple, ByteDance, Meta, and Microsoft.
Whats the FAANG / GAFAM equivalent acronym for those six?
MAMBAA?
AMAMBA?
BAAAMM? ⌘ Read more
yay.
satte mig ned. lavede en ao12. fik 19.5
Er jeg sub-20 nu?
Næste mål: sub-20 gennemsnit af 100.