<![CDATA[Daniel Moya]]>https://danimoya.hashnode.devRSS for NodeThu, 29 Oct 2026 00:47:45 GMT60<![CDATA[Three ways to move a Confluence space into LiveWiki (and what I'd check first)]]>https://danimoya.hashnode.dev/three-ways-to-move-a-confluence-space-into-livewiki-and-what-i-d-check-firsthttps://danimoya.hashnode.dev/three-ways-to-move-a-confluence-space-into-livewiki-and-what-i-d-check-firstThu, 22 Oct 2026 09:40:58 GMTI'm Daniel Moya, the developer of LiveWiki. This post covers how its Confluence import works.

LiveWiki accepts Confluence content three ways: an XML export, an HTML export, or directly through the Confluence Cloud API. MediaWiki sites import from their XML export.

What I'd check before migrating

  1. Start with your most-viewed pages, not the whole space.
  2. After import, look at each page's AI staleness score. It lists reasons a page may be out of date, which gives you a review list instead of a guess.
  3. Ask a few real questions. Answers come only from published pages and link their source, so a wrong answer points straight at the page to fix.
  4. Turn on the team: co-editing is real time, and AI edits stay drafts until a person approves them.

Try it: open the sample workspace at https://livewiki.foor.tech (no signup) to see imported pages, staleness reasons and sourced answers. If it fits, the free plan covers up to 5 members, or take the 30-day trial with no card.

– Daniel Moya, developer

]]><![CDATA[The 6 checks I run before sending a single cold email]]>https://danimoya.hashnode.dev/the-6-checks-i-run-before-sending-a-single-cold-emailhttps://danimoya.hashnode.dev/the-6-checks-i-run-before-sending-a-single-cold-emailSun, 18 Oct 2026 11:41:06 GMTYou wrote the email, picked the list, and hit send. A week later the replies are near zero and you can't tell whether people ignored you or never saw it. Usually it's the second one. Here's the checklist I go through before any cold campaign:

  1. SPF: dig TXT yourdomain.com should return exactly one v=spf1 ... record that includes every service sending for you, ending in ~all or -all. Two SPF records means SPF fails.
  2. DKIM: find your provider's selector (for example google._domainkey) and run dig TXT selector._domainkey.yourdomain.com. No key means mail you can't prove is yours.
  3. DMARC: dig TXT _dmarc.yourdomain.com. Start at p=none; rua=mailto:... so you get reports, then move to quarantine once things line up.
  4. MX: the sending domain needs working MX records. A domain that can't receive mail looks disposable.
  5. Spam words and formatting: words like "free!!!", "guaranteed", all-caps subject lines, image-only emails and link shorteners all hurt.
  6. Warm-up and throttling: a new mailbox sending 200 emails on day one is a red flag. Ramp up slowly and spread sends through the day.

Try this today: run the three dig commands above on your sending domain before your next campaign. It's a short check, and it can save the whole send.

Disclosure: I'm the developer of MarkOn, an AI SDR in free private beta. It runs these SPF/DKIM/DMARC, MX, spam-word, warm-up and throttling checks for you, then writes personalised sequences without templates. If you'd rather not run dig by hand, it's a private beta: leave a comment and I'll send you an invite.

]]>