toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

273
active users

#ccss

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@fsfe" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fsfe</span></a></span> also excetions to allow <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> to be continued to be used and bought need to be canceled and removed entirely.</p>
Susana Soto<p>Está abierto el período para postularse a las juntas de salud de la <a href="https://mastodon.cr/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a>. Es urgente contar con representantes de las personas aseguradas, que realmente defiendan nuestros intereses. Aquí pueden descargar el formulario de inscripción ➡️ <a href="https://www.ccss.sa.cr/juntas-salud" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">ccss.sa.cr/juntas-salud</span><span class="invisible"></span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@stevel" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>stevel</span></a></span> <span class="h-card" translate="no"><a href="https://bbs.kawa-kun.com/users/lazygamereviews" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lazygamereviews</span></a></span> <a href="https://infosec.space/tags/Funfact" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Funfact</span></a>: </p><p><a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> actually knows they have no leverage in reality, which is why when <a href="https://infosec.space/tags/Lenovo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Lenovo</span></a>, <a href="https://infosec.space/tags/Dell" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Dell</span></a> &amp; <a href="https://infosec.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hp</span></a> came to them to demand better <a href="https://infosec.space/tags/terms" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>terms</span></a> or they'd switch to <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>, Microsoft decided to pay them $25 per <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows</span></a> Pro preinstall instead.</p><ul><li>I think what is needed is not just Linux-friendly <a href="https://infosec.space/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hardware</span></a>, but explcitly Windows-unfriendly hardware and <a href="https://infosec.space/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>software</span></a>. </li></ul><p>Tho the only reason Microsoft's managment hasn't canceled <a href="https://infosec.space/tags/OTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OTP</span></a> <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> and replaced it with <a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaaS</span></a>-only shit is because they'd instantly piss off too many <a href="https://infosec.space/tags/customers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>customers</span></a> and <a href="https://infosec.space/tags/ValueRemoving" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ValueRemoving</span></a> <a href="https://infosec.space/tags/rentseekers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rentseekers</span></a> that run the entire <em>"<a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Antivirus</span></a>"</em> cottage industry.</p><ul><li>Remember: Noone asked for a <a href="https://infosec.space/tags/CopilotPC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CopilotPC</span></a> or <a href="https://infosec.space/tags/Copilot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Copilot</span></a> or <a href="https://infosec.space/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> bullshit, and when <a href="https://infosec.space/tags/consumers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>consumers</span></a> are given a fair choice they'd refuse to pay the premium for WinShit which is the inferior option.</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://udongein.xyz/users/lispi314" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lispi314</span></a></span> <span class="h-card" translate="no"><a href="https://digipres.club/@foone" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>foone</span></a></span> <em>noone</em> here argues against that.</p><ul><li>It's just that one needs to <a href="https://infosec.space/@kkarhan/114862595629371002" rel="nofollow noopener" target="_blank">work around garbage</a> and most people ain't privilegued to say <em>"No. I'll quit!"</em></li></ul><p>If it was my decision, <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> and <a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaaS</span></a> would be as illegal as NBC weapons!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://fedifreu.de/@cryptgoat" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cryptgoat</span></a></span> I do, because <span class="h-card" translate="no"><a href="https://floss.social/@fdroidorg" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fdroidorg</span></a></span> choosing to shill a <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> that isn't even distributed on a 3rd party repo is a decision by them.</p><ul><li><a href="https://infosec.space/tags/BraveBrowser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BraveBrowser</span></a> never was <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a>'d nor on <a href="https://infosec.space/tags/Fdroid" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fdroid</span></a>'s own repo.</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@katyswain" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>katyswain</span></a></span> I din't think that <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> is good either, but the demands of <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv3</span></a> are not compatible with the (adnitteldy shitty) reality of how <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IP</span></a>, <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Licensing</span></a> and <a href="https://infosec.space/tags/Patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Patents</span></a> work and thus it kneecaps a lot of things.</p><ul><li><p>GPLv3 caused <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a> to freeze their <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bash</span></a> version and divest into <a href="https://infosec.space/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LLVM</span></a> and adopt <a href="https://infosec.space/tags/zsh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>zsh</span></a>.</p></li><li><p>As <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> showed, enforcing the <a href="https://infosec.space/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPL</span></a>(v2) resulted in exactly 0 code being committed to <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BusyBox</span></a> and it only made said project look toxic and litigatious. </p></li><li><p>Also i've yet to see anything happen re: <a href="https://infosec.space/tags/paywalled" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>paywalled</span></a> <a href="https://infosec.space/tags/SourceCodeAccess" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SourceCodeAccess</span></a> for <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>grsec</span></a> &amp; <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RedHat</span></a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>. Maybe <a href="https://infosec.space/tags/GPLv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv4</span></a> will ban <a href="https://infosec.space/tags/paxwalling" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>paxwalling</span></a> and force violators to work on <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNU</span></a> / <a href="https://infosec.space/tags/HURD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HURD</span></a>?</p></li></ul><p>I chose <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>0BSD</span></a> for _OS/1337 because as with any "intellectual labour", <em>one cannot force others to collaborate</em> and I'd rather have people join in out of the goodness of their hearts instead of just dumping <em>some random git commit</em> that is useless.</p><p><a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaos.social/@epicenter_works" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>epicenter_works</span></a></span> deshalb muss es eine <a href="https://infosec.space/tags/Pflicht" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pflicht</span></a> zu <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> geben und <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> verboten werden!</p><ul><li>Nur <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a> und <a href="https://infosec.space/tags/Transparenz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Transparenz</span></a> kann <a href="https://infosec.space/tags/KRITIS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KRITIS</span></a> sichern...</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@Belledonne_Communications" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Belledonne_Communications</span></a></span> so it's <a href="https://infosec.space/tags/CallForPricing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CallForPricing</span></a>-<a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> and not <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a>, I guess...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mrmasterkeyboard</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> My choice of <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@musl" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>musl</span></a></span> for <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>OS1337</span></a></span> is because I want my stuff to be statically linked and not every minor update to have the risk to brick shit, because <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GlibC</span></a> is notorious for that since the <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNU</span></a> project are nonchalantly thinking <em>"just recompile it"</em> is a valid excuse.</p><ul><li>Espechally since (for better or worse) not everything is (A)GPL(v3)-licensed and prople may need to deal with <a href="https://infosec.space/tags/binaries" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binaries</span></a> and/or <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> because in many cases patents and licensing are not allowing the distribution of it.</li></ul><p>I mean, we all <em>'loved'</em> to live in a world where this wasn't the case but if I were to like deal with a vocoder for <a href="https://en.wikipedia.org/wiki/Mixed-excitation_linear_prediction" rel="nofollow noopener" target="_blank">MELP</a>, <a href="https://en.wikipedia.org/wiki/Multi-Band_Excitation" rel="nofollow noopener" target="_blank">AMBE</a> or <a href="https://twelp.pro" rel="nofollow noopener" target="_blank">TWELP</a> I'm pretty shure I'd <em>never ever</em> be allowed to distribute it's source code, even for <em>"clients exempted from the need to obtain licensing"</em>...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaos.social/@soc" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>soc</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@dysfun" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dysfun</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@musl" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>musl</span></a></span> well, <em>every single piece of software is!</em></p><ul><li>Show me a poeve of software, <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a> or <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> doesn't matter, that doesn't have this clause?</li></ul><p>And no, <em>"<a href="https://infosec.space/tags/CallForPricing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CallForPricing</span></a>"</em> and <a href="https://infosec.space/tags/NDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NDA</span></a>'d <a href="https://infosec.space/tags/MILINTEL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MILINTEL</span></a> / <a href="https://infosec.space/tags/Aerospace" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Aerospace</span></a> stuff like <a href="https://infosec.space/tags/VxWorks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VxWorks</span></a> <em>doesn't count!</em></p>

