Wow, it's so useful, almost the same h4xor spirit as asking for a summary of /b/ every morning through a message on IRC.

yuuuuuuuck

A proper article is researched.

Lo peor es que debido a las noticias del alto el fuego es que la gente piensa que ya no hay guerra. Y como son “pocas” todos los días se vuelve cotidiano y inconsecuente para los lectores. No motiva la gente a actuar que es lo que los medios (y los del billete atrás de ellos) quieren.

I was just passively scrolling through. Thanks for pointing this out. It's being given the Nicole treatment.

This Lemmy community is part of the problem.

Everything to do with the precision flying required to hit the towers as they did performed by a few barely trained Saudis in a commercial passenger jetliner.
The passport of one of the Saudi's found in perfect condition in the rubble.
The fact that an insurance policy had just been taken out on the buildings.
The emptying of the basement vaults one day prior.
The people who worked at the towers, but were absent that day.
Tower 7.
Everything to do with the Pentagon:
The fact that the fed announced trillions of dollars missing on 9/10.
The fact that the only part of the Pentagon destroyed was bookkeeping where those records and audits were stored.
The fact that it was clearly a missile strike and no plane debris could be shown.
Again, a nearly impossible strike in a commercial jet by a barely trained pilot.

This is just off the top of my head, I'm sure more will come to me as the day goes.

Add that the Secretary of Transportation Norman Mineta's testimony was not included in the commission report.

.

Is this not what the scaled sort already does?

Store the text as a key in S3 so you can easily access it with a rest call!

Got it! You want a Python script that recursively walks through a Git repository, finds all .py files, and writes them into a single Markdown file in a tree-like structure, followed by the file contents. Here's a clean script to do that:

import os

def generate_tree_md(root_dir, md_file):
    python_files = []
    
    # Walk the directory recursively and collect Python files
    for dirpath, dirnames, filenames in os.walk(root_dir):
        for filename in filenames:
            if filename.endswith('.py'):
                full_path = os.path.join(dirpath, filename)
                relative_path = os.path.relpath(full_path, root_dir)
                python_files.append(relative_path)
    
    # Sort files to ensure tree structure is consistent
    python_files.sort()
    
    with open(md_file, 'w', encoding='utf-8') as f:
        last_parts = []
        
        for file_path in python_files:
            parts = file_path.split(os.sep)
            # Print tree structure
            for i, part in enumerate(parts):
                if i < len(parts) - 1:  # Directory part
                    if len(last_parts) <= i or last_parts[i] != part:
                        # Print directory if it changed
                        f.write('    ' * i + f'└── {part}\n')
                        if len(last_parts) <= i:
                            last_parts.append(part)
                        else:
                            last_parts[i] = part
                else:  # File part
                    f.write('    ' * i + f'├── {part}\n')
            # Append file content
            f.write('```\n')
            with open(os.path.join(root_dir, file_path), 'r', encoding='utf-8') as code_file:
                f.write(code_file.read())
            f.write('```\n\n')

if __name__ == "__main__":
    repo_path = "."  # Change this to your repo path
    output_md = "merged_python_files.md"
    generate_tree_md(repo_path, output_md)
    print(f"Merged Python files written to {output_md}")

✅ How it works:

1. Recursively collects all .py files in the repo.
2. Sorts them to maintain tree order.
3. Writes a tree-like Markdown representation of directories and files.
4. Appends the content of each Python file in code blocks.

If you want, I can also improve this to look exactly like the Linux tree command with proper ├── and └── for both files and folders for nested directories—it’ll look prettier and more accurate for big projects.

Do you want me to do that?

Nice but this is not complete. He left out pearl clutching and catering to the middle of the tent.

Marcela's comment about “pearl clutching” and “catering to the middle of the tent” highlights two distinct rhetorical tactics often used in debates or discussions. Here's an explanation of each:

🫣 Pearl Clutching

Pearl clutching refers to a dramatic or exaggerated display of shock or outrage, often in response to something perceived as vulgar, immoral, or inappropriate. The term evokes the image of someone clutching their pearls in mock horror, a gesture historically associated with upper-class women feigning indignation. In modern usage, it describes reactions that may be insincere or disproportionate to the actual offense. (Cambridge Dictionary)

🎪 Catering to the Middle of the Tent

Catering to the middle of the tent is a metaphor from politics, particularly in the context of broad-based or "big tent" parties. A "big tent" party seeks to include a wide range of ideologies and groups. "Catering to the middle of the tent" implies focusing on the centrist or moderate factions within this broad coalition, often at the expense of more radical or fringe elements. This approach aims to maintain unity and appeal to the largest number of people, but can sometimes dilute more progressive or radical positions to achieve consensus. (Wikipedia)

Both terms describe strategies that can be used to navigate complex discussions or debates. While "pearl clutching" may serve to deflect criticism or portray oneself as morally superior, "catering to the middle of the tent" focuses on maintaining broad appeal and unity, sometimes at the cost of more specific or radical viewpoints.

Nice but this is not complete. He left out pearl clutching and catering to the middle of the tent.