Searching txt.sour.is

Twts matching #quotes
Sort by: Newest, Oldest, Most Relevant

[$] LWN.net Weekly Edition for October 9, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Kernel Rust features; systemd v258, part 2; Cauldron kernel hackers; BPF for GNU tools; 6.18 merge window, part 1; Lifetime-end pointer zapping; Robot Operating System.

  • Briefs: OpenSSH 10.1; Firefox profiles; Python 3.14; U-Boot v2025.10; FSF presidency; Quotes; …

  • Announcements: Newsletters, conferences, security upda … ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for October 2, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Fedora and AI; Linting kernel Rust; openSUSE Leap 16; mmap() file operation; 6.17 statistics; dirlock.

  • Briefs: Bcachefs removal; Alpine /usr merge; F-Droid; Fedora AI policy; OpenSUSE Leap 16; PostgreSQL 18; Radicle 1.5.0; Quotes; …

  • Announcements: Newsletters, conferences, security updates, patches, and more. ⌘ Read more

⤋ Read More
In-reply-to » @zvava I never used any of the social media platforms, that's why I'm probably ignorant.

@lyse@lyse.isobeef.org retwts are a discovery feature! on federated platforms with no algorithm where you only ever see posts from accounts you explicitly follow, the element of “hey look at this!” helps users to find other accounts they might like organically

i agree quoting and replying forum-style is generally a much better way of doing things even though im a heathen and i revel in the dark patterns inspired by quote posts but when you have nothing to add and you just want to share a twt with your followers it’d be good to have a standardized way of linking to twt

⤋ Read More
In-reply-to » at first i dismissed the idea of likes on twtxt as not sensible...like at all — then i considered they could just be published in a metadata field (though that field could get really unruly after a while)

@zvava@twtxt.net I never used any of the social media platforms, that’s why I’m probably ignorant.

I don’t understand the concept of a retwt. Just quote the (relevant) parts from whereever and comment on that. Or post a link instead of a quote. Sounds simple enough. :-) That’s also has the benefit that it works with every source, no matter what. Since it’s called retwt, I’d imagine this to only work (well) with whatever messages the system itself offers. But I could be wrong. What would be the benefit of having a dedicated message type or structure for “hey, look at that” messages in your opinion?

Hmm, what’s a content warning?

⤋ Read More

at first i dismissed the idea of likes on twtxt as not sensible…like at all — then i considered they could just be published in a metadata field (though that field could get really unruly after a while)

retwts are plausible, as “RE: https://example.com/twtxt.txt#abcdefg”, the hash could even be the original timestamp from the feed to make it human readable/writable, though im extremely wary of clogging up timelines

i thought quote twts could be done extremely sensibly, by interpreting a mention+hash at the end of the twt differently to when placed at the beginning — but the twt subject extension requires it be at the beginning, so the clean fallback to a normal reply i originally imagined is out of the question — it could still be possible (reusing the retwt format, just like twitter!) but i’m not convinced it’s worth it at that point

is any of this in the spirit of twtxt? no, not in the slightest, lmao

⤋ Read More
In-reply-to » This extension was turned off because it is no longer supported

Looks like here’s something wrong with Markdown parsing. 🤔 The original twt looks like this:

>This extension was turned off because it is no longer supported

Thanks Google.
This browser was uninstalled because it absolutely sucks!

So only the first line should be a quote.

⤋ Read More

** Om nom nom LLMs, in which I respond to Simon Willison’s analogy **
I am hesitant to wade into the tumultuous waters that are the discourse around generative AI and LLMs, but this morning I came across a thing that so thoroughly melted my brain I feel uncontrollably compelled to respond.

This morning, at evidently 4:10 AM (no mention of timezone), Simon Willison shared the following blog post, quoted here in full:

Quitting programming as … ⌘ Read more

⤋ Read More

Reimbursement inequities lead to hospitals deprioritizing women’s healthcare, experts tell Congress
Maia Anderson,  Staff Writer  -  Healthcare Brew