El finde pasado tuve la experiencia de visitar a alguien cercana que se encuentra internada en un hospi del Seguro Social.

Hay cosas desde dentro que siguen siendo esenciales para #CostaRica. Por ejemplo, un sistema de salud que no distingue clases sociales, procedencias y cosmovisiones.

Seguimos teniendo rasgos de una colectividad endémica e inigualable en nuestro país, a pesar de saber que convivimos hoy en un mundo que ve con rareza cualquier pilar de conciencia social, tal como está constituida en sus entrañas la misma #CCSS.

Replied in thread

@CenTdemeern1 +9001%

OFC they gonna axe #Windows & #MicrosoftOffice anyway in favour of #subscription-only #Saas like #XboxGamePass, #Office365 / #Microsoft365 & #Azure because that's where the real margins are, not with #OneTimePurchase products!

Replied in thread

@jacob yes, and #OpenWashing is a real issue not just with #AssholeLicensing as seen with #Redis & others using #SSPL as a literal #AssholeLicense which are just "#SourceAvailable" instead of #OpenSource, but actual #donations.and #contributions.

  • Try to convince any C-level decisionmakers to donate even 1% of the equivalent of licensing the #CCSS equivalents of the #FLOSS deployed will get one laughed at, and suggesting 10% threatened woth getting fired.

