Recent searches

No recent searches

Search options

Only available when logged in.
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

269
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.2

#functionality

0 posts0 participants0 posts today
xoron :verified:<p><a href="https://infosec.exchange/tags/Decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Decentralized</span></a> <a href="https://infosec.exchange/tags/Module" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Module</span></a> <a href="https://infosec.exchange/tags/Federation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Federation</span></a> <a href="https://infosec.exchange/tags/Microfrontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microfrontend</span></a> <a href="https://infosec.exchange/tags/Architecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Architecture</span></a> </p><p>I'm working on a <a href="https://infosec.exchange/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webapp</span></a> and I'm being <a href="https://infosec.exchange/tags/creative" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>creative</span></a> on the <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>approach</span></a>. It might be considered <a href="https://infosec.exchange/tags/overcomplicated" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>overcomplicated</span></a> (because it is), but I'm just trying something out. It's entirely possible this approach won't work <a href="https://infosec.exchange/tags/longterm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>longterm</span></a>. I see it as there is <a href="https://infosec.exchange/tags/onewaytofindout" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>onewaytofindout</span></a>. I don't recommend this approach. Just sharing what I'm trying/#investigating.</p><p>How it will be <a href="https://infosec.exchange/tags/architected" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>architected</span></a>: [<a href="https://positive-intentions.com/blog/decentralised-architecture](https://positive-intentions.com/blog/decentralised-architecture)" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">positive-intentions.com/blog/d</span><span class="invisible">ecentralised-architecture](https://positive-intentions.com/blog/decentralised-architecture)</span></a><br>Some <a href="https://infosec.exchange/tags/benefits" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>benefits</span></a> of the <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>approach</span></a>: [<a href="https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure](https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure)" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">positive-intentions.com/blog/s</span><span class="invisible">tatics-as-a-chat-app-infrastructure](https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure)</span></a></p><p>I find that <a href="https://infosec.exchange/tags/modulefederation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>modulefederation</span></a> and <a href="https://infosec.exchange/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>microfrontends</span></a> to generally be <a href="https://infosec.exchange/tags/discouraged" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>discouraged</span></a> when I see posts, but I think it works for me in my <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>approach</span></a>. I'm <a href="https://infosec.exchange/tags/optimistic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>optimistic</span></a> about the approach and the <a href="https://infosec.exchange/tags/benefits" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>benefits</span></a> and so I wanted to <a href="https://infosec.exchange/tags/share" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>share</span></a> details.</p><p>When I serve the <a href="https://infosec.exchange/tags/federatedmodules" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>federatedmodules</span></a>, I can also host the <a href="https://infosec.exchange/tags/storybook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>storybook</span></a> statics so I think this could be a good way to <a href="https://infosec.exchange/tags/document" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>document</span></a> the modules in <a href="https://infosec.exchange/tags/isolation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>isolation</span></a>.</p><p><a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cryptography</span></a> modules - <a href="https://cryptography.positive-intentions.com/?path=%2Fdocs%2Fcryptography-introduction--docs" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cryptography.positive-intentio</span><span class="invisible">ns.com/?path=%2Fdocs%2Fcryptography-introduction--docs</span></a></p><p><a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P2P</span></a> framework - <a href="https://p2p.positive-intentions.com/?path=%2Fdocs%2Fe2e-tests-connectionstatus--docs" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">p2p.positive-intentions.com/?p</span><span class="invisible">ath=%2Fdocs%2Fe2e-tests-connectionstatus--docs</span></a></p><p>This way, I can create <a href="https://infosec.exchange/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>microfrontends</span></a> that consume these <a href="https://infosec.exchange/tags/modules" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>modules</span></a>. I can then <a href="https://infosec.exchange/tags/share" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>share</span></a> the <a href="https://infosec.exchange/tags/functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>functionality</span></a> between <a href="https://infosec.exchange/tags/apps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>apps</span></a>. The following apps are using a different codebase from each other (there is a <a href="https://infosec.exchange/tags/distinction" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>distinction</span></a> between these apps in <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> and <a href="https://infosec.exchange/tags/closesource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>closesource</span></a>). Sharing those <a href="https://infosec.exchange/tags/dependencies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dependencies</span></a> could help make it easier to roll out <a href="https://infosec.exchange/tags/updates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>updates</span></a> to <a href="https://infosec.exchange/tags/coremechanics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coremechanics</span></a>.</p><p><a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P2P</span></a> chat - [<a href="https://chat.positive-intentions.com/](https://chat.positive-intentions.com/)" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">chat.positive-intentions.com/]</span><span class="invisible">(https://chat.positive-intentions.com/)</span></a><br><a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P2P</span></a> file transfer - [<a href="https://file.positive-intentions.com/](https://file.positive-intentions.com/)" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">file.positive-intentions.com/]</span><span class="invisible">(https://file.positive-intentions.com/)</span></a></p><p>The <a href="https://infosec.exchange/tags/functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>functionality</span></a> also works when I create an <a href="https://infosec.exchange/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Android</span></a> build with <a href="https://infosec.exchange/tags/Tauri" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tauri</span></a>. This could also lead to it being easier to create <a href="https://infosec.exchange/tags/newapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>newapps</span></a> that could use the <a href="https://infosec.exchange/tags/modules" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>modules</span></a> created.</p><p>I'm sure there will be some distinct <a href="https://infosec.exchange/tags/test" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>test</span></a>/#maintenance <a href="https://infosec.exchange/tags/overhead" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>overhead</span></a>, but depending on how it's <a href="https://infosec.exchange/tags/architected" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>architected</span></a> I think it could work and make it easier to <a href="https://infosec.exchange/tags/improve" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>improve</span></a> on the current <a href="https://infosec.exchange/tags/implementation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>implementation</span></a>.</p><p>Everything about the <a href="https://infosec.exchange/tags/project" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>project</span></a> is far from finished. It could be seen as this is a <a href="https://infosec.exchange/tags/complicated" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>complicated</span></a> way to do what <a href="https://infosec.exchange/tags/npm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>npm</span></a> does, but I think this <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>approach</span></a> allows for greater <a href="https://infosec.exchange/tags/flexibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>flexibility</span></a> by being able to <a href="https://infosec.exchange/tags/separate" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>separate</span></a> <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> and <a href="https://infosec.exchange/tags/closesource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>closesource</span></a> code for the <a href="https://infosec.exchange/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>web</span></a>. (Of course as <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>javascript</span></a>, it will always be "source code available". Especially in the age of <a href="https://infosec.exchange/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a>, I'm sure it's possible to <a href="https://infosec.exchange/tags/reverseengineer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reverseengineer</span></a> it like never before.)</p><p>(mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)</p>
RaymondPierreL3<p><span class="h-card" translate="no"><a href="https://mastodon.social/@keyboards" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>keyboards</span></a></span> <br>A portable… precursor to laptops. There is something ‘organic’ about early personal computers which is totally lacking in modern appliances. The balance between functionality and form is somewhat skewed to the wrong side methinks.</p><p><a href="https://aus.social/tags/Design" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Design</span></a> <a href="https://aus.social/tags/Form" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Form</span></a> <a href="https://aus.social/tags/Functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Functionality</span></a> <a href="https://aus.social/tags/PersonalComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PersonalComputing</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.world/@ginaintheburg" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ginaintheburg</span></a></span> the sheer fact that <a href="https://infosec.space/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chrome</span></a> has that <a href="https://infosec.space/tags/functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>functionality</span></a> <em>is</em> <a href="https://infosec.space/tags/evidence" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>evidence</span></a> for <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Govware</span></a>-Style <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malware</span></a> inside it.</p><ul><li>Whether that's just due to <em>"<a href="https://infosec.space/tags/GAFAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GAFAM</span></a> doing <a href="https://infosec.space/tags/PRISM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PRISM</span></a> shite"</em> or <em>"<a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudAct</span></a> / <a href="https://infosec.space/tags/LawfulInterception" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LawfulInterception</span></a> compliance"</em> is irrelevant for that assessment!</li></ul><p><em>SHITE LIKE THIS</em> is why I use <span class="h-card" translate="no"><a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>torproject</span></a></span> / <a href="https://infosec.space/tags/TorBrowser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TorBrowser</span></a> as my Default <a href="https://infosec.space/tags/Browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Browser</span></a>!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@donwatkins" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>donwatkins</span></a></span> Personally I would've considered <a href="https://infosec.space/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a> to be leading here because they pit <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> first and sacrifice <a href="https://infosec.space/tags/functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>functionality</span></a> and <a href="https://infosec.space/tags/speed" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>speed</span></a> for that goal!</p>
Andrew Shields<p>A Japanese lantern lit by gas in Marcel Proust's "Du côté de chez Swann" (1913). <a href="https://mas.to/tags/111Words" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>111Words</span></a> <a href="https://mas.to/tags/MarcelProust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MarcelProust</span></a> <a href="https://mas.to/tags/DuC%C3%B4t%C3%A9DeChezSwann" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DuCôtéDeChezSwann</span></a> <a href="https://mas.to/tags/Japan" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Japan</span></a> <a href="https://mas.to/tags/France" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>France</span></a> <a href="https://mas.to/tags/Lantern" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Lantern</span></a> <a href="https://mas.to/tags/GasLight" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GasLight</span></a> <a href="https://mas.to/tags/Literature" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Literature</span></a> <a href="https://mas.to/tags/Technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Technology</span></a> <a href="https://mas.to/tags/Ornamentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ornamentation</span></a> <a href="https://mas.to/tags/Functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Functionality</span></a> <a href="https://mas.to/tags/Orientalism" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Orientalism</span></a> <a href="https://mas.to/tags/Occidentalism" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Occidentalism</span></a> <a href="https://andrewjshields.blogspot.com/2024/09/a-japanese-lantern-lit-by-gas-in-marcel.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">andrewjshields.blogspot.com/20</span><span class="invisible">24/09/a-japanese-lantern-lit-by-gas-in-marcel.html</span></a></p>
Teri Radichel<p>Back to the Basics in Cloud Product Development<br>~~<br>If your basic functionality doesn’t work, the whiz-bang features don’t matter<br>~~<br><a href="https://infosec.exchange/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cloud</span></a> <a href="https://infosec.exchange/tags/product" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>product</span></a> <a href="https://infosec.exchange/tags/management" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>management</span></a> <a href="https://infosec.exchange/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>development</span></a> <a href="https://infosec.exchange/tags/engineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>engineering</span></a> <a href="https://infosec.exchange/tags/usability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>usability</span></a> <a href="https://infosec.exchange/tags/core" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>core</span></a> <a href="https://infosec.exchange/tags/functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>functionality</span></a></p><p><a href="https://medium.com/cloud-security/back-to-the-basics-in-cloud-product-development-f372d2b07aba" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">medium.com/cloud-security/back</span><span class="invisible">-to-the-basics-in-cloud-product-development-f372d2b07aba</span></a></p>
Teri Radichel<p>Back to the Basics in Cloud Product Development<br>~~<br>If your basic functionality doesn’t work, the whiz-bang features don’t matter<br>~~<br><a href="https://infosec.exchange/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cloud</span></a> <a href="https://infosec.exchange/tags/product" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>product</span></a> <a href="https://infosec.exchange/tags/management" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>management</span></a> <a href="https://infosec.exchange/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>development</span></a> <a href="https://infosec.exchange/tags/engineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>engineering</span></a> <a href="https://infosec.exchange/tags/usability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>usability</span></a> <a href="https://infosec.exchange/tags/core" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>core</span></a> <a href="https://infosec.exchange/tags/functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>functionality</span></a> </p><p><a href="https://medium.com/cloud-security/back-to-the-basics-in-cloud-product-development-f372d2b07aba" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">medium.com/cloud-security/back</span><span class="invisible">-to-the-basics-in-cloud-product-development-f372d2b07aba</span></a></p>
Sarah Fackrell<p>Remember the <a href="https://mastodon.social/tags/SubversiveVersusBootstrap" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SubversiveVersusBootstrap</span></a> trade dress case? </p><p><a href="https://mastodon.social/@design_law/110859507180526166" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mastodon.social/@design_law/11</span><span class="invisible">0859507180526166</span></a></p><p>The defendant has filed a motion to dismiss, asserting that the claimed design is covered by an expired utility patent:<br><a href="https://www.scribd.com/document/676869760/Subversive-v-Bootstrap-MTD-Trade-Dress" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">scribd.com/document/676869760/</span><span class="invisible">Subversive-v-Bootstrap-MTD-Trade-Dress</span></a></p><p><a href="https://mastodon.social/tags/TradeDress" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TradeDress</span></a> <a href="https://mastodon.social/tags/UtilityPatents" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UtilityPatents</span></a> <a href="https://mastodon.social/tags/Functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Functionality</span></a> <a href="https://mastodon.social/tags/PlantTrays" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PlantTrays</span></a></p>
Sarah Fackrell<p>Third Circuit:</p><p>"Some candy companies evoke [a slice of watermelon] by using colors alone, making their candies red, white, and green. But the watermelon effect is significantly stronger if the red-white-and-green candy is shaped like a wedge. Because the tricolored shape is recognizable as watermelon flavored, the whole appearance is useful. So a candy-maker cannot block competitors from using the combined shape and colors...."</p><p><a href="https://www.scribd.com/document/669963154/Pim-v-Haribo-Decision-3d-Circuit" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">scribd.com/document/669963154/</span><span class="invisible">Pim-v-Haribo-Decision-3d-Circuit</span></a></p><p><a href="https://mastodon.social/tags/TradeDress" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TradeDress</span></a> <a href="https://mastodon.social/tags/Functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Functionality</span></a> <a href="https://mastodon.social/tags/LawFedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LawFedi</span></a></p>
Sarah Fackrell<p>Via TTABlog: "TTAB Affirms Section 2(e)(5) Functionality Refusal of Pen Holder Configuration"</p><p><a href="https://thettablog.blogspot.com/2023/06/ttab-affirms-section-2e5-functionality_27.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">thettablog.blogspot.com/2023/0</span><span class="invisible">6/ttab-affirms-section-2e5-functionality_27.html</span></a></p><p><a href="https://mastodon.social/tags/TradeDress" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TradeDress</span></a> <a href="https://mastodon.social/tags/Functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Functionality</span></a></p>
Sarah Fackrell<p>Little Leaf's VP of marketing said that the shape is "due to a type of seed that has the inherent ability to grow into a curly lettuce, which is then nurtured with a particular recipe of natural light, moisture, nutrients, and custom-built greenhouses."</p><p><a href="https://www.fastcompany.com/90894369/can-you-really-trademark-the-shape-of-lettuce-were-about-to-find-out" rel="nofollow noopener" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">fastcompany.com/90894369/can-y</span><span class="invisible">ou-really-trademark-the-shape-of-lettuce-were-about-to-find-out</span></a></p><p>So, basically, they want to use trademark law monopolize a certain method of growing this particular type of seed.</p><p>That's not what trademark law is supposed to do.</p><p><a href="https://mastodon.social/tags/TradeDress" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TradeDress</span></a> <a href="https://mastodon.social/tags/Functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Functionality</span></a> <a href="https://mastodon.social/tags/AbolishTradeDress" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AbolishTradeDress</span></a></p>
Sarah Fackrell