_Stephan: In the United States, it isn’t just that women get inferior healthcare compared to men. There is also a major issue about how insurance companies are prepared to pay for that healthcare. To quote this report after studying the issue a team of researchers said, “The group— … ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for June 5, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: OpenH264 in Fedora; Wallabag; Safety certification; 6.16 Merge window; Bounce buffering; Hardening repository problems; Device-initiated I/O; Faster networking; OSPM 2025; Free software in science.

  • Briefs: Kea vulnerabilities; Alpine Linux 3.22.0; Fedora strategy; Quotes; …

  • Announcements: Newsletters, conferences, securi … ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for May 29, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Glibc security; How we lost the Internet; Encrypted DNS; 6.15 Development statistics; Filesystem stress-testing; BPF verifier; Network access from BPF; OSPM 2025.

  • Briefs: AlmaLinux 10.0; FESCo decision overturned; NixOS 25.05; Pocket, Launchpad retired; Quotes; …

  • Announcements: Newsletters, conferences, security updates, … ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for May 22, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Home Assistant; Setuptools; Debian AI GR; DMA-mapping API; BPF CI; OSPM 2025

  • Briefs: Go audit; Oniux; Asahi progress; Rust in FreeBSD; RHEL 10; Rust 1.87.0; RIP John L. Young; Quote; …

  • Announcements: Newsletters, conferences, security updates, patches, and more. ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for May 15, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Home Assistant; YaST; bpfilter; Flatpak; More LSFMM+BPF 2025 coverage.

  • Briefs: Screen security; Guix on Codeberg; Postgres I/O; GNOME executive director; Nextcloud blog; Podman 5.5.0; OSL sustainability; Quotes; …

  • Announcements: Newsletters, conferences, security updates, patches, and more. ⌘ Read more

⤋ Read More

Scientists Just Found Who’s Causing Global Warming
Joe Wilkins,  Staff Writer  -  Futurism