#AskMeHowIKnow

Gobierno procura reducir en 99% su obligación de financiar atención de salud para personas en vulnerabilidad

Como parte del pulso para conciliar la deuda del Gobierno con la CCSS, se impulsa interpretación para reducir obligación legal de financiar servicios de salud. de unas 420 mil personas a solo 3 mil
La entrada Gobierno procura reducir en 99% su obligación de financiar atención de salud para personas [...]

#AsambleaLegislativa #CCSS #ComisiónCCSS #DEUDACCSS #País

semanariouniversidad.com/pais/

Semanario Universidad · Gobierno procura reducir en 99% su obligación de financiar atención de salud para personas en vulnerabilidad • Semanario UniversidadComo parte del pulso para conciliar la deuda del Gobierno con la CCSS, se impulsa interpretación para reducir obligación legal de financiar servicios de salud. de unas 420 mil personas a solo 3 mil

Gerente de la CCSS: Deuda del Estado pasa desapercibida, pero compromete el futuro del sistema

Gustavo Picado Chacón, gerente financiero de la Caja Costarricense de Seguro Social (CCSS), advirtió a los diputados que la deuda que el Estado mantiene con la institución por el seguro de salud es muy importante, pero pasa desapercibida y amenaza el futuro del sistema. De acuerdo con Picado, las personas no dime [...]

#CCSS #Deuda #Nacionales #Política #Salud #Salud #VisualB

crhoy.com/nacionales/salud/ger

Replied in thread

@davidrevoy @Ertain @zeppy5d

Yes and no.

#Apple's #iPad makes it easy to test, build and sell #CCSS [commercial closed-source software] at a premium.

  • I mean, I'm happy with my #X230Tablet but I do acknowledge this is an old device and it's rather the exception than norm...

Simply because #Wacom makes good passive stylus and pen-capable touchscreens.

  • So OFC companies that have the money and resources to build premium #apps will target the premium customers who by virtue ob being able to splash 4 digits on a tablet brand-new will be proven more able to pay for their software.

That's why #Autodesk won't even sell people a #Linux license for #Maya (or any of their other tools) unless one has proof of ownership of a certified workstation (i.e. HP Z-series) with a #RHEL [#RedHat] #Workstation #subscription active to begin with.

  • And yes they will run the machine's serial # to check if it's ordered with parts that fit their system requirements from the factory and will demand the same for RHEL. I've been there and had to do that before they even consider offering one a subscription!

Compare that to like #AffinityDesigner on #iOS (or rather "#iPadOS") and the fact that basically all iPad users are expected to have an Apple account and credit card linked to it for the #AppStore and it's no wounder the developers of creative apps will focus on that.

The only exception are #FLOSS #apps that are native to Linux and/or got started on other #Unix Systems [#blender started out on #IRIX as CCSS] and serve #macOS & #Windows as 2nd & 3rd tier platforms [i.e. #darktable oftentimes had no Windows builds because none of the devs had or wanted a Windows machine to test on!]