DayCab Co., Inc. v. Prairie Tech., LLC, No. 22-5625 (6th Cir. 2023): New case trade dress case discussing, inter alia, the functionality of "conversion kits for tractor-trailer cabs that convert a sleeper tractor—which has a compartment designed for long-haul driving, with a sleeping unit for the driver—into a tractor that does not have a sleeper unit" opn.ca6.uscourts.gov/opinions.

#TradeDress #Functionality

Here's some context from the district court's decision: storage.courtlistener.com/reca

Continued thread
Sarah Fackrell

Some of you might remember that the parties previously litigated this issue in Colorado.

The district court, like the TTAB, concluded that the color pink was functional. scribd.com/document/335930110/

The 10th Circuit didn't reach the trademark issue because it concluded that the District Court didn't have personal jurisdiction over CeramTec: ca10.uscourts.gov/sites/ca10/f

ScribdC5 Med Werks V Ceramtec - Order | PDF | Trade Dress | Patent ClaimC5 Med Werks v Ceramtec - Order
#CeramTec#PinkHipImplants#Functionality
*
Sarah Fackrell

CeramTec has appealed its TTAB loss to the Federal Circuit: scribd.com/document/625729314/

CeramTec has trade dress registrations that claim the color pink for use in connection with hip implants.

But it has "sought or obtained additional [utility] patent protection for compositions claiming the beneficial effects of chromia, the chemical that turns the compound pink."

