Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/folkerschamel/statuses/111595025554128251">Folker (folkerschamel@mastodon.social)'s status on Sunday, 17-Dec-2023 18:28:24 JST</a><a href="https://mastodon.social/@folkerschamel" title="folkerschamel@mastodon.social"><img src="https://gnusocial.jp/avatar/18937-48-20221107104209.webp" width="48" height="48" alt="Folker" style="position: absolute; left: 0; top: 0;">Folker</a><div><ul><li><li><a href="https://gnusocial.jp/user/89924" title="tokyo_0@mas.to">Tokyo Outsider (337ppm)</a></li><li><a href="https://gnusocial.jp/user/93192" title="tay@tech.lgbt">Proxfox Virtual Environment 🦊</a></li></ul></div></section><article><p><a href="https://mas.to/@tokyo_0">@tokyo_0</a> <a href="https://mastodon.social/@Gargron">@Gargron</a> <a href="https://tech.lgbt/@tay">@tay</a> </p><p>Yea, but these "significant considerations" should be based on solid technical information and not just rumors or even misinformation about how things work.</p><p>I am full with <a href="https://mastodon.social/@Gargron">@Gargron</a> on clarifying technical misconceptions.</p><p>That was the reason for <a href="https://mastodon.social/@Gargron">@Gargron</a> follow-up in the first place.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2459059#notice-4876312">In conversation</a><time datetime="2023-12-17T18:28:24+09:00" title="Sunday, 17-Dec-2023 18:28:24 JST">about a year ago</time> <span>from <span><a href="https://mastodon.social/@folkerschamel/111595025554128251" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@folkerschamel/111595025554128251">permalink</a></footer></blockquote>

Corresponding Notice

Embed this notice
Folker (folkerschamel@mastodon.social)'s status on Sunday, 17-Dec-2023 18:28:24 JSTFolker
@tokyo_0 @Gargron @tay
Yea, but these "significant considerations" should be based on solid technical information and not just rumors or even misinformation about how things work.
I am full with @Gargron on clarifying technical misconceptions.
That was the reason for @Gargron follow-up in the first place.
In conversationabout a year ago from mastodon.socialpermalink

Public

Embed Notice

HTML Code

Corresponding Notice