_Stephan: The oligarchs who bought Trump his presidency by misinforming and confusing a majority of American voters are also the same people, as this article reports, who are also destroying the wellbeing of Earth. To quote them, “A recent study published in the journal Nature Climate Change has found that the richest 10 percent of … ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for May 8, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Debian and essential packages; Custom BPF OOM killers; Speculation barriers for BPF programs; More LSFMM+BPF 2025 coverage.

  • Briefs: Deepin on openSUSE; AUTOSEL; Mission Center 1.0.0; OASIS ODF; Redis license; USENIX ATC; Quotes; …

  • Announcements: Newsletters, conferences, security updates, patches, and more. ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for May 1, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Mailman 2 vulnerabilities; AI in Debian; __nonstring__; Cache-aware scheduling; Freezing filesystems; Socket-level storage; Debugging information; LWN in 2025.

  • Briefs: Debian election; Kali Linux key; OpenBSD 7.7; Firefox 138.0; GCC 15.1; Meson 1.8.0; Valgrind 3.25.0; FSF review; OSI retrospective; Mastodon; Quotes; …

  • [Announcements](https://lwn.net/Arti … ⌘ Read more

⤋ Read More

10 Times Government Officials Made Startling Claims
No, this is not that type of list. It doesn’t contain quotes like “God save the Queen, man” or “I tested positively toward negative, right.” This list is about claims made by government officials worldwide that sort of eclipse anything heads of state may have said (or will say in the future). Think you’ve heard […]

The post [10 Times Government Officials Made Startling Claims](https://listverse.com/2025/04/26/10-times-government … ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for April 24, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Owen Le Blanc and MCC; UID/GID drift; DMA for UIO; More LSFMM+BPF 2025 coverage.

  • Briefs: EU OS; RISC-V Fedora; Ubuntu 25.04; NLnet funding; Template strings; Tor Browser 14.5; Quotes; …

  • Announcements: Newsletters, conferences, security updates, patches, and more. ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for April 17, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: APT 3.0; Fedora 42; Lots more LSFMM+BPF coverage.

  • Briefs: CVE funding; Yelp vulnerability; Fedora 42; Manjaro 25.0; GCC 15; Pinta 3.0; Quotes; …

  • Announcements: Newsletters, conferences, security updates, patches, and more. ⌘ Read more

⤋ Read More

There are now two (recentish) quotes I really like these days:

The smartest person in the room is not the one with all the answers—it’s the one who’s brave enough to ask the dumb questions

and

The kindest person in the room is often the smartest

⤋ Read More

[$] LWN.net Weekly Edition for April 10, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Debian project leader election; 6.15 Merge window; Lots of LSFMM coverage; Joplin.

  • Briefs: Firefox hardening; OpenSSH 10.0; Supply chain security; FreeDOS 1.4; OpenSSL 3.5.0; Rust 1.86.0; Quotes; …

  • Announcements: Newsletters, conferences, security updates, patches, and more. ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for April 3, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Calibre 8.0; Fedora reproducibility; OpenWrt One; 6.15 Merge Window; LSFMM+BPF coverage including BPF in GCC, Rust merging process, and more.

  • Briefs: Ubuntu namespaces; New FPL; PorteuX 2.0; Firefox 137.0; GCC Rust; Rockbox 4.0; Rust specification; Thundermail; Dave Täht RIP; Quotes; …

  • Announcements: Newsletters, confer … ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for March 27, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Open source in government; OSI election; Memory-management medley; Address-space isolation; CMA; 6.14 Development stats; State of the page.

  • Briefs: Asahi Linux progress; Reproducible Debian; rpi-image-gen; Neovim 0.11; OpenH264; Quotes; …

  • Announcements: Newsletters, conferences, security updates, patches, and more. ⌘ Read more

⤋ Read More

[$] LWN.net Weekly Edition for March 20, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Oxidizr; Spectre mitigations; Frozen pages; Mapcount madness; Open-source risks; /e/OS.

  • Briefs: Supply chain attacks; SystemRescue 12.00; Casual Make; GIMP 3.0; Git 2.49.0; GNOME 48; PeerTube 7.1; Quotes; …

  • Announcements: Newsletters, conferences, security updates, patches, and more. ⌘ Read more

⤋ Read More

[ANN] The arbitration system in Haveno doesn’t prevent arbitrators from pulling the funds

[Issue confirmed by official monero moderator on dread:] After some thoughts, I think you are right and that the arbitration system in Haveno doesn’t prevent arbitrators from pulling the funds. They would need to create a bot that takes all the offers and automatically unlock the funds with the key of the taker and arbitrator (Quote from /u/monero_desk_support)

Link: [Dread discussion (onion)](http://dreadytofatroptsdj6io7l3xptbet6ono … ⌘ Read more

⤋ Read More
In-reply-to » I got promoted today to try using Passkeys on Github.com. Fine 😅 I did that, but I discovered that when you use your Passkey to login, Chrome prompts you for your device's password (i.e: The password you use to login to your macOS Desktop). Is that intentional? Kind of defeats the point no? I mean sure, now there's no Password being transmitted, stored or presented to Github.com but still, all an attacker has to do is somehow be on my device and know my login password to my device right? Is that better or worse? 🤔

@prologic@twtxt.net I’m speculating, but if I had to guess I’d say it’s probably asking for your user password in order to access some user keyring (or whatever your OS uses to manage user secret credentials) used to safely store your passkeys related data in order to do its passkeys /ME doing air quotes Magic™ … you could try with a different password manager to avoid said scenario.

Also, passkeys UX sucks.

⤋ Read More

What 10 Actors Actually Think of Their Most Famous Lines
You know you’ve really hit the mark with fame in Hollywood when you have one line that gets repeated over and over again by millions of people. To be an actor who has “made it,” as the phrase is used, is to be a star who can be readily quoted by millions of fans and […]

The post [What 10 Actors Actually Think of Their Most Famous Lines](https://listverse.com/2025/01/26/what-10-actors-actually-think-of-their-most-famous … ⌘ Read more

⤋ Read More
In-reply-to » been playing with making fun scripts using charm CLI's gum library :P

@kat@yarn.girlonthemoon.xyz To improve you shell programming skills, I highly recommend to check out shellcheck: https://github.com/koalaman/shellcheck It points out common errors and gives some suggestions on how to improve the code. Some details in shell scripting are very tricky to get right at first. Even after decades of shell programming, I run into “corner cases” every now and then.

E.g. in getlyr’s line 7 it warns:

echo -e $(gum style --italic --foreground "#f4b8e4" "'$artist', '$song'")
        ^-- SC2046: Quote this to prevent word splitting.

For more information:
  https://www.shellcheck.net/wiki/SC2046 -- Quote this to prevent word splitt...

Most likely not all that problematic in this application, but it’s good to know about this underlying concept. Word splitting is basically splitting tokens on whitespace, this can lead to interesting consequences as illustrated by this little code:

$ echo $(echo "Hello   World")
Hello World

$ echo "$(echo "Hello   World")" 
Hello   World

In the first case the shells sees two whitespace-separated tokens or arguments for the echo command. This basically becomes echo Hello World. So, echo joins them by a single space. In the second one it sees one argument for the echo command, so echo simply echos this single argument that contains three spaces.

⤋ Read More

Religious Leaders Experiment With AI In Sermons
An anonymous reader quotes a report from the New York Times: To members of his synagogue, the voice that played over the speakers of Congregation Emanu El in Houston sounded just like Rabbi Josh Fixler’s. In the same steady rhythm his congregation had grown used to, the voice delivered a sermon about what it meant to be a neighbor in the age of artificial intelligence. Then, Rabbi Fix … ⌘ Read more

⤋ Read More

Americans spend more time living with diseases than rest of world, study shows
Maya Yang,  Reporter  -  The Guardian (U.K.)

_Stephan: ”Americans spend more time living with diseases than people from other countries, according to a new study.” What more needs to be said?  To quote from the JAMA paper: “Gains in life expectancy across global populations are recognized as a societal achievement.[1](https://jamanetwork.com/journals/jamanetworkopen/ful … ⌘ Read more

⤋ Read More

Drylands now make up 40% of land on Earth, excluding Antarctica, study says
Fiona Harvey,  Environment Editor  -  The Guardian (U.K.)

_Stephan: To quote from this report, “Barron Orr, chief scientist at UNCCD, said: ‘For the first time, a UN scientific body is warning that burning fossil fuels is causing permanent drying across much of the world, with potentially catastrophic impacts affecting access to water that could push people and nature even clos … ⌘ Read more

⤋ Read More

The Fediverse Is Getting Its Own TikTok Competitor Called Loops
An anonymous reader quotes a report from TechCrunch: Similar to how Mastodon offers an open source, distributed version of X, the fediverse is getting its own TikTok competitor. This week, an app called Loops began accepting signups on its new platform for sharing short, looping videos. Still in the early stages, Loops is not yet open sourced, nor … ⌘ Read more

⤋ Read More

Monero Observer Artistic Saturday Top 5 - Week 41, 2024
Previous Artistic Saturday weekly reports can be found in the [art] 1 section.

5 - ‘Delist this’ illustration (by EncryptedMonero2)

Image

4 - ‘Hal Finney’ quote (by anocash_xmr3)

Image

3 - ‘The ultimate store of value’ meme (by cypherpunk313374)

![‘The ultimate stor … ⌘ Read more

⤋ Read More

Sharing the comments of the poll (anonymous so I have no idea whom the comments are from):

your poll should include questions about markdown. personally i think inline bits like style, links, images are yes. block quotes, code blocks, bullet lists are mid. but tables and footnotes are no.

Yes sorry about this, I wasn’t able to change much after publishing the poll 😅

⤋ Read More
In-reply-to » @movq going a little sideways on this, "*If twtxt/Yarn was to grow bigger, then this would become a concern again. But even Mastodon allows editing, so how much of a problem can it really be? 😅*", wouldn't it preparing for a potential (even if very, very, veeeeery remote) growth be a good thing? Mastodon signs all messages, keeps a history of edits, and it doesn't break threads. It isn't a problem there.😉 It is here.

i feel like we should isolate a subset of markdown that makes sense and built it into lextwt. it already has support for links and images. maybe basic formatting bold, italic. possibly block quote and bullet lists. no tables or footnotes

⤋ Read More
In-reply-to » @movq going a little sideways on this, "*If twtxt/Yarn was to grow bigger, then this would become a concern again. But even Mastodon allows editing, so how much of a problem can it really be? 😅*", wouldn't it preparing for a potential (even if very, very, veeeeery remote) growth be a good thing? Mastodon signs all messages, keeps a history of edits, and it doesn't break threads. It isn't a problem there.😉 It is here.

i feel like we should isolate a subset of markdown that makes sense and built it into lextwt. it already has support for links and images. maybe basic formatting bold, italic. possibly block quote and bullet lists. no tables or footnotes

⤋ Read More
In-reply-to » 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?

@mckinley@twtxt.net Thanks for the feedback.

  1. Yeah I agrees that nick sound not be part of syntax. Any valid URL to a twtxt.txt-file should be enough and is more clear, so it is not confused with a email (one of the the issues with webfinger and fedivese handles)
  2. I think any valid URL would work, since we are not bound to look for exact matches. Accepting both http and https as well as a gemni and gophe could all work as long as the path to the twtxt.txt is the same.
  3. My idea is that you quote the timestamp as it is in the original twtxt.txt that you are referring to, so you can do it by simply copy/pasting. Also what are the change that the same human will make two different posts within the same second?!

Regarding the whole cryptographic keys for identity, to me it seems like an unnecessary layer of complexity. If you move to a new house or city you tell people that you moved - you can do the same in a twtxt.txt. Just post something like “I move to this new URL, please follow me there!” I did that with my feeds at least twice, and you guys still seem to read my posts:)

⤋ Read More

Not making THREADING the default view of e-mail clients and thus teaching users that e-mail is “chaotic” (if you get a lot of mail, it becomes unusable without threading) and “needs” full quoting all the time was one of the worst mistakes ever.

⤋ Read More
In-reply-to » Question of the day: What configuration file formats do you all like and use?

Yeah, the lack of comments makes regular JSON not a good configuration format in my view. Also, putting all keys in quotes and the use of commas is annoying. The big upside is that’s in lots of standard libraries.

I think the appeal with YAML is that is has comments, is kind of easy to write and read and also provides unlimited nesting levels. But it has all its drawbacks, no question. Forbidding tabs, thousands of different string flavors, having so many boolean options (poor Norwegians) etc. I use it, but I don’t particularly enjoy it.

Among simple key value pairs, I like INI files, but with # for comments, not ;. I never used TOML, read up on it yesteray before writing this question, but it looks a bit weird and has some strange rules. I guess I have to give it a try one day.

And yes, as mentioned by several of you, it always depends on the complexity of the configuration at hand.

I’m developing something for the scouts at the moment with rather simple requirements on the config. Currently, there are just four settings. Even INI would be overkill with its section. I selected JSON for now, because that’s readily available with Go’s std lib. But I do not like it.

Btw. what’s your own config format, @xuu@txt.sour.is?

⤋ Read More
In-reply-to » (#fytbg6a) What about using the blockquote format with > ?

@sorenpeter@darch.dk this makes sense as a quote twt that references a direct URL. If we go back to how it developed on twitter originally it was RT @nick: original text because it contained the original text the twitter algorithm would boost that text into trending.

i like the format (#hash) @<nick url> > "Quoted text"\nThen a comment
as it preserves the human read able. and has the hash for linking to the yarn. The comment part could be optional for just boosting the twt.

The only issue i think i would have would be that that yarn could then become a mess of repeated quotes. Unless the client knows to interpret them as multiple users have reposted/boosted the thread.

The format is also how iphone does reactions to SMS messages with +number liked: original SMS

⤋ Read More
In-reply-to » (#fytbg6a) What about using the blockquote format with > ?

@sorenpeter@darch.dk this makes sense as a quote twt that references a direct URL. If we go back to how it developed on twitter originally it was RT @nick: original text because it contained the original text the twitter algorithm would boost that text into trending.

i like the format (#hash) @<nick url> > "Quoted text"\nThen a comment
as it preserves the human read able. and has the hash for linking to the yarn. The comment part could be optional for just boosting the twt.

The only issue i think i would have would be that that yarn could then become a mess of repeated quotes. Unless the client knows to interpret them as multiple users have reposted/boosted the thread.

The format is also how iphone does reactions to SMS messages with +number liked: original SMS

⤋ Read More