# email Email is electronic mail for sending text messages between computer users using standardized Internet message formats and transport protocols. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The weekly snippet-server: open-sourced DevFeed: [The weekly snippet-server: open-sourced]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-02-01T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Snippet](), [configuration](), [email](), [Markdown]() Tags: [configuration](), [email](), [engineering](), [infrastructure](), [markdown](), [news](), [open](), [snippet]() ### AI overview Craig Silverstein describes Khan Academy's open-sourced weekly snippet server, a simple tool for sharing brief weekly work updates. It uses a textbox with optional Markdown formatting and makes snippets visible according to email-domain and server configuration. ### Source excerpt By Craig Silverstein When I joined Khan Academy, my first project was to write a version of the ... Read more ## Building EasyReply: How We Used Laravel to Unify Customer Support DevFeed: [Building EasyReply: How We Used Laravel to Unify Customer Support]() Original publisher: [Read original article]() Author: Emma Blake Published: 2026-09-11T16:06:51Z Content type: article Language: en Sources: [Laravel]() Topics: [Laravel](), [Support](), [Artificial Intelligence](), [React](), [WebSocket](), [PHP](), [Single-page application (SPA)](), [email](), [Front end](), [Instagram]() Tags: [ai](), [api](), [development](), [email](), [frontend](), [instagram](), [laravel](), [queue](), [react](), [sponsor](), [support](), [ui](), [websocket]() ### AI overview This article explains how EasyReply uses Laravel to combine email, Slack, Instagram, and WhatsApp conversations in an AI-powered shared inbox. It describes Laravel Reverb for real-time updates, Inertia and React for the frontend, and queues for background processing. ### Source excerpt EasyReply pulls email, Slack, Instagram, and WhatsApp into one AI shared inbox, built on Laravel with Reverb, Inertia, React, and queues. The post Building EasyReply: How We Used Laravel to Unify Customer Support appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## \[Crypto\] Time-based one-time password (TOTP) for 2FA, part I DevFeed: [\[Crypto\] Time-based one-time password (TOTP) for 2FA, part I]() Original publisher: [Read original article]() Published: 2026-09-09T22:00:00Z Content type: tutorial Language: en Sources: [Dennis Yurichev]() Topics: [passwords](), [QR Code](), [Google](), [Python](), [Unix](), [App](), [email](), [Code]() Tags: [account](), [app](), [argument](), [backup](), [code](), [crypto](), [env-file-security](), [github](), [google](), [password](), [protection](), [python](), [run](), [server](), [smartphone](), [unix]() ### AI overview This tutorial explains how time-based one-time passwords work for two-factor authentication. It covers importing a base32-encoded secret from a QR code into Google Authenticator, generating 6-digit login codes, and calculating them with HMAC-SHA-1 from the secret and Unix time. It also discusses backup codes and securely storing TOTP secrets separately from passwords. ### Source excerpt [Crypto] Time-based one-time password (TOTP) for 2FA, part I ## 10+ best practices to improve your email deliverability DevFeed: [10+ best practices to improve your email deliverability]() Original publisher: [Read original article]() Author: Jesse Sumrak Published: 2026-09-09T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [email](), [SendGrid](), [API]() Tags: [best-practices](), [deliverability](), [domain](), [email](), [industry-insights](), [marketing](), [sendgrid](), [spam](), [spoofing](), [subscriber]() ### AI overview This tutorial explains email deliverability and presents more than ten practices for improving inbox placement, including domain authentication, double opt-in, non-spammy subject lines, list cleaning, and avoiding spam traps. It also distinguishes delivery from deliverability and discusses sender reputation and subscriber engagement. ### Source excerpt Email deliverability determines whether your messages reach inboxes or spam folders. Follow these 10+ best practices to improve your deliverability rates. ## 🎙 How I AI: How this PM uses Claude to handle 70% to 80% of his workday DevFeed: [🎙 How I AI: How this PM uses Claude to handle 70% to 80% of his workday]() Original publisher: [Read original article]() Author: Lenny Rachitsky Published: 2026-08-31T15:01:58Z Content type: article Language: en Sources: [Lenny's Newsletter]() Topics: [Claude](), [Artificial Intelligence](), [Notion](), [Slack](), [email]() Tags: [ai](), [claude](), [email](), [notion](), [podcast](), [slack]() ### AI overview A podcast episode explains how Melio product manager Daniel Blum built a self-improving AI system around Claude and Cowork. The system manages parts of his Notion workflow, prepares weekly and daily briefs, scans Slack and email for relevant context, asks questions about missing knowledge, and learns from his edits. Blum says it eventually handles 70% to 80% of his workday, while emphasizing that system architecture and continuously maintained context matter more than choosing a particular AI platform. ### Source excerpt Your weekly listens from How I AI, part of the Lenny's Podcast Network ## How I turned Claude into a self-improving PM assistant | Daniel Blum (PM, Melio) DevFeed: [How I turned Claude into a self-improving PM assistant | Daniel Blum (PM, Melio)]() Original publisher: [Read original article]() Author: Claire Vo Published: 2026-08-31T12:04:18Z Content type: article Language: en Sources: [Lenny's Newsletter]() Topics: [Claude](), [Notion](), [Slack](), [email](), [Artificial Intelligence](), [Automation](), [AI Infrastructure](), [User experience (UX)]() Tags: [agent-orchestration](), [automation](), [claude](), [email](), [notion](), [slack](), [ux]() ### AI overview A podcast episode in which Daniel Blum explains how he uses Claude and Cowork to manage Notion, Slack, and email workflows, automate weekly preparation, learn internal terminology, and identify improvements to his system. He also discusses scaling the setup to Melio's PM team and the remaining limitations. ### Source excerpt Listen now | 🎙 PM Daniel Blum walks through the exact Cowork and Claude setup that manages his Notion, tracks his tasks across Slack and email, and self-improves every week without him lifting a finger ## Automating quality support at scale: AI and human in the loop DevFeed: [Automating quality support at scale: AI and human in the loop]() Original publisher: [Read original article]() Author: Hugo Casademont Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [Windmill Blog]() Topics: [Artificial Intelligence](), [Claude](), [Discord](), [Slack](), [GitHub Issues](), [email](), [Linear](), [telemetry](), [WebSocket]() Tags: [ai](), [ai-windmill-support-claude](), [automated](), [claude](), [discord](), [email](), [github-issues](), [linear](), [slack](), [support](), [telemetry](), [windmill]() ### AI overview Windmill describes an internal support-automation pipeline that consolidates Discord, Slack, email, and GitHub issues into a Discord queue. It uses Claude and customer context to triage requests, draft replies and fixes, while requiring human approval before responses are sent. ### Source excerpt How does Windmill automate its own support? A Windmill pipeline funnels Discord, Slack and email tickets into one Discord queue, triages them with Claude, drafts replies, and dispatches fixes. ## Three Checks for Verifying an Agent's Email Attachment Before Sending DevFeed: [Three Checks for Verifying an Agent's Email Attachment Before Sending]() Original publisher: [Read original article]() Author: Nate Published: 2026-08-07T13:02:23Z Content type: tutorial Language: en Sources: [Nate's Substack]() Topics: [email](), [file]() Tags: [agent](), [email](), [file]() ### AI overview The article describes an agent attaching the wrong file to an email and incorrectly reporting success. It presents three checks for verifying the attachment before sending, along with a preliminary question. ### Source excerpt An agent attached the wrong file to my email and reported success. I almost hit send. Here are the three checks I run now, and the question I answer before all of them. ## How to Use Codex for Work: My Complete System at OpenAI | Jason Liu DevFeed: [How to Use Codex for Work: My Complete System at OpenAI | Jason Liu]() Original publisher: [Read original article]() Author: Peter Yang Published: 2026-07-26T13:05:16Z Content type: tutorial Language: en Sources: [Behind the Craft]() Topics: [codex](), [email](), [Slack](), [OpenAI](), [sessions](), [Learning]() Tags: [codex](), [email](), [how-to](), [openai](), [sessions](), [slack](), [tasks](), [work]() ### AI overview The article describes how Jason Liu uses Codex throughout his workday to manage Slack and email, learn from past sessions, and run long tasks with verifiable goals. ### Source excerpt How Jason uses Codex throughout his workday for managing Slack and email, learning from past sessions, and running long tasks with verifiable goals ## OpenTK: nu ook met Internetconsultaties & notificaties DevFeed: [OpenTK: nu ook met Internetconsultaties & notificaties]() Original publisher: [Read original article]() Published: 2026-07-20T11:37:00Z Content type: release Language: nl Sources: [Bert Hubert's writings]() Topics: [data](), [context](), [email]() Tags: [email](), [service]() ### AI overview OpenTK has added Internet consultations to opentk.nl, including them in its search engine and notification service. The article explains that Internet consultations are an early public stage in the development of new laws or regulations. ### Source excerpt Sinds 2024 run ik OpenTK, met als doel zo goed mogelijk te laten zien wat er in de Tweede Kamer allemaal gebeurt. En, om daar ook nuttige email-notificaties over te versturen. OpenTK is begonnen omdat ik (vanuit de Internetwereld) ineens geconfronteerd werd met een wet die over DNS (mijn hobby) ging en over een paar dagen in stemming zou komen. Dat was heel erg schrikken en ik dacht, dat kan ons nooit meer gebeuren. ## Invite Systems are an Open Relay DevFeed: [Invite Systems are an Open Relay]() Original publisher: [Read original article]() Author: Josh Sherman Published: 2026-07-19T00:00:00Z Content type: opinion Language: en Sources: [Josh Sherman]() Topics: [systems](), [email](), [Monitoring]() Tags: [email](), [monitoring](), [server](), [service](), [user]() ### AI overview The article explains how invite systems can be abused for spam when users control organization names and platforms fail to limit invitation volume. It recommends sensible invite caps and monitoring for users who reach them. ### Source excerpt Every time I think I've seen it all from spammers, they do something that surprises me. The ingenuity of bad actors is an interesting thing. I always wonder what sort of world we'd live in if their efforts were focused on good. What sucks the most is when they abuse something that's intended to bring people together. Case in point, an invite system. It exists to allow somebody the chance to get the rest of their team using a product or service. Invites wouldn't work if they said "You've been invited to platform" with no additional context. Typically the email states the name of the organization you're being invited to. "You've been invited to your organization name here". Where does that organization name come from? The user of course! And what happens if the user has ill intentions? They set the organization name to something like "Text 1-800-555-1212 for a good time", or something even sketchier than that. Generally speaking, these emails come through transactionally and from a generic email on the platform. If your system doesn't meter the number of invites, you have yourself a certified spam cannon! May as well set up an SMTP server without authentication, better known as an open mail relay. There's a few ways you can approach limits. Have a cap on the total number of pending invites? The spammer may delete pending invites to keep moving. Daily limits on total invites sent? Maybe they'll be okay with stretching their campaign over days? Probably not, most spammers are in the business of going as hard and fast as possible before they get caught. Occasionally somebody will fly below the radar, but I think that's more of a bug than a feature. Sane limits as to not get in the way of legitimate users tends to get you pretty far. Monitoring if/when somebody hits the limits is good too. Spammers usually won't write in to let you know they hit some limit. I say usually because there are some special folks out there that will come knocking. ## Promies Feedback Board: A simple way to collect user feedback in your apps DevFeed: [Promies Feedback Board: A simple way to collect user feedback in your apps]() Original publisher: [Read original article]() Author: Mike Yerou Published: 2026-05-05T10:46:53Z Content type: article Language: en Sources: [Rock and Null]() Topics: [Mobile](), [App](), [notifications](), [email](), [account]() Tags: [android](), [apps](), [email](), [extension](), [ios](), [mobile-apps](), [notifications](), [product]() ### AI overview Promies Feedback Board is a tool for mobile app developers to collect user ideas, issue reports, and feature votes in one place. It supports customizable boards, public responses, status updates, CAPTCHA-protected voting, subscriptions, statistics, and email notifications. ### Source excerpt Promies Feedback Board gives you a single, vote-protected hub to see exactly which features your users actually want. ## Silver lining playbook: Likely China-origin activity targeting US persons DevFeed: [Silver lining playbook: Likely China-origin activity targeting US persons]() Original publisher: [Read original article]() Published: 2026-02-01T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [OpenAI](), [ChatGPT](), [Social engineering](), [email](), [information retrieval]() Tags: [chatgpt](), [china](), [email](), [information-retrieval](), [openai](), [report](), [research](), [safety](), [social-engineering](), [us]() ### AI overview OpenAI describes banning a small set of likely China-origin ChatGPT accounts that used its models to research US persons and federal locations, draft social-engineering emails, and request guidance related to face-manipulation software. The activity was named "Silver Lining Playbook." ### Source excerpt OpenAI banned likely China-origin accounts using AI to research US persons, locations, and social-engineering tactics. ## How Goldcast scaled event orchestration to millions using Temporal DevFeed: [How Goldcast scaled event orchestration to millions using Temporal]() Original publisher: [Read original article]() Author: Himalaya Gahlot Published: 2026-01-20T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Orchestration](), [email](), [real-time](), [data](), [Databases]() Tags: [community](), [databases](), [email-delivery](), [infrastructure](), [legacy](), [operations](), [orchestration](), [queues](), [real-time](), [scale](), [workflows]() ### AI overview Goldcast describes how it adopted Temporal to support reliable email delivery and event duplication for large-scale marketing operations. ### Source excerpt Goldcast shares how Temporal Workflows power reliable email delivery and event duplication at scale, boosting success rates and speeding operations. ## Wrangling my email with Claude Code DevFeed: [Wrangling my email with Claude Code]() Original publisher: [Read original article]() Author: James Long Published: 2025-11-14T12:00:00Z Content type: opinion Language: en Sources: [James Long]() Topics: [Claude Code](), [email](), [Artificial Intelligence](), [MCP](), [n8n]() Tags: [ai](), [api](), [claude-code](), [email](), [mcp](), [n8n]() ### AI overview The author describes exploring AI-assisted workflows for managing an email backlog. After trying self-hosted n8n automation, they turn to Claude Code and investigate using MCP to give it access to Gmail for identifying follow-ups and organizing information about companies. ### Source excerpt I'm terrible at managing emails/DMs/etc. A lot of times it feels like trying to keep up is a full-time job in and of itself. Now that I don't have a job I finally have time to figure out a better workflow to manage life. I have a good workflow for writing notes and managing tasks in Bear, but my biggest weakness is staying on top of communication. What happens frequently is I'll have a backlog so big that I end up ignoring it, which is really bad as I miss out on opportunities or important emails. We now have AI as an incredible tool. I was always too busy to sit down and learn how to leverage AI to transform my life; it's so early and this space is super chaotic. However, I finally have time to figure out new workflows that use AI. My first attempt was to run my own instance of n8n on fly and setup some workflows for processing email. I got it working (and accidentally spammed my wife with multiple emails every hour, which she is still annoyed by), but I realized right now I don't need automations. I just need new tools to help manage my life. Next, I turned to Claude Code. I use it all the time while writing code, and I knew there was a way to extend it. So I thought of a specific use case: after announcing I left my job, I received a lot of emails from interested companies. Since I'm still dealing with some burnout, it's been difficult to stay on top of. How can AI help us here? I thought of a few questions: Which email threads should I follow-up on? Are there any important ones that I forgot to reply to? How can I more clearly see all these companies to help decide what my next step should be? I want to be able to clearly see a list of companies and info about them The first step is to give Claude Code access to my gmail. Writing a Gmail Skill to access email I've used tool calling before only when interacting with an LLM via an API. How do I give Claude Code, a product, the ability to read my email? It looked like MCP was the way to do it. Claude Code has an /m ## Postfix on Kubernetes: A Step-by-Step Email Guide DevFeed: [Postfix on Kubernetes: A Step-by-Step Email Guide]() Original publisher: [Read original article]() Author: RisingStack Engineering Published: 2025-09-25T04:12:00Z Content type: tutorial Language: en Sources: [RisingStack]() Topics: [Kubernetes](), [email](), [Authorization]() Tags: [authentication](), [email](), [guide](), [kubernetes](), [postfix](), [spoofing]() ### AI overview A step-by-step guide to running a Postfix email server on Kubernetes. It explains the infrastructure and email-authentication requirements, including a fixed outbound IP address, a domain, PTR and SPF records, and DKIM and DMARC configuration. ### Source excerpt You are in the process of putting together your application. While designing your authorization solution, you realize you will need to send emails to potential clients.Using a third-party service (like SendGrid or Mailgun) to cover your needs for now looks pretty attractive. After all, you don't have any users yet, they offer free tiers, and [...] The post Postfix on Kubernetes: A Step-by-Step Email Guide appeared first on RisingStack Engineering. ## How to Configure Leaky Bucket, GCRA, and Exponential Rate Limiters DevFeed: [How to Configure Leaky Bucket, GCRA, and Exponential Rate Limiters]() Original publisher: [Read original article]() Published: 2025-09-14T03:30:44Z Content type: tutorial Language: en Sources: [Tony Finch's blog]() Topics: [rate-limiting](), [client](), [HTTP](), [email](), [Server]() Tags: [client](), [email](), [http](), [rate-limiting](), [servers]() ### AI overview This article explains how to configure leaky bucket, GCRA, and exponential rate limiters using a limit and a period. It describes average rates, burst sizes, forgetting behavior, and an email-server example for detecting spam. ### Source excerpt Last year I wrote a pair of articles about ratelimiting: GCRA: leaky buckets without the buckets exponential rate limiting Recently, Chris "cks" Siebenmann has been working on ratelimiting HTTP bots that are hammering his blog. His articles prompted me to write some clarifications, plus a few practical anecdotes about ratelimiting email. mea culpa The main reason I wrote the GCRA article was to explain GCRA better without the standard obfuscatory terminology, and to compare GCRA with a non-stupid version of the leaky bucket algorithm. It wasn't written with my old exponential ratelimiting in mind, so I didn't match up the vocabulary. In the exponential ratelimiting article I tried to explain how the different terms correspond to the same ideas, but I botched it by trying to be too abstract. So let's try again. parameters It's simplest to configure these ratelimiters (leaky bucket, GCRA, exponential) with two parameters: limit period The maximum permitted average rate is calculated from these parameters by dividing them: rate = limit / period The period is the time over which client behaviour is averaged, which is also how long it takes for the ratelimiter to forget past behaviour. In my GCRA article I called it the window. Linear ratelimiters (leaky bucket and GCRA) are 100% forgetful after one period; the exponential ratelimiter is 67% forgetful. The limit does double duty: as well as setting the maximum average rate (measured in requests per period) it sets the maximum size (measured in requests) of a fast burst of requests following a sufficiently long quiet gap. how bursty You can increase or decrease the burst limit - while keeping the average rate limit the same - by increasing or decreasing both the limit and the period. For example, I might set limit = 600 requests per period = 1 hour. If I want to allow the same average rate, but with a smaller burst size, I might set limit = 10 requests per period = 1 minute. anecdote When I was looking after email servers ## Building in Public: How Diving Nomads Automates Coliving & Coworking Partner Outreach DevFeed: [Building in Public: How Diving Nomads Automates Coliving & Coworking Partner Outreach]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2025-08-29T05:00:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [n8n](), [Automation](), [Google Maps](), [API](), [OpenAI](), [email]() Tags: [automation](), [building-in-public](), [email](), [google](), [n8n](), [openai](), [startup-business-automation-software-development-case-study-practices-ai]() ### AI overview Diving Nomads describes an automated process for finding and contacting coliving and coworking partners near dive centers. The workflow uses Google Maps API and n8n to discover locations, stores candidates in NocoDB, applies OpenAI-based quality ratings, extracts contact emails from websites, and queues selected spaces for outreach through Brevo. ### Source excerpt At Diving Nomads, we're building something special for digital nomads who love scuba diving. Our mission is to make it easy for them to find great places to work, live, and dive -- without having to choose between beautiful dive spots and solid remote work setups. ## Digital Affairs Committee Members Face Political Uncertainty Amid Debate Over U.S. Cloud Dependence DevFeed: [Digital Affairs Committee Members Face Political Uncertainty Amid Debate Over U.S. Cloud Dependence]() Original publisher: [Read original article]() Published: 2025-08-26T06:01:23Z Content type: opinion Language: nl Sources: [Bert Hubert's writings]() Topics: [Cloud](), [Microsoft](), [Azure](), [microsoft-azure](), [email]() Tags: [azure](), [cloud](), [email](), [microsoft](), [microsoft-azure](), [politiek](), [servers](), [tech]() ### AI overview This Dutch opinion article argues that political parties are sidelining experienced members of the Dutch parliament's Digital Affairs Committee. It highlights the committee's debate over government dependence on U.S. cloud providers and says part of a planned migration of email and documents to Microsoft servers was put on hold. ### Source excerpt Als er kamerleden voor de commissie Digitale Zaken gevonden moeten worden steekt bijna niemand in Den Haag zijn of haar hand op. Want iedereen weet, het kost je je carrière als je te digitaal bent. Je partij straft je af met een lullige positie op de lijst voor de volgende verkiezingen. Dit gebeurde harde werkers Hind Dekker en Lisa van Ginneken al eerder. Inmiddels is er NerdVote.nl wat aandacht vraagt voor dit probleem! ## Building Diving Nomads: Automating Dive Center Onboarding and Memberships with No-Code Tools DevFeed: [Building Diving Nomads: Automating Dive Center Onboarding and Memberships with No-Code Tools]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2025-07-25T05:00:00Z Content type: tutorial Language: en Sources: [Tobias Mende]() Topics: [Automation](), [n8n](), [No-code](), [Low code](), [Database](), [email](), [Self-hosted](), [Notion](), [Cloud]() Tags: [automate](), [automation](), [building](), [created](), [database](), [email](), [hooks](), [low-code](), [n8n](), [no-code](), [platform](), [startup-business-automation-software-development-case-study-practices]() ### AI overview This article describes how Diving Nomads uses an automation-first stack to onboard dive centers and manage memberships. It covers scraping directories into NocoDB, sending outreach through Brevo, tracking responses with webhooks, and using n8n workflows to reduce manual work. ### Source excerpt Building Diving Nomads in Public: How We Onboard Dive Centers and Automate Memberships with (Almost) No Code TL;DR We're building a platform for digital nomads with a passion for scuba diving. Our lean, automation-first tech stack allows us to move fast, deliver value early, and maybe inspire other early-stage founders to rethink how they build. ## Dutch government email: keeping systems on government-owned servers instead of moving to Microsoft's cloud DevFeed: [Dutch government email: keeping systems on government-owned servers instead of moving to Microsoft's cloud]() Original publisher: [Read original article]() Published: 2025-06-07T18:42:36Z Content type: opinion Language: nl Sources: [Bert Hubert's writings]() Topics: [Cloud](), [Microsoft](), [email](), [servers](), [Software]() Tags: [cloud](), [email](), [microsoft](), [servers](), [software]() ### AI overview The article argues that the Dutch government should consider maintaining its email systems on government-owned servers when support for the current software ends on 14 October 2025. It describes Microsoft's promotion of migration to its US cloud and notes that nine ministries plan to acquire newer software to keep email on their own servers. ### Source excerpt De hele korte versie: De kern van de Nederlandse overheid draait nu op eigen emailservers, in eigen beheer. Op 14 oktober 2025 verloopt de ondersteuning op de gebruikte software. Microsoft stimuleert sterk om dan alle email over te dragen aan de Amerikaanse cloud, met alle gevolgen van dien. Maar het is ook mogelijk (met wat moeite) om een nieuwe versie van de email software aan te schaffen, zoals 9 ministeries van plan zijn. ## Voor de duidelijkheid: Open-Xchange DevFeed: [Voor de duidelijkheid: Open-Xchange]() Original publisher: [Read original article]() Published: 2025-02-19T20:05:11Z Content type: opinion Language: nl Sources: [Bert Hubert's writings]() Topics: [email](), [Software]() Tags: [email](), [software]() ### AI overview The author clarifies that although he previously owned shares in and worked for Open-Xchange, he has not been a shareholder since 2021, has had no substantive contact with the company for years, and has no business relationship with it. He also says he does not believe its software is suitable for the independent European communications systems he advocates. ### Source excerpt Recent ben ik (te?) veel in het nieuws over het belang van het hebben van zelfstandige communicatiemogelijkheden in Nederland en Europa. Mogelijkheden die niet afhankelijk zijn van de goede wil van Amerikanen. En waarbij die ook niet mee kunnen lezen. Op mijn homepage kan je al jaren lezen dat ik vroeger aandeelhouder was van het Duitse bedrijf Open-Xchange. Open-Xchange maakt emailplatformen, met name voor telefoonmaatschappijen en internetbedrijven. Je zou nu kunnen denken, Bert promoot Europese communicatiemogelijkheden omdat hij Open-Xchange wil promoten. ## Shifting Cyber Norms: Microsoft security POST-ing to you DevFeed: [Shifting Cyber Norms: Microsoft security POST-ing to you]() Original publisher: [Read original article]() Published: 2025-01-23T11:42:25Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [Security](), [email](), [Microsoft](), [JavaScript](), [Single-page application (SPA)]() Tags: [cybersecurity](), [email](), [javascript](), [microsoft](), [programming](), [scanners](), [security]() ### AI overview The article argues that Microsoft and other email security scanners now visit links in transmitted email and execute their JavaScript, including requests that trigger POST actions. It reports that this behavior can invalidate single-use passwordless sign-on and email-confirmation links, and discusses changing norms around email inspection and software behavior. ### Source excerpt tl;dr: Microsoft and other email security scanners will visit the links in email you transmit, and run the JavaScript in those links, including calls that lead to POSTs going out. This used to be unacceptable, since POSTs have side effects. Yet here we are. This breaks even somewhat sophisticated single-use sign-on / email confirmation messages. Read on for how to deal with this, and some thoughts on how we should treat gatekeepers like Microsoft that can randomly break things & get away with it. ## Welkom bij OpenTK (deel 2): de monitors DevFeed: [Welkom bij OpenTK (deel 2): de monitors]() Original publisher: [Read original article]() Published: 2024-12-13T14:13:41Z Content type: tutorial Language: nl Sources: [Bert Hubert's writings]() Topics: [API](), [monitor](), [Open Data](), [email](), [Open Source](), [account](), [Internet]() Tags: [account](), [api](), [data](), [email](), [internet](), [monitor](), [open-source](), [opentk](), [politiek](), [project]() ### AI overview This Dutch article explains how OpenTK uses the Tweede Kamer's technical API and open parliamentary data to help users monitor committees, people, dossiers, searches, cases, and activities. Users can link an email address to receive matching-document notifications, with duplicate matches combined into a single email. ### Source excerpt Welkom! Goed inzicht in ons parlement is belangrijk, soms omdat er dingen in het nieuws zijn. En soms juist omdat dingen (nog) niet in het nieuws zijn, maar er binnenkort wel besluiten over genomen gaan worden. De Tweede Kamer publiceert alles wat ze doen via een technische API, en dat is echt geweldig. Hierdoor kunnen we op Internet eigen viewers maken om deze data zo goed mogelijk zichtbaar te maken. [Next page]()