Veganism Social

Kevin Karhan :verified:<a href="https://mastodon.social/@dec_hl" class="u-url mention" rel="nofollow noopener" target="_blank">@dec_hl</a> I think something like an <a href="https://infosec.space/tags/App" class="mention hashtag" rel="nofollow noopener" target="_blank">#App</a> <a href="https://infosec.space/tags/curator" class="mention hashtag" rel="nofollow noopener" target="_blank">#curator</a> site that allows <a href="https://infosec.space/tags/filtering" class="mention hashtag" rel="nofollow noopener" target="_blank">#filtering</a> / has said filters set by default as a "<a href="https://infosec.space/tags/SafeSearch" class="mention hashtag" rel="nofollow noopener" target="_blank">#SafeSearch</a>" would be propably best...<ul><li>The core problem is that since there's no <a href="https://infosec.space/tags/affiliate" class="mention hashtag" rel="nofollow noopener" target="_blank">#affiliate</a> program woth <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a>'s <a href="https://infosec.space/tags/AppStore" class="mention hashtag" rel="nofollow noopener" target="_blank">#AppStore</a> nor <a href="https://infosec.space/tags/GooglePlay" class="mention hashtag" rel="nofollow noopener" target="_blank">#GooglePlay</a> and <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> having killed competitiors to the latter like <a href="https://infosec.space/tags/AndroidPit" class="mention hashtag" rel="nofollow noopener" target="_blank">#AndroidPit</a> <a href="https://infosec.space/tags/AppCenter" class="mention hashtag" rel="nofollow noopener" target="_blank">#AppCenter</a> with <a href="https://infosec.space/tags/VAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#VAT</a> shite, there is no ethical way to monetize it once it exceeds the average <a href="https://infosec.space/tags/WebHoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebHoster</a>'s "unlimited traffic" plans...</li></ul>Not to mention it'll get <a href="https://infosec.space/tags/downranked" class="mention hashtag" rel="nofollow noopener" target="_blank">#downranked</a> and <a href="https://infosec.space/tags/shadowbanned" class="mention hashtag" rel="nofollow noopener" target="_blank">#shadowbanned</a> from both platfirms pretty quickly.

Kevin Karhan :verified:<a href="https://infosec.exchange/@JayeLTee" class="u-url mention" rel="nofollow noopener" target="_blank">@JayeLTee</a> <a href="https://infosec.exchange/@masek" class="u-url mention" rel="nofollow noopener" target="_blank">@masek</a> <a href="https://mastodon.social/@Brokar" class="u-url mention" rel="nofollow noopener" target="_blank">@Brokar</a> <a href="https://techhub.social/@Techmeme" class="u-url mention" rel="nofollow noopener" target="_blank">@Techmeme</a> <a href="https://infosec.exchange/@bucketchallenge" class="u-url mention" rel="nofollow noopener" target="_blank">@bucketchallenge</a> THIS is why I find <a href="https://infosec.space/tags/Azure" class="mention hashtag" rel="nofollow noopener" target="_blank">#Azure</a>, <a href="https://infosec.space/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#aws</a>, <a href="https://infosec.space/tags/GCP" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCP</a> et. al so frustrating and similarly neglective as <a href="https://infosec.space/tags/NameCheap" class="mention hashtag" rel="nofollow noopener" target="_blank">#NameCheap</a>, <a href="https://infosec.space/tags/GDaddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDaddy</a> and <a href="https://infosec.space/tags/CloudFlare" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudFlare</a>, cuz evhen the cheapest 08/15 <a href="https://infosec.space/tags/VPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPS</a> & <a href="https://infosec.space/tags/Webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhoster</a> I know will take <a href="https://infosec.space/tags/AbuseReports" class="mention hashtag" rel="nofollow noopener" target="_blank">#AbuseReports</a> serious and handle them accordingly, whereas one may have to block entire IP blocks if not complete ASNs to shield from ongoing attacks!

