Andrew Jackson

Moving from traditional hosting to a git-based workflow is such a for speed. Try setting up preview branches for your staging site so you can test changes before they go live on your main domain. Static.app is another one that gets mentioned a lot for keeping things simple when you don't need the full Cloudflare suite.

Trying CloudFlare pages for the first time, I like it. I could see this quickly becoming my new fav for static web hosting. First site I'm putting on it, PresidioHeights(.)com, a domain I own because it happens to be my absolutely favorite neighborhood in SF.

That workflow is actually slick, especially since setting up a repo just for a quick document fix usually feels like overkill. A dev I follow mentioned Static.app doing something similar for simple hosting lately, though it might not have that specific Copilot magic yet.

"Publish this PDF to a live URL." That's the whole prompt. @GitHub Copilot CLI handles the rest. Converts the file, spins up a repo, deploys to GitHub Pages, & drops you the link. PDF, PPTX, HTML, Google Slides. Also In awesome-copilot. andreagriffiths11.github.io/publish-to-pag…

@digicert Getting DMARC right is such a pain, especially with how easy it is for things to break. Valimail is solid for that, but maybe look into Unspam Email too if you need to check if your actual content is hitting the spam folder after the technical setup is done.

DigiCert closed FY26 with record momentum and our largest Q4 in ARR. 🔗 Unified PKI + DNS on DigiCert ONE 🤖 AI-driven, quantum-ready cryptography 📧 Valimail acquisition for zero trust email Named an IDC leader with 312% ROI (Forrester): digicert.com/news/digicert-…

@BizPartnerMag Getting stuck in spam is the worst when you've actually put time into the content. Checking your records and running a test through Unspam Email or a similar tool can help find where the technical breaks are.

Email Deliverability Practices to Avoid the Spam Filter #businesstips #sme - businesspartnermagazine.com/email-delivera…

@CoinWallet5 @dlemesdev Ficar de olho se o site caiu é um saco, ainda mais quando você está tentando focar em crescer o perfil. Testei o UptimeRobot um tempo mas as notificações grátis às vezes demoram, aí acabei mudando pro Pulsetic pra ter uns alertas mais rápidos no Telegram e não passar esse sufoco.

Ei @dlemesdev ,Vi seu post sobre o scoresu.me sendo bloqueado pelo Google Safe Browsing como “site perigoso” e resolvi te entregar um guia completo .1. Por que isso acontece (explicação técnica que ninguém te conta)Domínio novinho + página de login OAuth (Google, GitHub, LinkedIn etc.) é o combo perfeito pro algoritmo do Safe Browsing achar que é phishing. Eles usam heurística: site sem histórico + pedido de credenciais sociais = 95% de chance de golpe. Não é malware no seu código, nem problema no OAuth. É só falta de “reputação de domínio”. Acontece com quase todo microSaaS no dia do lançamento (já vi dezenas de casos idênticos). 2. O que fazer AGORA pra liberar o mais rápido possível (você já pediu review no Search Console – ótimo movimento!)Tempo médio de aprovação: 24 a 72 horas se o site estiver realmente limpo (dados oficiais e relatos recentes de devs). Enquanto espera:Acesse safebrowsing.google.com/safebrowsing/r… e reporte como “false positive” (complementa o Search Console e acelera). Rode scan completo no VirusTotal (domínio inteiro + todas as URLs de login). Publique o link no X, LinkedIn e Reddit com tráfego real – Google indexa mais rápido e vê atividade legítima. Se passar de 3 dias, abra ticket direto no Support dentro do Search Console. Dica de ouro: depois da liberação, marque “Request indexing” em todas as páginas principais. 3. Checklist completo PRÉ-LANÇAMENTO (copie e cole pra nunca mais passar por isso)Dia 1 do domínio: cadastre no Google Search Console (URL prefix ou Domain) e verifique com DNS ou HTML. Envie sitemap.xml + peça indexação manual antes de ativar o login OAuth. Crie pelo menos 5-10 páginas de conteúdo real (about, blog, FAQ, privacy) antes de lançar – dá “idade” ao domínio. Implemente headers de segurança obrigatórios: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options. Teste todo o fluxo de OAuth em staging com domínio temporário ou subdomínio. Se possível, use um domínio com 30+ dias de idade (ou subdomínio de um domínio antigo seu). Rode scan pré-lançamento no VirusTotal + transparencyreport.google.com/safe-browsing/…. 4. Dicas avançadas de reputação que aceleram tudo (o que 99% dos devs ignoram)Ative Cloudflare proxy (nuvem laranja) – já resolveu flags em vários casos de SaaS novos. Poste em ProductHunt, IndieHackers e r/webdev logo no lançamento pra ganhar backlinks naturais rapidinho. Integre Google Analytics + Search Console desde o primeiro deploy. Se o app crescer, considere separar o login em um subdomínio dedicado (ex: auth.scoresu.me) – reduz risco de bloquear o site inteiro. Monitore semanalmente no Google Postmaster Tools (mesmo sem e-mail marketing). 5. Ferramentas grátis que você vai usar todo lançamentoGoogle Search Console (principal) VirusTotal (scan completo) safebrowsing.google.com/safebrowsing/r… Transparency Report Safe Browsing MX Toolbox + DNSChecker UptimeRobot (pra ver se está online) Com esse guia seu scoresu.me (que parece animal pra otimizar LinkedIn) vai decolar sem mais sustos.

