mirror of
https://github.com/aljazceru/disobey.dev.git
synced 2025-12-17 15:24:20 +01:00
Merge pull request #1 from aljazceru/claude/migrate-hugo-blog-posts-011CUrTvANhxB5s1raCqaffr
Migrate Hugo blog posts with URL preservation
This commit is contained in:
28
content/about.md
Normal file
28
content/about.md
Normal file
@@ -0,0 +1,28 @@
|
|||||||
|
---
|
||||||
|
title: "About"
|
||||||
|
slug: "about"
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
## Overview
|
||||||
|
|
||||||
|
Aljaz is a developer focused on freedom technology, with particular interest in Bitcoin's Lightning Network and artificial intelligence. His stated goal is to "combine all of these (minus the ranting) into something that pushes the quest for freedom one step forward."
|
||||||
|
|
||||||
|
## Current Projects
|
||||||
|
|
||||||
|
**nostr.net** - Founded in January 2022, this is described as "the biggest directory of all things nostr." Aljaz operates several nostr infrastructure services including a public relay, web-of-trust relay, and HTTP gateway.
|
||||||
|
|
||||||
|
**Bolt Observer** - Launched in February 2022, this venture focuses on enterprise Lightning Network solutions with automated liquidity features and data platforms for businesses.
|
||||||
|
|
||||||
|
**Bitcoin Ljubljana** - Co-founded in August 2021 (concluded September 2023), this meetup grew into a significant community hub for Bitcoin education and monthly events in Ljubljana.
|
||||||
|
|
||||||
|
## Professional Background
|
||||||
|
|
||||||
|
His career spans infrastructure and security work, including:
|
||||||
|
- Head of Platform at Bitstamp (2018-2021), where he expanded AWS infrastructure and implemented Lightning Network capabilities
|
||||||
|
- Owner of InSec consulting firm (2014-2023), focusing on infrastructure and security projects
|
||||||
|
- Various roles in DevOps, system administration, and information security from 2006 onward
|
||||||
|
|
||||||
|
## Additional Involvement
|
||||||
|
|
||||||
|
Aljaz maintains several directories, publishes talks and podcast appearances, and participated in the Sovereign Engineering Cohort-01 experiment.
|
||||||
19
content/contact.md
Normal file
19
content/contact.md
Normal file
@@ -0,0 +1,19 @@
|
|||||||
|
---
|
||||||
|
title: "Contact"
|
||||||
|
slug: "contact"
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
## Contact Methods
|
||||||
|
|
||||||
|
**Social Media & Messaging:**
|
||||||
|
- Twitter handle: @aaaljaz
|
||||||
|
- Nostr protocol address: aljaz@nostr.si (with associated public key npub1aljazgxlpnpfp7n5sunlk3dvfp72456x6nezjw4sd850q879rxqsthg9jp)
|
||||||
|
|
||||||
|
**Direct Communication:**
|
||||||
|
- Email: a@[domain name]
|
||||||
|
- GPG key fingerprint available for secure correspondence: "A5 E1 84 5C 24 34 67 29"
|
||||||
|
|
||||||
|
## Topics of Interest
|
||||||
|
|
||||||
|
Nostr, Pubky, the Liquid Network, Lightning Network, DLCs, and cryptoanarchy.
|
||||||
11
content/posts/a-true-believer.md
Normal file
11
content/posts/a-true-believer.md
Normal file
@@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
title: "A True Believer"
|
||||||
|
date: 2025-08-14
|
||||||
|
slug: "a-true-believer"
|
||||||
|
tags: ["freedom", "cypherpunk"]
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
The piece describes an idealized figure working tirelessly on liberation-focused technologies. This individual operates under severe constraints, using salvaged materials and working relentlessly toward their vision. The author emphasizes the builder's unwavering commitment, noting that "he builds what he knows, what inspires him" and remains focused on their cause rather than conventional work schedules or comfort.
|
||||||
|
|
||||||
|
The narrative portrays someone deeply dedicated to their mission—building continues "when the enemy is gone"—and someone who views their work as their entire existence rather than a job with fixed hours. The characterization emphasizes resilience and singular focus on what the author frames as a freedom-oriented objective.
|
||||||
37
content/posts/accessing-llm-through-cli.md
Normal file
37
content/posts/accessing-llm-through-cli.md
Normal file
@@ -0,0 +1,37 @@
|
|||||||
|
---
|
||||||
|
title: "quickly accessing llama3.2 from a terminal (or any other model)"
|
||||||
|
date: 2024-10-18
|
||||||
|
slug: "accessing-llm-through-cli"
|
||||||
|
tags: ["AI", "Infrastructure"]
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
The author describes their workflow for integrating large language models into terminal-based work. Rather than switching to a browser or relying on a Telegram bot, they set up a more seamless solution using a remote GPU instance.
|
||||||
|
|
||||||
|
## Technical Setup
|
||||||
|
|
||||||
|
The solution involves three key components:
|
||||||
|
|
||||||
|
1. **Remote Infrastructure:** A cloud GPU instance running Ollama, accessible via SSH port forwarding (port 11434)
|
||||||
|
2. **Web Interface Option:** Open WebUI for browser-based access
|
||||||
|
3. **CLI Tool:** The `llm` package with Ollama plugin support
|
||||||
|
|
||||||
|
Installation steps are straightforward:
|
||||||
|
- Install the main CLI tool
|
||||||
|
- Add Ollama plugin support
|
||||||
|
- Set Llama3.2 as the default model
|
||||||
|
|
||||||
|
## Usage Examples
|
||||||
|
|
||||||
|
**Simple Query:**
|
||||||
|
The tool handles basic prompts directly from the command line with natural conversational responses.
|
||||||
|
|
||||||
|
**System Prompts:**
|
||||||
|
Users can pipe code or text through the tool with custom instructions, such as requesting code explanations.
|
||||||
|
|
||||||
|
**Chat Mode:**
|
||||||
|
Interactive sessions allow extended conversations, though the author finds this less practical than web UI alternatives.
|
||||||
|
|
||||||
|
## Limitations
|
||||||
|
|
||||||
|
The author notes the model includes safety guidelines that prevent certain types of content, and suggests exploring uncensored alternatives for less restricted interactions.
|
||||||
26
content/posts/ai-blogs-and-resource.md
Normal file
26
content/posts/ai-blogs-and-resource.md
Normal file
@@ -0,0 +1,26 @@
|
|||||||
|
---
|
||||||
|
title: "AI blogs and resource"
|
||||||
|
date: 2024-09-26
|
||||||
|
slug: "ai-blogs-and-resource"
|
||||||
|
tags: ["AI"]
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
The author curates a selection of thoughtful, long-form content sources in the AI space, noting that "in a world of explosive amount of content about AI" quality resources are valuable.
|
||||||
|
|
||||||
|
## Recommended Resources
|
||||||
|
|
||||||
|
The following sites are highlighted for substantive coverage:
|
||||||
|
|
||||||
|
- **gwern.net** - Features deep learning content alongside other topics
|
||||||
|
- **ym2132.github.io** - Focuses on extended posts about generative adversarial networks
|
||||||
|
- **simonwillison.net** - Combines Python and AI topics
|
||||||
|
- **retrochronic.com** - Explores intersections of AI and philosophy
|
||||||
|
|
||||||
|
## Video Content
|
||||||
|
|
||||||
|
For visual learners, the author recommends the AI Explained YouTube channel as an additional resource.
|
||||||
|
|
||||||
|
## Notes
|
||||||
|
|
||||||
|
The author indicates this collection may be expanded or updated in the future, suggesting it serves as an evolving curation rather than a definitive list.
|
||||||
16
content/posts/cryptoanarchy.md
Normal file
16
content/posts/cryptoanarchy.md
Normal file
@@ -0,0 +1,16 @@
|
|||||||
|
---
|
||||||
|
title: "cryptoanarchy.info"
|
||||||
|
date: 2024-11-29
|
||||||
|
slug: "cryptoanarchy"
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
The author describes an initiative to archive and preserve historical cryptocurrency and cypherpunk materials. According to the piece, the creator has been "slowly hoarding and studying a lot of old(er) crypto anarchy and cypherpunk materials over time."
|
||||||
|
|
||||||
|
The project involves maintaining backups of various resources, including anarplex archives and podcast series content. The author aims to expand upon existing work found at cryptoanarchy.wiki by establishing a comprehensive directory of materials deemed significant for historical preservation.
|
||||||
|
|
||||||
|
Future plans include packaging the accumulated materials into a torrent format to ensure wider distribution. The author states the goal is to prevent "the wisdom of those before us does not go to waste."
|
||||||
|
|
||||||
|
The initiative welcomes community contributions. Interested parties can submit suggestions through the contact page or contribute directly via the GitHub repository at cryptoanarchy-archive.
|
||||||
|
|
||||||
|
The website is accessible at cryptoanarchy.info and serves as a digital preservation effort for cypherpunk and crypto-anarchist literature and resources.
|
||||||
14
content/posts/github-no-more.md
Normal file
14
content/posts/github-no-more.md
Normal file
@@ -0,0 +1,14 @@
|
|||||||
|
---
|
||||||
|
title: "Github no more?"
|
||||||
|
date: 2025-08-17
|
||||||
|
slug: "github-no-more"
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
The author discusses concerns about GitHub representing a critical infrastructure vulnerability. While repositories exist across multiple machines, they lack proper organization, making recovery time-consuming.
|
||||||
|
|
||||||
|
To mitigate this risk, the author created a private Gitea mirror of all GitHub repositories. Using the tool "mirror-to-gitea," they successfully mirrored over 300 repositories across multiple organizations without manual configuration.
|
||||||
|
|
||||||
|
Beyond personal repositories, the author maintains mirrors of third-party projects for preservation and OSINT purposes. These are currently stored separately but could potentially be integrated into Gitea, though this would significantly increase deployment size—potentially to tens of thousands of repositories.
|
||||||
|
|
||||||
|
The author acknowledges this approach doesn't eliminate GitHub dependency but ensures a comprehensive backup exists. They describe the solution as providing security through redundancy while maintaining the practical utility GitHub currently offers.
|
||||||
27
content/posts/how-to-post-videos-everyone-can-watch.md
Normal file
27
content/posts/how-to-post-videos-everyone-can-watch.md
Normal file
@@ -0,0 +1,27 @@
|
|||||||
|
---
|
||||||
|
title: "how to post videos everyone can watch"
|
||||||
|
date: 2025-05-22
|
||||||
|
slug: "how-to-post-videos-everyone-can-watch"
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
The author addresses a persistent problem in 2025: video compatibility across devices. They note that while technology has advanced significantly, sharing videos that work universally remains challenging, particularly when iPhone users cannot open certain formats.
|
||||||
|
|
||||||
|
## Solution
|
||||||
|
|
||||||
|
The article recommends using FFmpeg with a bash function to convert videos to a universally compatible format. The proposed bash function is:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
cvideo() { ffmpeg -i "$1" -c:v libx264 -crf 20 -preset slow -vf format=yuv420p -c:a aac -movflags +faststart "${1%_*}"_twitter.mp4; }
|
||||||
|
```
|
||||||
|
|
||||||
|
**Usage example:** `cvideo iphone_cant_watch_me.webm`
|
||||||
|
|
||||||
|
## Key Points
|
||||||
|
|
||||||
|
- This approach converts videos to MP4 format compatible across platforms
|
||||||
|
- The resulting files are suitable for social media uploads (Twitter, etc.)
|
||||||
|
- Users should add this function to their `.bashrc` or similar shell configuration file
|
||||||
|
- The solution leverages FFmpeg, established open-source software for multimedia handling
|
||||||
|
|
||||||
|
The author humorously contrasts modern codec issues with historical workarounds, suggesting that universal video compatibility "is something we need to wait for AGI to be achievable."
|
||||||
14
content/posts/i-build-timeconvert-org.md
Normal file
14
content/posts/i-build-timeconvert-org.md
Normal file
@@ -0,0 +1,14 @@
|
|||||||
|
---
|
||||||
|
title: "I built timeconvert.org"
|
||||||
|
date: 2025-01-31
|
||||||
|
slug: "i-build-timeconvert-org"
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
The author created a minimalist timestamp conversion website emphasizing simplicity and user experience. They describe the project as featuring "No cookies, no banners, no analytics, no frameworks, no junk. Good old web 1.0. html + css + javascript."
|
||||||
|
|
||||||
|
The motivation stemmed from frustration with existing solutions. While acknowledging that epoch converter tools already exist, the creator found them problematic due to excessive popups and cookie consent requests. They wanted a streamlined alternative where users could "paste whatever time format I have and it will give me the alternatives."
|
||||||
|
|
||||||
|
The author notes an interesting development decision-making process: after building the tool, they spent time analyzing keyword analytics and purchased a dedicated domain (timeconvert.org) specifically for hosting it. They humorously reflect on this scope creep, attributing it partly to how "LLM's are a big enabler of procrastination driven development."
|
||||||
|
|
||||||
|
The site represents a deliberately back-to-basics approach to web development, prioritizing user privacy and simplicity over modern frameworks and tracking mechanisms.
|
||||||
25
content/posts/the-directory-guy.md
Normal file
25
content/posts/the-directory-guy.md
Normal file
@@ -0,0 +1,25 @@
|
|||||||
|
---
|
||||||
|
title: "the directory guy"
|
||||||
|
date: 2024-09-29
|
||||||
|
slug: "the-directory-guy"
|
||||||
|
tags: ["nostr", "directories"]
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
The author shares their practice of maintaining public research bookmark repositories on GitHub, initially created to share resources with friends discussing various topics. Several of these collections have gained popularity.
|
||||||
|
|
||||||
|
## Featured Directories
|
||||||
|
|
||||||
|
**nostr.net** - A comprehensive directory of Nostr resources. Originally a GitHub repository, it "got big enough that its starting to warrant a redesign" and later received its own domain.
|
||||||
|
|
||||||
|
**ungovernable.tech** - Started as research bookmarks exploring confidential data vending machines. It has evolved into a work-in-progress consolidation of research around technologies offering "better alternative to the current big brother dystopia of centralized dragnets."
|
||||||
|
|
||||||
|
**dlc.wiki** - A collection focused on discreet log contracts. Though the author isn't actively researching this topic, it remains updated through community contributions.
|
||||||
|
|
||||||
|
**lightning-network.tech** - Contains resources for Lightning Network node operators, maintained intermittently by the author.
|
||||||
|
|
||||||
|
**lightning-landscape.net** - An under-construction project attempting to create an accessible directory with easier community participation, currently paused due to operational costs.
|
||||||
|
|
||||||
|
**world-backup** - A GitHub repository curating essential information for emergency scenarios, including manuals and critical data like maps for portable drives.
|
||||||
|
|
||||||
|
The author reflects that these directories hopefully have provided value to others exploring these emerging technologies and protocols.
|
||||||
@@ -0,0 +1,17 @@
|
|||||||
|
---
|
||||||
|
title: "The Untold Story of the Greatest Crypto Project Ever"
|
||||||
|
date: 2024-10-03
|
||||||
|
slug: "the-untold-story-of-the-greatest-crypto-project-ever"
|
||||||
|
tags: ["cryptography", "freedom", "cypherpunk"]
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
This brief article discusses a historical narrative about cryptography rather than cryptocurrency. The author clarifies that "crypto in this case stands for cryptography, as it is for a long time before shitcoins came into existence."
|
||||||
|
|
||||||
|
The piece references Paul Rosenberg's work *A Lodging of Wayfaring Men* and notes that an audiobook version was created by Max Hillebrand. However, the main focus is directing readers to an earlier story titled *The Untold Story of the Greatest Crypto Project Ever*, which the author suggests may have inspired Rosenberg's book.
|
||||||
|
|
||||||
|
## Key Points
|
||||||
|
|
||||||
|
Since the original blog posts are no longer available on Rosenberg's website, the author has compiled links to archived versions of the story across six installments (Introduction and Parts 1-6), primarily hosted on freedomsphoenix.com and the Internet Archive.
|
||||||
|
|
||||||
|
The author presents this narrative as valuable for understanding cypherpunk and anarcho-capitalist ideas from the 1990s, describing it as "a great starting point" for deeper exploration of these historical movements and their key figures.
|
||||||
23
content/posts/wordpress-docker-setup.md
Normal file
23
content/posts/wordpress-docker-setup.md
Normal file
@@ -0,0 +1,23 @@
|
|||||||
|
---
|
||||||
|
title: "wordpress docker setup"
|
||||||
|
date: 2025-05-05
|
||||||
|
slug: "wordpress-docker-setup"
|
||||||
|
draft: false
|
||||||
|
---
|
||||||
|
|
||||||
|
The author shares a Docker configuration for quickly deploying WordPress, developed while creating a WooCommerce extension. The setup involves two main components:
|
||||||
|
|
||||||
|
## Docker Compose Configuration
|
||||||
|
|
||||||
|
The article provides a `docker-compose.yml` file featuring a WordPress service and MySQL database. The WordPress container exposes port 12999 and connects to the database using environment variables. The setup includes volume mounting for `wp-content` directory and establishes networking between services using a bridge network called `wp-network`. The MySQL database is configured with persistent storage through named volumes.
|
||||||
|
|
||||||
|
## Nginx Reverse Proxy Setup
|
||||||
|
|
||||||
|
A critical configuration element involves setting up an Nginx reverse proxy with HTTPS support. The author emphasizes that "you need to set https headers for the proxy otherwise wordpress will serve the content back in mixed mode" and cause browser complaints.
|
||||||
|
|
||||||
|
Key proxy headers include:
|
||||||
|
- `X-Forwarded-Proto https` for protocol preservation
|
||||||
|
- HTTP/1.1 upgrade settings for connection compatibility
|
||||||
|
- Host header configuration for proper routing
|
||||||
|
|
||||||
|
The configuration integrates with Let's Encrypt SSL certificates for HTTPS termination, creating a secure connection between the reverse proxy and clients while communicating with the containerized WordPress installation.
|
||||||
Reference in New Issue
Block a user