#aaronschwartz — Public Fediverse posts

https://www.fogolf.com/1327736/donald-trump-breaks-silence-on-american-troops-killed-in-iran/ Donald Trump Breaks Silence on American Troops Killed in Iran #AaronSchwartz #Donald #DonaldTrump #DonaldTrumpGolf #DonaldTrumpGolfing #DroneStrike #HannahBrandt #Iran #IranianMissileStrike #PeteHegseth #trump #TrumpGolf #TrumpGolfing

https://www.fogolf.com/1327736/donald-trump-breaks-silence-on-american-troops-killed-in-iran/ Donald Trump Breaks Silence on American Troops Killed in Iran #AaronSchwartz #Donald #DonaldTrump #DonaldTrumpGolf #DonaldTrumpGolfing #DroneStrike #HannahBrandt #Iran #IranianMissileStrike #PeteHegseth #trump #TrumpGolf #TrumpGolfing

https://www.fogolf.com/1327736/donald-trump-breaks-silence-on-american-troops-killed-in-iran/ Donald Trump Breaks Silence on American Troops Killed in Iran #AaronSchwartz #Donald #DonaldTrump #DonaldTrumpGolf #DonaldTrumpGolfing #DroneStrike #HannahBrandt #Iran #IranianMissileStrike #PeteHegseth #trump #TrumpGolf #TrumpGolfing

And I think that's the important bit. It hits a sweet spot for functionality and ubiquity, _and_ it is freeform enough that I don't have to think in advance how I want to use it—I literally adapt queries and files to the project I'm working on, as I go.

It's a "whatever" box in the context of, "I'm down for whatever you're into, boss" box. But it will do "whatever", deterministically. By cleverly combining pretty, extensible, and customizable rendering of the results of queries over an ad-hoc #markdown-based datastore.