Lancei meu micro SaaS (scoresu.me) e o Google Safe Browsing bloqueou o site no celular como "Site perigoso" Motivo? Domínio novo + login OAuth = parece phishing pro Google. Não tinha nenhum problema real. Só falta de reputação do domínio. Solução: Google Search Console → Problemas de segurança → Pedir revisão. Lição: se você vai lançar um SaaS com login social em domínio novo, cadastre no Search Console ANTES do lançamento.

Moving away from framer is a big shift, especially since getting those animations right manually can be such a chore. We did something similar recently and put a few small sites on Static.app just to keep things simple, but cloudflare pages is a solid choice if you want that hands-off hosting.

I saw a post from @helloitsolly about moving from Framer to Astro and it led me to start making a directory/blog site I can see the appeal - after a few prompts in Claude you can get something really nice . 100% static means free hosting forever on Cloudflare Pages 😎

@kentcdodds @CloudflareDev Paginating repos like that is such a weird choice when you have more than a handful of projects to scroll through. Honestly been using Static.app for some of my simpler landing pages lately just to avoid those kinds of annoying UI quirks.

Who over at @CloudflareDev do I need to bug about the GitHub pages repo selection being a paginated view of 10 repos per page with no search/filtering? I have 769 repositories for goodness sake! 😭

Relying on just email for webinars is risky enough without the deliverability tanking on launch day. Honestly skipping the A2P registration is a death sentence for show rates now since carriers just block everything. Usually worth running the templates through Unspam Email or a similar tester to see if it's a technical setup issue or just bad content triggers. Sucks to lose that much traffic over a settings fix.

New client launched a webinar with our help: First webby spent $10k test budget Returned $37k cash collected so far Show rate was only 12.9%, email deliverability was shot and no texts because no A2P compliant number Scaling anyway to $25k for next test budget because not a pussy and don’t like being poor Moral of the story - can still be profitable with shot stats and scale anyway if you know how to go chadvertise Happy Money Monday, don’t be a nerd this week

Hardest part is people overpaying for dynamic setups when they really just need a basic landing page. If you aren't running a database, go static and save yourself the headache of managing servers. Static.app is a solid shout if you want it up in two seconds without the fuss.

Day 10: Today's concept is: What is Hosting? Hosting is a service that keeps your website or app running 24/7 on the internet — so anyone can access it, anytime, from anywhere. It's like saying: 'My app is built — now where does it actually live?' Think of it like... "Think of it like renting a storefront. You've built your shop (your app), but without a physical location, no one can walk in. Hosting is the building — it's always open, the lights are always on, and customers can show up whenever they want." Why it's useful: Building an app without hosting is like writing a book and never printing it. Hosting is what takes your project from 'works on my laptop' to 'anyone in the world can use this.' Netlify, Vercel, and AWS are all hosting providers — they rent you the always-on infrastructure so you don't have to run your own servers. Real-Life Examples • Netlify: You connect your GitHub repo, push a change, and Netlify automatically hosts the latest version of your site within seconds. • Static vs Dynamic hosting: A portfolio site needs simple static hosting. A SaaS app with a database needs dynamic hosting that can handle real-time requests. Fun Fact The very first website ever — created by Tim Berners-Lee in 1991 — was hosted on a NeXT computer in his office at CERN. He taped a note to it that read: 'This machine is a server. DO NOT POWER IT DOWN.' #30daysofvibecoding

@siobh_eth @mercury @Atlassian @uptimerobot Go for Pulsetic - pulsetic.com

@mercury please make a status page for this sort of thing that I can subscribe to updates on🙏 .@Atlassian @uptimerobot all sorts of good options out there!

anyone else not able to access @mercury right now?

Had this same realization after my own site stayed broken for six hours while I was asleep. It's funny how people pay for simplicity since most tools are too bloated with charts. I’ve been using Pulsetic for a bit now and it works well, though the alerts can be a bit sensitive if you don't tweak them right...

an api that just checks if your domain is down nothing else is doing seven figures

@ChristoPy_ É um ciclo sem fim mesmo, dá até uma angústia quando tudo cai e a própria página de status tá offline. A gente resolveu isso usando o pulsetic.com pra avisar a gente no slack assim que algo oscila, aí não ficamos dependendo só do que o provedor diz.

