hngrok
Top Archive
Login

2026/05/13

  1. I moved my digital stack to Europe from monokai.com
    996 by monokai_nl 1d ago | | |

    Article: 21 min

    The author discusses their experience in migrating their digital infrastructure to Europe for reasons related to digital sovereignty and data control. They share the process of replacing various services with European alternatives, focusing on analytics, email, password management, compute, object storage, backups, transactional emails, error tracking, AI API integration, CDN, payments, code assistance, and version control.

    By migrating to European services, the author demonstrates a commitment to digital sovereignty and data control, potentially inspiring others in the tech industry to consider similar moves for their own infrastructure.
    • Migrated services to European alternatives for better control over data and compliance with GDPR
    • Challenges in maintaining self-hosted infrastructure, such as maintenance overhead and limitations on custom domains
    • Comparison of European providers like Proton Mail, Scaleway, and Bugsink against US-based services
    • Considerations for transactional email services, including deliverability, pricing, and feature sets
    • Switching AI API integrations to Mistral and Claude Code due to alignment with personal views on data sovereignty
    • Continued use of Cloudflare for CDN needs despite its non-European origin

    Discussion (595): 2 hr 23 min

    The comment thread discusses the shift towards moving data storage, operations, and services from US-based providers to European or domestic alternatives due to concerns about digital sovereignty, trust issues with the US government, and the impact of policies like the Cloud Act. There is a growing trend towards self-hosting and using EU-based cloud services as alternatives.

    • US government's actions have led to a shift in sentiment towards moving data storage and operations to Europe.
    • Concerns about digital sovereignty, including the Cloud Act and potential military threats, are influencing European companies and organizations.
    Cloud Computing ,Digital Infrastructure
  2. Leaving GitHub for Forgejo from jorijn.com
    607 by jorijn 1d ago | | |

    Article: 33 min

    The article discusses the author's decision to leave GitHub for Forgejo, citing issues such as outages, AI integration, jurisdictional risks, and lack of control over data training. The author also details their self-hosted setup on code.jorijn.com using Forgejo v15 LTS with a focus on security measures like KVM isolation, gVisor, weekly rebuilds, and scope-bound runner tokens.

    By leaving GitHub for Forgejo, the author highlights concerns about data control and jurisdictional risks that could influence other developers' decisions regarding cloud service providers. The institutional pattern of national governments choosing open-source alternatives may also have broader implications.
    • GitHub is now a unit of Microsoft's CoreAI division, affecting its autonomy
    • Outages are attributed to AI-driven load growth
    • Copilot training data default has been flipped to opt-in for AI training by default
    • US jurisdictional risks under FISA 702 and CLOUD Act are unresolved
    • EU data residency provides comfort but not a fix for these risks
    • Forgejo was chosen over GitLab due to its full open-source nature, no open-core split, and alignment with the Dutch government's digital autonomy requirements
    Quality:
    The article provides a detailed analysis of the decision-making process and technical setup, maintaining an objective tone.

    Discussion (326): 1 hr 28 min

    The comment thread discusses concerns over GitHub's AI training practices, the desire for decentralized alternatives like Forgejo, and the trade-offs between centralized services and self-hosted platforms. Users express a mix of opinions on the importance of social aspects in development communities and the need for more control over data privacy.

    • Decentralization offers advantages but comes with challenges, especially in terms of scalability and maintenance.
    • AI training practices by centralized services like GitHub raise ethical concerns among users.
    Counterarguments:
    • The social aspect of GitHub is crucial for collaboration, discovery, and visibility of projects.
    Software Development Cloud Computing, DevOps, Security
  3. Setting up a free *.city.state.us locality domain (2025) from fredchan.org
    601 by speckx 1d ago | | |

    Article: 11 min

    This guide explains how to obtain a free *.city.state.us domain in the US by registering with a delegated registrar and acquiring nameservers from Amazon Lightsail. It includes steps for choosing a locality domain, acquiring nameservers, filling out the registration form, sending it to the registrar, and setting up DNS records.

    • US citizens or permanent residents can register
    • Domains are associated with specific locations
    • Registration requires providing personal information
    • Amazon Lightsail provides free nameservers
    • WHOIS requests do not reveal your address
    Quality:
    The article provides clear, step-by-step instructions with relevant technical details and avoids sensationalism.

    Discussion (205): 35 min

    The comment thread discusses various aspects of locality domains, including their history, usage by local governments and organizations, privacy concerns with .us TLDs, and potential for personal use. The discussion is characterized by a mix of informative insights, opinions on the commercialization of DNS, and legal considerations regarding government use of these domains.

    • Locality domains have been around since the early days of the internet
    • They can be used for branding and communication by local governments
    • Privacy concerns exist with .us TLDs due to lack of WHOIS privacy services
    Counterarguments:
    • Some locality domains may not be available due to expiration or being claimed by third parties
    • Privacy concerns can be mitigated through various services and legal measures
    • Alternative domain options exist for personal use, such as .codify.city
    Internet Domain Names
  4. Kickstarter is forced to ban adult content by payment processors from kotaku.com
    387 by stalfosknight 1d ago | | |

    Article: 4 min

    Kickstarter updates its Mature Content guidelines to prohibit certain forms of adult content, possibly due to pressure from payment processor Stripe.

    NSFW content creators may face restrictions on platforms, potentially affecting funding and visibility of adult-oriented projects.
    • Updated guidelines prohibit violent, derogatory, and sexually photo-realistic content.
    • Specific restrictions include implied sex acts, MILF/DILF content, and nudity.
    • Stripe may be influencing the change due to company ownership by Peter Thiel and Elon Musk.
    Quality:
    The article provides factual information without expressing a clear opinion.

    Discussion (272): 1 hr 10 min

    The comment thread discusses various reasons behind payment processors banning adult content, including high chargeback rates, reputational risk, and political pressure from conservative religious groups. There is a consensus that religious influence plays a significant role in the censorship of adult content, while some argue that the issue revolves around financial risks for payment processors.

    • Payment processors are banning adult content due to high chargeback rates, reputational risk, or political pressure.
    • Conservative religious groups are driving the censorship of adult content.
    Counterarguments:
    • Chargebacks do not cost payment networks any money; they are borne by merchants.
    • There is no evidence that payment processors made Kickstarter ban adult content. The ban was already in place before the article's claims.
    Internet News, Technology
  5. The Emacsification of Software from sockpuppet.org
    382 by rdslw 1d ago | | |

    Article: 17 min

    The article discusses the author's experience with finding a suitable Markdown viewer application on macOS and their subsequent creation of MDV.app, an Emacs-inspired native application that improves reading experiences for Markdown documents.

    Embracing personal software development and AI-generated code may lead to a proliferation of custom, specialized applications that enhance user experiences but also contribute to the fragmentation of standardization in software development.
    • The author's dissatisfaction with existing Markdown viewers and the desire for a better reading experience
    • The use of AI agents to generate code for the application

    Discussion (237): 1 hr 8 min

    The discussion revolves around the increasing trend of personalization and customization in software development, facilitated by Large Language Models (LLMs). Users share experiences about building custom applications using LLMs or modifying existing ones in tools like Emacs, Neovim, and others. The conversation highlights the benefits of AI-assisted programming for creating personalized solutions tailored to individual needs.

    • LLMs facilitate the creation of personalized software, making it easier for individuals to build solutions tailored to their specific needs.
    • Emacs and Neovim are highly customizable tools that allow users to tailor their workflows for personal preferences.
    Software Development MacOS Applications, Text Editing, User Interface Design
  6. Princeton mandates proctoring for in-person exams, upending 133 year precedent from dailyprincetonian.com
    365 by bookofjoe 21h ago | | |

    Article: 15 min

    Princeton University has decided to mandate proctoring for all in-person exams starting July 1st, marking a significant change from its 1893-established honor system. The decision was made after months of deliberation due to concerns over academic integrity violations and the increasing use of AI tools by students.

    • In-person examinations at Princeton will be proctored starting July 1, reversing the honor system established in 1893.
    • The proposal was passed by the faculty with one opposing vote after months of deliberation and approval from various committees.
    • Proctors will observe but not interfere during exams, documenting any suspected Honor Code violations for the student-run Honor Committee to investigate.
    Quality:
    The article provides a balanced view of the decision and its implications, citing various sources.

    Discussion (554): 2 hr 22 min

    The discussion revolves around concerns over a significant increase in cheating at Princeton, with many attributing this to changes in societal values and technological advancements that facilitate academic dishonesty. The effectiveness of the institution's honor code system is questioned, as it no longer appears to deter cheating effectively. There are differing opinions on whether proctoring exams could be an appropriate solution or if the issue lies deeper within the culture and expectations placed upon students.

    • Cheating has increased significantly at Princeton over recent years.
    Counterarguments:
    • Cheating has always been a part of education, and it's not specific to Princeton.
    • The honor code system is deeply ingrained in the culture and values of the institution.
    Education Higher Education
  7. Starship V3 from spacex.com
    318 by fprog 1d ago | | |

    Article:

    The article provides advice on how to prevent malware infections when using personal or shared networks.

    • Run an anti-virus scan on personal devices
    • Ask network administrators to check for misconfigured or infected devices

    Discussion (594): 2 hr 23 min

    The comment thread discusses SpaceX's Starship/Super Heavy project and the potential for space-based data centers. While acknowledging SpaceX's technological advancements and Elon Musk's leadership style, there is skepticism regarding the economic feasibility of space-based projects due to high launch costs, regulatory hurdles, and concerns about environmental impact. The debate also touches on Musk's public behavior and motives for acquiring XAI.

    • SpaceX's Starship/Super Heavy could revolutionize space travel and infrastructure
    • Space-based data centers offer potential advantages but face significant challenges
    • Elon Musk's leadership style is effective in attracting funding
    Counterarguments:
    • Space-based data centers may not be economically viable due to high launch costs and regulatory hurdles
    • Elon Musk's public behavior raises questions about his motives for acquiring XAI
    • SpaceX's aggressive timelines are often unrealistic, leading to skepticism
    Cybersecurity Internet Safety, Malware Prevention
  8. MacBook Neo Deep Dive: Benchmarks, Wafer Economics, and the 8GB Gamble from jdhodges.com
    307 by tosh 23h ago | | |

    Article: 41 min

    An in-depth analysis of the MacBook Neo's specifications, performance, and pricing, highlighting its unique design choices and strategic implications during a global DRAM shortage.

    • The MacBook Neo uses an A18 Pro chip, similar to that in iPhone 16 Pro.
    • It offers a balance of performance and affordability with its $599 price point.
    • Memory constraints are highlighted as the primary limitation, especially for multi-core tasks.
    • Apple's vertical integration strategy allows them to maintain margins while offering high-quality products.
    • DRAM shortage context explains Apple's decision on RAM capacity.
    Quality:
    The article provides detailed analysis and data, avoiding sensationalism.

    Discussion (366): 1 hr 2 min

    The discussion revolves around the Apple Neo laptop, with users expressing mixed opinions on its performance and hardware limitations. There is consensus on its value for the price point, but concerns about RAM capacity, battery life, and potential obsolescence are raised. Users also express interest in future upgrades or improvements to address these issues.

    • The Neo offers good value for its price point
    • There are limitations to the hardware that may affect performance
    Computer Hardware Laptops, Macs
  9. Deterministic Fully-Static Whole-Binary Translation Without Heuristics from arxiv.org
    297 by matt_d 1d ago | | |

    Article: 2 min

    Elevator is a new binary translator that statically translates x86-64 executables to AArch64 without relying on heuristics, providing deterministic translations for all possible byte interpretations.

    This technology could significantly enhance the security and reliability of software deployment, especially in critical systems where runtime errors are unacceptable.
    • Elevates first binary translator without heuristics or runtime fallbacks.
    • Handles code-versus-data decoding errors statically.
    • Generates separate control flow paths for all interpretations of every byte.
    • Uses a high-level description of the source ISA to compose code tiles.
    • Produces complete, self-contained binaries with no runtime component in the trusted code base.
    • Achieves performance on par with or better than QEMU's user-mode JIT emulation.

    Discussion (65): 13 min

    The discussion revolves around a paper proposing an innovative solution for binary translation, focusing on handling code and data ambiguities. Participants acknowledge its limitations, such as not supporting self-modifying or JIT-compiled code, but also highlight potential performance benefits compared to existing solutions like QEMU's user-mode JIT emulation.

    • The paper's solution sidesteps code-versus-data determination through superset disassembly.
    Counterarguments:
    • Self-modifying code is generally considered a bad practice in modern development due to its negative impact on performance and security.
    • The system's space expansion of 50x might be a cache disaster for some applications.
    Computer Science Software Development, Computer Vision
  10. Open Source Resistance: keep OSS alive on company time from ossresistance.com
    265 by mikemcquaid 1d ago | | |

    Article: 13 min

    The article presents the 'Open Source Resistance' manifesto advocating for treating open-source (OS) maintenance as part of regular work time in companies, without needing permission or paperwork. It argues against the current practice where OS maintainers have to request time off or donations for their work, and suggests that maintaining dependencies is already infrastructure work on the commons.

    • OS maintenance should be treated as part of regular work time.
    • No need to ask permission or paperwork for OS contributions.
    • Maintainers should not have to rely on donations or personal time for their work.
    Quality:
    The article presents a clear argument with supporting evidence and acknowledges the potential legal implications.

    Discussion (81): 21 min

    The discussion revolves around the idea of open source maintainers taking work time to contribute to projects they benefit from, with opinions on whether employers should expect such contributions. The conversation also delves into legal complexities surrounding intellectual property rights in the context of open source and employee contracts.

    • Maintainers inside companies should take work time to maintain open source projects they benefit from.
    • Employers may not allow or expect employees to contribute to open source projects during their work hours without permission.
    Counterarguments:
    • It's sad that we're at the point where everything has to be hyperbolic
    • This doesn't apply to every state. In California you have the California Labor Code Section 2870 which prohibits employers from stealing workers IP.
    • Employers just write stuff in their employement contracts. They'll write everything they possibly can, to cover asses in every possible direction.
    Open Source Software Development, Business Practices
More

About | FAQ | Privacy Policy | Feature Requests | Contact