Now, I know that (especially after reading the mention of #symbolics #lispmachine in the first post), someone's gonna say "but emacs!". And sure, follow your bliss, not stepping into that one. Suffice it to say, I'm well past mid career and have tried to love Emacs, perennially, since I started. I have accepted that it meets neither my workflow nor aesthetic needs (and I'll thank you for trusting me on that).

I thought, for a while, that maybe I could make #VSCode be the environment I could use to do this, what with MarkdownPreviewEnhanced and other plugins. But that is an IDE optimized for developing _other_ applications, which is different from building a boat whilst sailing it.

Anyway, this is turning into something that should be a blog post, and I don't expect anyone will read this far anyway, but I thought I'd stop and give credit where credit is due. #obsidian is the closed thing to an ad-hoc productivity operating system I've ever used, and it's quietly become one of the most important pieces of software I have.

Nicely done, @obsidian and community. And nicely done, @gruber and #aaronschwartz and everyone who's made #markdown what it is.

And I think that's the important bit. It hits a sweet spot for functionality and ubiquity, _and_ it is freeform enough that I don't have to think in advance how I want to use it—I literally adapt queries and files to the project I'm working on, as I go.

It's a "whatever" box in the context of, "I'm down for whatever you're into, boss" box. But it will do "whatever", deterministically. By cleverly combining pretty, extensible, and customizable rendering of the results of queries over an ad-hoc #markdown-based datastore.

Now, I know that (especially after reading the mention of #symbolics #lispmachine in the first post), someone's gonna say "but emacs!". And sure, follow your bliss, not stepping into that one. Suffice it to say, I'm well past mid career and have tried to love Emacs, perennially, since I started. I have accepted that it meets neither my workflow nor aesthetic needs (and I'll thank you for trusting me on that).

I thought, for a while, that maybe I could make #VSCode be the environment I could use to do this, what with MarkdownPreviewEnhanced and other plugins. But that is an IDE optimized for developing _other_ applications, which is different from building a boat whilst sailing it.

Anyway, this is turning into something that should be a blog post, and I don't expect anyone will read this far anyway, but I thought I'd stop and give credit where credit is due. #obsidian is the closed thing to an ad-hoc productivity operating system I've ever used, and it's quietly become one of the most important pieces of software I have.

Nicely done, @obsidian and community. And nicely done, @gruber and #aaronschwartz and everyone who's made #markdown what it is.

And I think that's the important bit. It hits a sweet spot for functionality and ubiquity, _and_ it is freeform enough that I don't have to think in advance how I want to use it—I literally adapt queries and files to the project I'm working on, as I go.

It's a "whatever" box in the context of, "I'm down for whatever you're into, boss" box. But it will do "whatever", deterministically. By cleverly combining pretty, extensible, and customizable rendering of the results of queries over an ad-hoc #markdown-based datastore.

Now, I know that (especially after reading the mention of #symbolics #lispmachine in the first post), someone's gonna say "but emacs!". And sure, follow your bliss, not stepping into that one. Suffice it to say, I'm well past mid career and have tried to love Emacs, perennially, since I started. I have accepted that it meets neither my workflow nor aesthetic needs (and I'll thank you for trusting me on that).

I thought, for a while, that maybe I could make #VSCode be the environment I could use to do this, what with MarkdownPreviewEnhanced and other plugins. But that is an IDE optimized for developing _other_ applications, which is different from building a boat whilst sailing it.

Anyway, this is turning into something that should be a blog post, and I don't expect anyone will read this far anyway, but I thought I'd stop and give credit where credit is due. #obsidian is the closed thing to an ad-hoc productivity operating system I've ever used, and it's quietly become one of the most important pieces of software I have.

Nicely done, @obsidian and community. And nicely done, @gruber and #aaronschwartz and everyone who's made #markdown what it is.

And I think that's the important bit. It hits a sweet spot for functionality and ubiquity, _and_ it is freeform enough that I don't have to think in advance how I want to use it—I literally adapt queries and files to the project I'm working on, as I go.

It's a "whatever" box in the context of, "I'm down for whatever you're into, boss" box. But it will do "whatever", deterministically. By cleverly combining pretty, extensible, and customizable rendering of the results of queries over an ad-hoc #markdown-based datastore.

Now, I know that (especially after reading the mention of #symbolics #lispmachine in the first post), someone's gonna say "but emacs!". And sure, follow your bliss, not stepping into that one. Suffice it to say, I'm well past mid career and have tried to love Emacs, perennially, since I started. I have accepted that it meets neither my workflow nor aesthetic needs (and I'll thank you for trusting me on that).

I thought, for a while, that maybe I could make #VSCode be the environment I could use to do this, what with MarkdownPreviewEnhanced and other plugins. But that is an IDE optimized for developing _other_ applications, which is different from building a boat whilst sailing it.

Anyway, this is turning into something that should be a blog post, and I don't expect anyone will read this far anyway, but I thought I'd stop and give credit where credit is due. #obsidian is the closed thing to an ad-hoc productivity operating system I've ever used, and it's quietly become one of the most important pieces of software I have.

Nicely done, @obsidian and community. And nicely done, @gruber and #aaronschwartz and everyone who's made #markdown what it is.

And I think that's the important bit. It hits a sweet spot for functionality and ubiquity, _and_ it is freeform enough that I don't have to think in advance how I want to use it—I literally adapt queries and files to the project I'm working on, as I go.

It's a "whatever" box in the context of, "I'm down for whatever you're into, boss" box. But it will do "whatever", deterministically. By cleverly combining pretty, extensible, and customizable rendering of the results of queries over an ad-hoc #markdown-based datastore.

Now, I know that (especially after reading the mention of #symbolics #lispmachine in the first post), someone's gonna say "but emacs!". And sure, follow your bliss, not stepping into that one. Suffice it to say, I'm well past mid career and have tried to love Emacs, perennially, since I started. I have accepted that it meets neither my workflow nor aesthetic needs (and I'll thank you for trusting me on that).

I thought, for a while, that maybe I could make #VSCode be the environment I could use to do this, what with MarkdownPreviewEnhanced and other plugins. But that is an IDE optimized for developing _other_ applications, which is different from building a boat whilst sailing it.

Anyway, this is turning into something that should be a blog post, and I don't expect anyone will read this far anyway, but I thought I'd stop and give credit where credit is due. #obsidian is the closed thing to an ad-hoc productivity operating system I've ever used, and it's quietly become one of the most important pieces of software I have.

Nicely done, @obsidian and community. And nicely done, @gruber and #aaronschwartz and everyone who's made #markdown what it is.

"Sam Altman May Control Our Future—Can He Be Trusted?"

https://www.newyorker.com/magazine/2026/04/13/sam-altman-may-control-our-future-can-he-be-trusted#intcid=_the-new-yorker-mobile-app-discover_2e586c43-a407-4654-bcc7-76a531387d6e_popular-organic

#TheNewYorker #NewYorker #SamAltmann #Altmann #AaronSchwartz #Schwartz #artificialintelligence #ai
#fascism

"Sam Altman May Control Our Future—Can He Be Trusted?"

https://www.newyorker.com/magazine/2026/04/13/sam-altman-may-control-our-future-can-he-be-trusted#intcid=_the-new-yorker-mobile-app-discover_2e586c43-a407-4654-bcc7-76a531387d6e_popular-organic

#TheNewYorker #NewYorker #SamAltmann #Altmann #AaronSchwartz #Schwartz #artificialintelligence #ai
#fascism

"Sam Altman May Control Our Future—Can He Be Trusted?"

https://www.newyorker.com/magazine/2026/04/13/sam-altman-may-control-our-future-can-he-be-trusted#intcid=_the-new-yorker-mobile-app-discover_2e586c43-a407-4654-bcc7-76a531387d6e_popular-organic

#TheNewYorker #NewYorker #SamAltmann #Altmann #AaronSchwartz #Schwartz #artificialintelligence #ai
#fascism

"Sam Altman May Control Our Future—Can He Be Trusted?"

https://www.newyorker.com/magazine/2026/04/13/sam-altman-may-control-our-future-can-he-be-trusted#intcid=_the-new-yorker-mobile-app-discover_2e586c43-a407-4654-bcc7-76a531387d6e_popular-organic

#TheNewYorker #NewYorker #SamAltmann #Altmann #AaronSchwartz #Schwartz #artificialintelligence #ai
#fascism

"Sam Altman May Control Our Future—Can He Be Trusted?"

https://www.newyorker.com/magazine/2026/04/13/sam-altman-may-control-our-future-can-he-be-trusted#intcid=_the-new-yorker-mobile-app-discover_2e586c43-a407-4654-bcc7-76a531387d6e_popular-organic

#TheNewYorker #NewYorker #SamAltmann #Altmann #AaronSchwartz #Schwartz #artificialintelligence #ai
#fascism

Tasty ... and RIP #AaronSchwartz again : « #NVIDIA Contacted Anna’s Archive to Secure Access to Millions of Pirated Books » 🤑

https://torrentfreak.com/nvidia-contacted-annas-archive-to-secure-access-to-millions-of-pirated-books/

#AnnasArchive #Piracy #AIBubble #AI #IA #LLM #GranTheftAutomatic

Tasty ... and RIP #AaronSchwartz again : « #NVIDIA Contacted Anna’s Archive to Secure Access to Millions of Pirated Books » 🤑

https://torrentfreak.com/nvidia-contacted-annas-archive-to-secure-access-to-millions-of-pirated-books/

#AnnasArchive #Piracy #AIBubble #AI #IA #LLM #GranTheftAutomatic

"internets own boy - story of aaron schwartz" - passend zum Todestag von Aaron Schwartz. Über Datenhoheit , Zugang zu Wissen und Open Source und staatliche Repression.
notable Mention : #scihub #openaccess #aaronschwartz https://sci-hub.cat
Der Film direktlink : https://archive.org/download/TheInternetsOwnBoyTheStoryOfAaronSwartz

"internets own boy - story of aaron schwartz" - passend zum Todestag von Aaron Schwartz. Über Datenhoheit , Zugang zu Wissen und Open Source und staatliche Repression.
notable Mention : #scihub #openaccess #aaronschwartz https://sci-hub.cat
Der Film direktlink : https://archive.org/download/TheInternetsOwnBoyTheStoryOfAaronSwartz

@mahryekuh @robb I was just thinking of this appalling hypocrisy today!
I see no 'Rule of Law', only 'Rule of Coin'

#AaronSchwartz

@mahryekuh @robb I was just thinking of this appalling hypocrisy today!
I see no 'Rule of Law', only 'Rule of Coin'

#AaronSchwartz

Siempre es bueno volver a ver éste documental recordando todo el trabajo de Aaron Schwartz. #RSS #AaronSchwartz #Reddit

https://youtu.be/hjFLqC5EnQo?si=xdInxBy-iUBkZDA-

Appropriate image for today..

#reddit #redditblackout #kbin #aaronschwartz

Appropriate image for today..

#reddit #redditblackout #kbin #aaronschwartz

"internets own boy - story of aaron schwartz" - passend zum 10. Todestag von Aaron Schwartz. Über Datenhoheit , Zugang zu Wissen und Open Source und staatliche Repression.
notable Mention : #scihub #openaccess #aaronschwartz https://sci-hub.cat
Der Film direktlink : https://archive.org/download/TheInternetsOwnBoyTheStoryOfAaronSwartz

"internets own boy - story of aaron schwartz" - passend zum 10. Todestag von Aaron Schwartz. Über Datenhoheit , Zugang zu Wissen und Open Source und staatliche Repression.
notable Mention : #scihub #openaccess #aaronschwartz https://sci-hub.cat
Der Film direktlink : https://archive.org/download/TheInternetsOwnBoyTheStoryOfAaronSwartz

🎬 The Internet's Own Boy
The Story of Aaron Schwartz

A biopic about the story of programming prodigy and information activist Aaron Swartz. From Swartz's help in the development of the basic internet protocol RSS to his co-founding of Reddit, his fingerprints are all over the internet. This film is a personal story about what we lose when we are tone deaf about technology and its relationship to our civil liberties.

🔴 https://vidcommons.org/w/jW7wSVvHF4o7LCTdaCCUQ2

#AaronSchwartz

RT https://twitter.com/HenriVerdier
Aujourd’hui 11 janvier, cela fait 6 ans qu’Aaron Schwartz nous a quitté.
Cette semaine est sorti le livre essentiel de @florevasseur. #mustread

« Be curious. Read widely. Try new things. I think a lot of what people call intelligence boils down to curiosity... » #AaronSchwartz