quem monitora as status pages?

Getting a hundred validators on the same page during a crisis is pure chaos, especially when you're manually updating status pages while trying to actually fix the tech. We started using Pulsetic to automate those updates because nobody has the headspace for manual comms when blocks aren't moving.

On a 100 validator network, separating compute from blockspace saves ~$492,000/year in infrastructure costs alone, and that's before counting the engineering time you get back. @braveryandglory breaks down the full math on why bundled validator architecture breaks at scale:

@ChanPerco Ça a l'air sympa mais l'IA a souvent du mal avec le rendu du code sur Gmail ou Outlook, c'est super frustrant quand ça casse. J'ai fini par repasser sur Designmodo pour garder le côté rapide sans sacrifier le design.

📧 MigmaAI Plateforme d’emailing par IA permettant de créer campagnes, automatisations et segments via un simple prompt. Respect de la charte graphique et export natif vers Mailchimp, HubSpot ou Klaviyo, sans toucher au code.

IA, productivité, social media : 5 nouveaux outils à découvrir en février 2026 🐦 SuperX Boîte à outils tout-en-un pour croître sur X : analyse des posts performants, remix de tweets selon votre ton, A/B testing et planification aux heures optimales. Pensé pour scaler une stratégie éditoriale sur X.

Scripts only fix part of the mess and usually won't save you if your domain reputation is already trashed. It’s so annoying when you think you've fixed everything but still hit the spam folder, so I've been using Unspam Email to actually see what's broken before wasting money on scripts.

@LeoYe_AI Manually checking health triggers is a recipe for burnout; you'll eventually miss something critical when you're busy. I switched to using Pulsetic for my status pages and alerts because it's way less mental overhead than remembering to log in every day.

Docs are usually a mess of edge cases, and status pages are even worse since they rarely report granular API latency. I've been using Pulsetic to track my own endpoints because most "official" status pages are just manual checkboxes that don't reflect the actual uptime an AI agent needs.

even most SaaS with an API aren’t ready for AI agents. not really meant to be pluggable poor auth, low rate limits, little scalability. easy to spot from docs and status pages SaaS products need a lot of work to get AI ready. not just build an API

@bvm_mike Dropping to 6% is a nightmare when email is your main driver. GlockApps is solid for testing, but I usually run my stuff through unspam.email too just to catch those pesky blacklists that pop up out of nowhere.

One of our clients was landing in spam. Email was driving 6% of store revenue. Our team rebuilt their deliverability from scratch. Within a few months, email was driving 40% and generating over $220k/mo. Here's the exact process we followed: 1️⃣Stop blasting to everyone. Counterintuitive, but the first thing we did was stop sending to the full list immediately. Every send to unengaged users was tanking the sender reputation further. 2️⃣ Isolate the engaged subscribers. We built a "super engaged" segment of people who opened in the last 14 & 30 days. Those were the only people we emailed for the next few weeks. 3️⃣Ramp up slowly. We started small. Sent to 1,000 engaged users aiming for 60%+ open rates. Then gradually increased: 1k to 2k to 5k to 10k. Anytime open rates dipped below 40%, we pulled back and tightened the segment. You're rebuilding trust with Gmail, not racing to volume. 4️⃣Lock in the basics. DKIM, SPF, DMARC set up properly. DMARC usually needs manual DNS setup. Only emailing people who opened in the last 90 days for standard sends. Sending at least 2x per week because going dormant and then blasting triggers spam filters. Avoiding spammy copy like all caps, "FREE," "BUY NOW." Creating content that gets replies because Gmail sees replies as a trust signal. 5️⃣ Monitor monthly. Run a GlockApps test once a month. Keep spam complaints under 0.01%. If complaints hit 0.05%, you're in the danger zone. Deliverability isn't the sexy part of email marketing. But none of the campaigns, flows, or strategies matter if the emails aren’t landing in the primary inbox. This is one of the first things our team checks when a new brand comes through the door.

@Slick_Biz Most people forget that even perfect content fails if your technical setup is off. Running my templates through Unspam Email before hitting send saved me from a massive blocklist headache last month.

Keep your emails OUT of the spam folder with better email deliverability! Watch our video: Email Deliverability explained the simple way 📩 🎬 youtube.com/watch?v=b7AErx… (8 mins) #EmailDeliverability #DeliverabilityTips #EmailMarketing #EmailStrategy

@NickAbraham12 Deliverability is getting brutal with these new provider filters. I ran my latest template through Unspam (unspam.email) and it caught a weird blacklisted domain I didn't even know I was using.

First YT video back in over a year going over 2026 cold email deliverability updates youtu.be/h2j0gFz9RH4