The TTAB held that, in this context, pink is functional & unregistrable

#CeramTec#PinkHipImplants#Functionality
*
Sarah Fackrell

"Most of the issued patents cited in this brief have expired, meaning that the disclosed features are in the public domain. To conclude that [Timberland] can strip the public's right to copy and benefit from these features today would be antithetical to the pro-competitive objectives of both trademark and patent law."

TBL Licensing v. Vidal, 2022 WL 17573906, at *5 (E.D. Va. Dec. 8, 2022).

h/t @ TTABlog: thettablog.blogspot.com/2022/1

thettablog.blogspot.comThe TTABlog®: E.D. Va. Affirms TTAB: Timberland Boot Design is Functional and Lacks Acquired Distinctiveness
#Trademarks#TradeDress#Litigation
Continued thread
Sarah Fackrell

In prior litigation, CeramTec tried to argue that (at least some of) the patents weren't a problem because they covered both pink and not-pink embodiments: scribd.com/document/371204153/

But the 10th Circuit didn't get to that issue because it concluded the district court lacked personal jurisdiction over CeramTec: ca10.uscourts.gov/sites/ca10/f

ScribdC5 Medical Werks v. CeramTec - Appellant Brief | PDF | Personal Jurisdiction | LawsuitC5 Medical Werks v. CeramTec - Appellant Brief
#TradeDress#DesignLaw#Functionality
TrendingLive feeds
About