Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/HistoPol/statuses/113216267719509676">HistoPol (#HP) 🥥 🌴 (histopol@mastodon.social)'s status on Sunday, 29-Sep-2024 02:05:49 JST</a><a href="https://mastodon.social/@HistoPol" title="histopol@mastodon.social"><img src="https://gnusocial.jp/avatar/44595-48-20221221005726.webp" width="48" height="48" alt="HistoPol (#HP) 🥥 🌴" style="position: absolute; left: 0; top: 0;">HistoPol (#HP) 🥥 🌴</a><div><a href="https://gnusocial.jp/notice/7327864" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/80908" title="elan@publicsquare.global">Elan Hasson</a></li><li><a href="https://gnusocial.jp/user/80909" title="jamesbritt@mastodon.social">James Britt</a></li><li><a href="https://gnusocial.jp/user/101909" title="weirdwriter@tweesecake.social">Robert Kingett backup</a></li></ul></div></section><article><p><a href="https://tweesecake.social/@weirdwriter">@weirdwriter</a> <a href="https://mastodon.world/@MoiraEve">@MoiraEve</a> <a href="https://publicsquare.global/@elan">@elan</a> <a href="https://mastodon.social/@jamesbritt">@jamesbritt</a> </p><p>(2/2)</p><p>...don't use <a href="https://mastodon.social/tags/camelcase" rel="tag">#camelcase</a>  as I think it looks weird.)*</p><p><a href="https://www.freecodecamp.org/news/snake-case-vs-camel-case-vs-pascal-case-vs-kebab-case-whats-the-difference/" rel="nofollow noreferrer">https://www.freecodecamp.org/news/snake-case-vs-camel-case-vs-pascal-case-vs-kebab-case-whats-the-difference/</a></p><p>Now that we've got this paragraph issue settled, how about my two examples, are <a href="https://mastodon.social/tags/UShistory" rel="tag">#UShistory</a> or <a href="https://mastodon.social/tags/USpol" rel="tag">#USpol</a> o.k. for you to listen to or do you need <a href="https://mastodon.social/tags/USHistory" rel="tag">#USHistory</a> and <a href="https://mastodon.social/tags/USPol" rel="tag">#USPol</a>? Especially the second one can be misleading for sighted people, as USP (Unique Selling Proposition) is actually a much used acronym, therefore I prefer my personal slight variation.</p><p>//</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/923355#notice-7327871">In conversation</a><time datetime="2024-09-29T02:05:49+09:00" title="Sunday, 29-Sep-2024 02:05:49 JST">about 2 months ago</time> <span>from <span><a href="https://mastodon.social/@HistoPol/113216267719509676" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@HistoPol/113216267719509676">permalink</a></footer></blockquote>

Corresponding Notice

Embed this notice
HistoPol (#HP) 🥥 🌴 (histopol@mastodon.social)'s status on Sunday, 29-Sep-2024 02:05:49 JSTHistoPol (#HP) 🥥 🌴
in reply to
@weirdwriter @MoiraEve @elan @jamesbritt
(2/2)
...don't use #camelcase as I think it looks weird.)*
https://www.freecodecamp.org/news/snake-case-vs-camel-case-vs-pascal-case-vs-kebab-case-whats-the-difference/
Now that we've got this paragraph issue settled, how about my two examples, are #UShistory or #USpol o.k. for you to listen to or do you need #USHistory and #USPol? Especially the second one can be misleading for sighted people, as USP (Unique Selling Proposition) is actually a much used acronym, therefore I prefer my personal slight variation.
//
In conversationabout 2 months ago from mastodon.socialpermalink

Public

Embed Notice

HTML Code

Corresponding Notice