Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://ngmx.com/users/sindarina/statuses/110598224405314735">Sindarina, Edge Case Detective (sindarina@ngmx.com)'s status on Friday, 30-Jun-2023 17:08:06 JST</a><a href="https://ngmx.com/@sindarina" title="sindarina@ngmx.com"><img src="https://gnusocial.jp/avatar/102235-48-20230329174946.webp" width="48" height="48" alt="Sindarina, Edge Case Detective" style="position: absolute; left: 0; top: 0;">Sindarina, Edge Case Detective</a><div><a href="https://ngmx.com/@sindarina/110598199724246507" rel="in-reply-to">in reply to</a></div></section><article><p>The same goes for domain names; do NOT use a public domain name you do not control in your configuration, documentation, or UI language.</p><p>Instead, use one of the available reserved domain names documented in RFC 2606, such as 'example.com', 'example.net', or the .example top-level domain.</p><p>❌ test.com<br>❌ yourdomain.com<br>✅ example.com<br>✅ yourdomain.example</p><p>Pass it on to your fellow developers, designers, documentation writers, and so forth.</p><p>Full RFC text is here;</p><p><a href="https://datatracker.ietf.org/doc/rfc2606/" rel="nofollow noreferrer">https://datatracker.ietf.org/doc/rfc2606/</a></p><p>2/ 🧵</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/1686462#notice-3356068">In conversation</a><time datetime="2023-06-30T17:08:06+09:00" title="Friday, 30-Jun-2023 17:08:06 JST">Friday, 30-Jun-2023 17:08:06 JST</time> <span>from <span><a href="https://ngmx.com/@sindarina/110598224405314735" rel="external" title="Sent from ngmx.com via ActivityPub">ngmx.com</a></span></span><a href="https://ngmx.com/@sindarina/110598224405314735">permalink</a><h4>Attachments</h4><ol><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="http://example.com/">Example Domain</a></h5><div></div></header><div></div><footer></footer></article></li><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="http://example.net/">Example Domain</a></h5><div></div></header><div></div><footer></footer></article></li><li><label><a rel="external" href="https://gnusocial.jp/attachment/1181060">Untitled attachment</a></label><br></li><li><article><header><div>Domain not in remote thumbnail source whitelist: cdn.sedo.com</div><h5><a href="http://yourdomain.com/">yourdomain.com is available for purchase - Sedo.com</a></h5><div></div></header><div></div><footer></footer></article></li><li><label><a rel="external" href="https://gnusocial.jp/attachment/1181062">Untitled attachment</a></label><br></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Sindarina, Edge Case Detective (sindarina@ngmx.com)'s status on Friday, 30-Jun-2023 17:08:06 JST Sindarina, Edge Case Detective
in reply to
The same goes for domain names; do NOT use a public domain name you do not control in your configuration, documentation, or UI language.
Instead, use one of the available reserved domain names documented in RFC 2606, such as 'example.com', 'example.net', or the .example top-level domain.
❌ test.com
❌ yourdomain.com
✅ example.com
✅ yourdomain.example
Pass it on to your fellow developers, designers, documentation writers, and so forth.
Full RFC text is here;
https://datatracker.ietf.org/doc/rfc2606/
2/ 🧵
In conversationFriday, 30-Jun-2023 17:08:06 JST from ngmx.compermalink
Attachments
1. No result found on File_thumbnail lookup.
  Example Domain
2. No result found on File_thumbnail lookup.
  Example Domain
3. Untitled attachment
4. Domain not in remote thumbnail source whitelist: cdn.sedo.com
  yourdomain.com is available for purchase - Sedo.com
5. Untitled attachment

Public

Embed Notice

HTML Code

Corresponding Notice