Kevin Karhan :verified:<a href="https://udongein.xyz/users/lispi314" class="u-url mention" rel="nofollow noopener" target="_blank">@lispi314</a> <a href="https://mk.absturztau.be/@enigmatico" class="u-url mention" rel="nofollow noopener" target="_blank">@enigmatico</a> <a href="https://transfem.social/@bunnybeam" class="u-url mention" rel="nofollow noopener" target="_blank">@bunnybeam</a> <a href="https://ublog.kimapr.net/users/kimapr" class="u-url mention" rel="nofollow noopener" target="_blank">@kimapr</a> nodds in agreement<ul><li>I think having a proper <a href="https://infosec.space/tags/API" class="mention hashtag" rel="nofollow noopener" target="_blank">#API</a> is a way to facilitate that, cuz worst-case one just slaps together some <a href="https://infosec.space/tags/aliases" class="mention hashtag" rel="nofollow noopener" target="_blank">#aliases</a> in <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#bash</a>, <a href="https://infosec.space/tags/fish" class="mention hashtag" rel="nofollow noopener" target="_blank">#fish</a>, <a href="https://infosec.space/tags/zsh" class="mention hashtag" rel="nofollow noopener" target="_blank">#zsh</a> or whatever <a href="https://infosec.space/tags/shell" class="mention hashtag" rel="nofollow noopener" target="_blank">#shell</a> and just uses <a href="https://infosec.space/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> to query stuff manually as this solves the whole <a href="https://infosec.space/tags/WebApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebApp</a> - issue.</li></ul>And I do prefer <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> as it works fine for an ever increasing audience!<ul><li>Even if we choose to point at bad <a href="https://infosec.space/tags/UX" class="mention hashtag" rel="nofollow noopener" target="_blank">#UX</a> / <a href="https://infosec.space/tags/UI" class="mention hashtag" rel="nofollow noopener" target="_blank">#UI</a> combos like <a href="https://infosec.space/tags/GnuPG" class="mention hashtag" rel="nofollow noopener" target="_blank">#GnuPG</a>, we've to also acknowledge better existing alternatives like <a href="https://infosec.space/tags/enc" class="mention hashtag" rel="nofollow noopener" target="_blank">#enc</a> that <a href="https://github.com/life4/enc" rel="nofollow noopener" target="_blank">just work</a>!</li></ul>Personally, I think that everything people are expected to use if not forced to use should be <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> as licensed in a <a href="https://infosec.space/tags/OSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#OSI</a> accredited license and be released with <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceCode</a> and <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> to make <a href="https://infosec.space/tags/reproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#reproduceableBuilds</a> and thus facilitate <a href="https://infosec.space/tags/audits" class="mention hashtag" rel="nofollow noopener" target="_blank">#audits</a> by truly independent parties...<ul><li>And if that's not possible any requirement to using said things should be outlawed no matter the context! </li></ul>A unsarcastically good example is <a href="https://infosec.space/tags/S3" class="mention hashtag" rel="nofollow noopener" target="_blank">#S3</a>, even tho I hate <a href="https://infosec.space/tags/amazon" class="mention hashtag" rel="nofollow noopener" target="_blank">#amazon</a>, they wanted <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a> to integrate their <a href="https://infosec.space/tags/ObjectStorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#ObjectStorage</a> which necessitated an <a href="https://infosec.space/tags/open" class="mention hashtag" rel="nofollow noopener" target="_blank">#open</a> source'd API to the point that it's <a href="https://infosec.space/tags/backend" class="mention hashtag" rel="nofollow noopener" target="_blank">#backend</a> is inherently reproduceable, and now every halfassing <a href="https://infosec.space/tags/Webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhoster</a> offers S3 <a href="https://infosec.space/tags/storage" class="mention hashtag" rel="nofollow noopener" target="_blank">#storage</a>, sometimes with bit & second-precise billing.

Kevin Karhan :verified:<a href="https://possum.city/@mook" class="u-url mention" rel="nofollow noopener" target="_blank">@mook</a> <a href="https://mastodon.social/@MastodonEngineering" class="u-url mention" rel="nofollow noopener" target="_blank">@MastodonEngineering</a> EXACTLY THIS is why I think a "<a href="https://infosec.space/tags/Webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhoster</a>-only" functional <a href="https://infosec.space/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> server is kinda important.<ul><li>And if <a href="https://infosec.space/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a> was that, I could understand them saying "<a href="https://infosec.space/tags/canfix" class="mention hashtag" rel="nofollow noopener" target="_blank">#canfix</a> & <a href="https://infosec.space/tags/wontfix" class="mention hashtag" rel="nofollow noopener" target="_blank">#wontfix</a>" for all the valid reasons (tho I'm shure <a href="https://infosec.space/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> devs fluent in <a href="https://infosec.space/tags/mod_security" class="mention hashtag" rel="nofollow noopener" target="_blank">#mod_security</a> & <a href="https://infosec.space/tags/mod_rewrite" class="mention hashtag" rel="nofollow noopener" target="_blank">#mod_rewrite</a> would likely disagree!)...</li></ul>And for what Mastodon does, it feels quite overengineered and overcomplex, but then again I'm used to <a href="https://infosec.space/tags/MkDocs" class="mention hashtag" rel="nofollow noopener" target="_blank">#MkDocs</a> and other, "<a href="https://infosec.space/tags/offline" class="mention hashtag" rel="nofollow noopener" target="_blank">#offline</a>-<a href="https://infosec.space/tags/CMS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMS</a>|es" that do just work and are kinda essential for stuff on <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a> because noone there uses <a href="https://infosec.space/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> and enabling <a href="https://infosec.space/tags/JS" class="mention hashtag" rel="nofollow noopener" target="_blank">#JS</a> is discouraged by <a href="https://infosec.space/tags/TorBrowser" class="mention hashtag" rel="nofollow noopener" target="_blank">#TorBrowser</a> for all the right reasons...I should take a closer look at <a href="https://infosec.space/tags/streams" class="mention hashtag" rel="nofollow noopener" target="_blank">#streams</a> once I have time for that...

Recent searches

Search options

Administered by:

Server stats:

#webhoster