Social 📸 Photography

Kevin Karhan :verified:<a href="https://infosec.exchange/@pasi" class="u-url mention" rel="nofollow noopener" target="_blank">@pasi</a> except <a href="https://infosec.space/tags/CloudFlare" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudFlare</a> is a <a href="https://infosec.space/tags/RogueISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#RogueISP</a> and you could get <a href="https://infosec.space/tags/DDoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DDoS</a>-Protection from any other <a href="https://infosec.space/tags/Webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhoster</a> that didn't host <a href="https://infosec.space/tags/Terrorism" class="mention hashtag" rel="nofollow noopener" target="_blank">#Terrorism</a> like <a href="https://infosec.space/tags/Daesh" class="mention hashtag" rel="nofollow noopener" target="_blank">#Daesh</a> and <a href="https://infosec.space/tags/KiwiFarms" class="mention hashtag" rel="nofollow noopener" target="_blank">#KiwiFarms</a>, only firing the latter when bigger clients said: "It's US or THEM!" and started cancelling <a href="https://infosec.space/tags/ClownFlare" class="mention hashtag" rel="nofollow noopener" target="_blank">#ClownFlare</a>!

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.

manitu GmbHZum 10. Mal sucht hosttest.de den <a href="https://manitu.social/tags/Webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhoster</a> des Jahres!Auch dieses Jahr sind wir für die Wahl nominiert und würden uns sehr über eure Stimme freuen ♥️ <a href="https://www.hosttest.de/wahl/manitu/" rel="nofollow noopener" translate="no" target="_blank">https://www.hosttest.de/wahl/manitu/</a>Unter allen Teilnehmern werden auch wieder tolle Preise verlost - es kann sich also auch für euch richtig lohnen!

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...

Kevin Karhan :verified:<a href="https://void.rehab/@MarkAssPandi" class="u-url mention" rel="nofollow noopener" target="_blank">@MarkAssPandi</a> Is there any good <a href="https://infosec.space/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> Server Software that doesn't require a <a href="https://infosec.space/tags/VPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPS</a> but just a regular-ass <a href="https://infosec.space/tags/Webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhoster</a>?

JeroenEcht he al dagen lopen te stoeien met een Wordpress website van een klant die niet wilt updaten. Geeft Curl error 28 als melding. Verschillende oplossingen geprobeerd. Teneinde raat een update naar 6.4.2 (draaide 6.4.0) uitgevoerd. Pats probleem verholpen. Ja veeg mij maar op. Geen idee wat het probleem veroorzaakte en waarom het traag werkte. Maar nu gaat alles weer snel. <a href="https://space.jeroenvd.nl/tags/IT" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://space.jeroenvd.nl/tags/hosting" rel="nofollow noopener" target="_blank">#hosting</a> <a href="https://space.jeroenvd.nl/tags/Webhoster" rel="nofollow noopener" target="_blank">#Webhoster</a> <a href="https://space.jeroenvd.nl/tags/ict" rel="nofollow noopener" target="_blank">#ict</a> <a href="https://space.jeroenvd.nl/tags/online" rel="nofollow noopener" target="_blank">#online</a> <a href="https://space.jeroenvd.nl/tags/website" rel="nofollow noopener" target="_blank">#website</a>

FloGibt es hier Meinungen zu <a href="https://augsburg.social/tags/manitu" class="mention hashtag" rel="nofollow noopener" target="_blank">#manitu</a> als <a href="https://augsburg.social/tags/Webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhoster</a>?

Eric Mächlerich liebe es ja wenn <a href="https://mastodon.digitalsuccess.dev/tags/hoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#hoster</a> dumm tun weil man nicht der <a href="https://mastodon.digitalsuccess.dev/tags/kunde" class="mention hashtag" rel="nofollow noopener" target="_blank">#kunde</a> ist sondern nur der <a href="https://mastodon.digitalsuccess.dev/tags/webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#webhoster</a>.... als ob ich aus spass anrufe und mal alle namen und vornamen kombinationen durchteste damit ich zugriff auf eine fremde <a href="https://mastodon.digitalsuccess.dev/tags/webseite" class="mention hashtag" rel="nofollow noopener" target="_blank">#webseite</a> erhalte

Anonymous Germany<a href="https://social.tchncs.de/tags/Webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhoster</a> <a href="https://social.tchncs.de/tags/GoDaddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#GoDaddy</a>, Mutter von u.a. den deutschen Hostinguntermehmen <a href="https://social.tchncs.de/tags/HostEurope" class="mention hashtag" rel="nofollow noopener" target="_blank">#HostEurope</a> und <a href="https://social.tchncs.de/tags/DomainFactory" class="mention hashtag" rel="nofollow noopener" target="_blank">#DomainFactory</a>, entdeckte Dezember 2022 eine <a href="https://social.tchncs.de/tags/Sicherheitsluecke" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sicherheitsluecke</a> in ihren Systemen, die Angreifer hatten jedoch anscheinend seit mehreren Jahren Zugang zum Netzwerk des Unternehmens. Dies zeigt ein Meldung an die SEC. GoDaddy arbeite nun mit externen Cybersecurity-Forensikern und Strafverfolgern auf der ganzen Welt zusammen, um den Ursprung der Sicherheitsverletzung zu untersuchen.Wow!<a href="https://www.bleepingcomputer.com/news/security/godaddy-hackers-stole-source-code-installed-malware-in-multi-year-breach/" rel="nofollow noopener" target="_blank">https://www.bleepingcomputer.com/news/security/godaddy-hackers-stole-source-code-installed-malware-in-multi-year-breach/</a>

Oli | Oli's HelpDeskShit happens: <a href="https://nerdculture.de/tags/Webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhoster</a> <a href="https://nerdculture.de/tags/webgo" class="mention hashtag" rel="nofollow noopener" target="_blank">#webgo</a> hat vergessen sein Wildcard-SSL-<a href="https://nerdculture.de/tags/Zertifikat" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zertifikat</a> zu erneuern und das betrifft vor allem den Mailverkehr... 😐

StefanHey du da draußen im Fediverse, kennst du "hetzner.de" als <a href="https://quasselkopf.de/tags/Webhoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#Webhoster</a> sowie hast mit diesem Anbieter eventuell schon Erfahrung gesammelt bezüglich Hosting?Mich interessieren so Sachen wie: Verwaltung, Verfügbarkeit, Kundendienst, bei diesem Anbieter. Definitiv existieren noch andere Webhoster, jedoch interessiert mich erstmal nur <a href="https://quasselkopf.de/tags/Hetzner" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hetzner</a> in dem Zusammenhang. 😉Wenn du diesem Toot einen BOOST spendierst für eine bessere Reichweite, danke ich sehr dafür. 👍

Recent searches

Search options

Administered by:

Server stats:

#webhoster