Shakedown Social

Dominik WombacherHave you heard of AWS S3 Vectors [1]? I tested it with AWS Bedrock Knowledge Base to build a Serverless RAG without monthly costs. Pretty cool to create a MVP/PoC or just play around with an AI Chatbot for less than a cup of coffee. More in my Blog [2].[1] <a href="https://aws.amazon.com/blogs/aws/introducing-amazon-s3-vectors-first-cloud-storage-with-native-vector-support-at-scale/" rel="nofollow noopener" translate="no" target="_blank">https://aws.amazon.com/blogs/aws/introducing-amazon-s3-vectors-first-cloud-storage-with-native-vector-support-at-scale/</a>[2] <a href="https://dominik.wombacher.cc/posts/serverless-rag-without-monthly-costs-using-aws-bedrock-and-s3-vectors.html" rel="nofollow noopener" translate="no" target="_blank">https://dominik.wombacher.cc/posts/serverless-rag-without-monthly-costs-using-aws-bedrock-and-s3-vectors.html</a><a href="https://fosstodon.org/tags/AWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AWS</a> <a href="https://fosstodon.org/tags/S3Vectors" class="mention hashtag" rel="nofollow noopener" target="_blank">#S3Vectors</a> <a href="https://fosstodon.org/tags/RAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#RAG</a> <a href="https://fosstodon.org/tags/Serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#Serverless</a> <a href="https://fosstodon.org/tags/GenAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#GenAI</a>

🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸I've been faffing about with <a href="https://mastodon.social/tags/CDK" class="mention hashtag" rel="nofollow noopener" target="_blank">#CDK</a> for over a year now, reading books, vibecoding projects, and I only now actually got around to deploying something with it. It's not that bad--when you've got Q's help 😆 <a href="https://mastodon.social/tags/AWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AWS</a> <a href="https://mastodon.social/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloud</a> <a href="https://mastodon.social/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a>

🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸I built my website using <a href="https://fosstodon.org/@enhance_dev" class="u-url mention" rel="nofollow noopener" target="_blank">@enhance_dev</a> a couple years ago but I feel like I should use a more popular <a href="https://mastodon.social/tags/IaC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IaC</a> framework for deploying to <a href="https://mastodon.social/tags/AWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AWS</a> like <a href="https://mastodon.social/tags/CDK" class="mention hashtag" rel="nofollow noopener" target="_blank">#CDK</a>, <a href="https://mastodon.social/tags/SAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SAM</a>, <a href="https://mastodon.social/tags/Terraform" class="mention hashtag" rel="nofollow noopener" target="_blank">#Terraform</a> or just raw <a href="https://mastodon.social/tags/CloudFormation" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudFormation</a>. The problem is, I'm spoiled; Enhance makes <a href="https://mastodon.social/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a> so easy. I find myself just reimplementing all it's features; file based routing, html templates, session management, etc. <a href="https://mastodon.social/tags/webDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webDev</a>

🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸I mean, I'm never really compiling binaries, unless they are <a href="https://mastodon.social/tags/NodeJs" class="mention hashtag" rel="nofollow noopener" target="_blank">#NodeJs</a> dependencies (some might be) so it's never *really* mattered, but the obsessive compulsive part of me just wants my dev environment to be as much like production as possible.. <a href="https://mastodon.social/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloud</a> <a href="https://mastodon.social/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a> <a href="https://mastodon.social/tags/lambda" class="mention hashtag" rel="nofollow noopener" target="_blank">#lambda</a> <a href="https://mastodon.social/tags/softwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwareDevelopment</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mastodon.social/tags/javaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javaScript</a>

Corin Ashwell 🌍 🌿 🍄🏳️‍⚧️Singing "zip and, zip and deplooooy" to the tune of <a href="https://mastodon.social/tags/Metallica" class="mention hashtag" rel="nofollow noopener" target="_blank">#Metallica</a> Seek & Destroy<a href="https://mastodon.social/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a> <a href="https://mastodon.social/tags/computing" class="mention hashtag" rel="nofollow noopener" target="_blank">#computing</a>

Decenta LyzedWould you like to compile <a href="https://aus.social/tags/Scuttlebutt" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scuttlebutt</a> on Windows ? Anyone?<a href="https://aus.social/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#p2p</a> <a href="https://aus.social/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a> <a href="https://aus.social/tags/decentralization" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralization</a>

Matt BacchiI had a (years) old <a href="https://hachyderm.io/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a> framework app deployed that I either wanted to merely update the Lambda runtime, or delete the stack entirely. I both of those actions just now but the CLI wouldn't let me do either without creating an account on their system.To .... remove an app...I'm manually deleting the resources and lamenting the death of yet another developer tool that I trusted to not be evil. I liked them originally, but they've lost their way.<a href="https://hachyderm.io/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloud</a> <a href="https://hachyderm.io/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#aws</a> <a href="https://hachyderm.io/tags/serverlessframework" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverlessframework</a> <a href="https://hachyderm.io/tags/sls" class="mention hashtag" rel="nofollow noopener" target="_blank">#sls</a>

Fedify: an ActivityPub server frameworkWe're excited to announce the release of <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Fedify" target="_blank">#Fedify</a> 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a>.🌐 Cloudflare Workers supportFedify 1.6 introduces first-class support for <a href="https://workers.cloudflare.com/" rel="nofollow noopener" target="_blank">Cloudflare Workers</a>, enabling <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/serverless" target="_blank">#serverless</a> deployment of <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> applications at the edge.New components<ul> <li><a href="https://fedify.dev/manual/kv#workerskvstore-cloudflare-workers-only" rel="nofollow noopener" target="_blank"><code>WorkersKvStore</code></a>: A key–value store implementation using <a href="https://developers.cloudflare.com/kv/" rel="nofollow noopener" target="_blank">Cloudflare's KV API</a> for persistent storage in Workers environments</li><li><a href="https://fedify.dev/manual/mq#workersmessagequeue-cloudflare-workers-only" rel="nofollow noopener" target="_blank"><code>WorkersMessageQueue</code></a>: A message queue implementation leveraging <a href="https://developers.cloudflare.com/queues/" rel="nofollow noopener" target="_blank">Cloudflare Queues</a> for reliable message processing</li> </ul>Key features<ul> <li>Seamless integration with <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Cloudflare" target="_blank">#Cloudflare</a>'s serverless runtime</li><li>Automatic handling of queue message processing through Workers' <code>queue()</code> method</li><li>Support for <a href="https://developers.cloudflare.com/workers/runtime-apis/nodejs/" rel="nofollow noopener" target="_blank">Node.js compatibility flag</a> required for Fedify's cryptographic operations</li><li>Manual queue processing via <code>Federation.processQueuedTask()</code> method</li> </ul>For a complete working example, see the <a href="https://github.com/fedify-dev/fedify/tree/1.6-maintenance/examples/cloudflare-workers" rel="nofollow noopener" target="_blank">Cloudflare Workers example</a> in the Fedify repository.🏗️ Federation builder patternFedify 1.6 introduces the <code>FederationBuilder</code> class and <code>createFederationBuilder()</code> function to support <a href="https://fedify.dev/manual/federation#builder-pattern-for-structuring" rel="nofollow noopener" target="_blank">deferred federation instantiation</a>. This pattern provides several benefits:<ul> <li>Deferred instantiation: Set up dispatchers and listeners before creating the federation object</li><li>Better code organization: Avoid circular dependencies and improve project structure</li><li>Cloudflare <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/Workers" target="_blank">#Workers</a> compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals</li><li>Modular setup: Build complex federations piece by piece before instantiation</li> </ul>The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.🔐 HTTP Message Signatures (RFC 9421)Fedify 1.6 implements the official <a href="https://www.rfc-editor.org/rfc/rfc9421" rel="nofollow noopener" target="_blank">HTTP Message Signatures standard (RFC 9421)</a> specification, the final revision of the HTTP Signatures specification.Double-knocking mechanismTo ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:<ol> <li>Primary attempt: <a href="https://www.rfc-editor.org/rfc/rfc9421" rel="nofollow noopener" target="_blank">RFC 9421</a> (HTTP Message Signatures) for modern implementations</li><li>Fallback: <a href="https://datatracker.ietf.org/doc/html/draft-cavage-http-signatures-12" rel="nofollow noopener" target="_blank">Draft cavage version</a> for legacy compatibility</li><li>Adaptive caching: The system remembers which version each server supports to optimize future requests</li> </ol>This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.Interoperability testingThe RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:<ul> <li>Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures</li><li>Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to <a href="https://github.com/mastodon/mastodon/pull/34814" rel="nofollow noopener" target="_blank">Mastodon PR #34814</a>, though Mastodon 4.4.0 has not yet been released)</li> </ul>These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselves—making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.🔍 WebFinger enhancementsDedicated WebFinger lookupThe new <a href="https://fedify.dev/manual/context#webfinger-lookups" rel="nofollow noopener" target="_blank"><code>Context.lookupWebFinger()</code></a> method provides direct access to <a href="https://datatracker.ietf.org/doc/html/rfc7033" rel="nofollow noopener" target="_blank">WebFinger</a> data, offering developers more granular control over account discovery and resource resolution beyond the higher-level <a href="https://fedify.dev/manual/context#looking-up-remote-objects" rel="nofollow noopener" target="_blank"><code>Context.lookupObject()</code></a> method.🛠 Context API improvementsContext data replacementThe new <a href="https://fedify.dev/manual/context#replacing-the-context-data" rel="nofollow noopener" target="_blank"><code>Context.clone()</code></a> method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.🚀 Migration considerationsBackward compatibilityFedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.Node.js version requirementImportant: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.New deployment optionsFor new deployments, consider leveraging Cloudflare Workers support for:<ul> <li>Global edge deployment with low latency</li><li>Serverless scaling and automatic resource management</li><li>Integration with Cloudflare's ecosystem of services</li> </ul>🎯 Looking forwardFedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards. For detailed migration guides, API documentation, and examples, please visit the <a href="https://fedify.dev/" rel="nofollow noopener" target="_blank">Fedify documentation</a>. Join our community on <a href="https://matrix.to/#/#fedify:matrix.org" rel="nofollow noopener" target="_blank">Matrix</a> or <a href="https://discord.gg/bhtwpzURwd" rel="nofollow noopener" target="_blank">Discord</a> for support and discussions.<a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/RFC9421" target="_blank">#RFC9421</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/HTTPSignatures" target="_blank">#HTTPSignatures</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/HTTPMessageSignatures" target="_blank">#HTTPMessageSignatures</a> <a class="mention hashtag" rel="nofollow noopener" href="https://hollo.social/tags/CloudflareWorkers" target="_blank">#CloudflareWorkers</a>

Kevin Karhan :verified:<a href="https://tacobelllabs.net/@astraluma" class="u-url mention" rel="nofollow noopener" target="_blank">@astraluma</a> <a href="https://girldick.gay/@alina" class="u-url mention" rel="nofollow noopener" target="_blank">@alina</a> <a href="https://fedi.xerz.one/users/xerz" class="u-url mention" rel="nofollow noopener" target="_blank">@xerz</a> Bonus points if you can make it "<a href="https://infosec.space/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a>" using <a href="https://infosec.space/tags/pwnat" class="mention hashtag" rel="nofollow noopener" target="_blank">#pwnat</a> techniques... <a href="https://github.com/samyk/pwnat" rel="nofollow noopener" translate="no" target="_blank">https://github.com/samyk/pwnat</a>

MijndertPinning an <a href="https://toot.community/tags/introduction" class="mention hashtag" rel="nofollow noopener" target="_blank">#introduction</a> on my newly reactivated account.I'm a lead platform engineer, runner and <a href="https://toot.community/tags/minimalist" class="mention hashtag" rel="nofollow noopener" target="_blank">#minimalist</a>. I'm interested in <a href="https://toot.community/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#aws</a>, <a href="https://toot.community/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a>, <a href="https://toot.community/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a>, <a href="https://toot.community/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a> and adjacent topics. I've been in the industry, as they say, for over 17 years now. I'm getting old.I do some <a href="https://toot.community/tags/running" class="mention hashtag" rel="nofollow noopener" target="_blank">#running</a> and <a href="https://toot.community/tags/rowing" class="mention hashtag" rel="nofollow noopener" target="_blank">#rowing</a> for a bit of physical exercise. I really like computers so I need to sometimes touch grass.

Harry W.If you're using <a href="https://mstdn.social/tags/Serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#Serverless</a> Framework, and you really don't want to move to v4 because they've now made it pay to play, you can use this Open Source version: <a href="https://github.com/oss-serverless/serverless" rel="nofollow noopener" translate="no" target="_blank">https://github.com/oss-serverless/serverless</a>Pretty much a drop in replacement<a href="https://mstdn.social/tags/AWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AWS</a> <a href="https://mstdn.social/tags/Lambda" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lambda</a> <a href="https://mstdn.social/tags/OSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OSS</a> <a href="https://mstdn.social/tags/serverless_framework" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless_framework</a>

Kevin Karhan :verified:<a href="https://fosstodon.org/@bert_hubert" class="u-url mention" rel="nofollow noopener" target="_blank">@bert_hubert</a> TBH, even shit like <a href="https://infosec.space/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#aws</a> isn't selling furniture, but demand a premium every step of the way for every tool used to turn wood into some furniture - in perpetuality and with no good means to control costs. <a href="https://www.youtube.com/watch?v=ZzI9JE0i6Lc" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=ZzI9JE0i6Lc</a><ul><li>And that's why "<a href="https://infosec.space/tags/Cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloud</a>" and "<a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener" target="_blank">#SaaS</a>" are shit and buzzwords 99% of the time.</li></ul>Just like "<a href="https://infosec.space/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a>" is just a <a href="https://infosec.space/tags/lie" class="mention hashtag" rel="nofollow noopener" target="_blank">#lie</a>... <a href="https://www.youtube.com/watch?v=qQk94CjRvIs" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=qQk94CjRvIs</a>

Kevin Karhan :verified:<a href="https://udongein.xyz/users/lispi314" class="u-url mention" rel="nofollow noopener" target="_blank">@lispi314</a> <a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> <a href="https://mastodon.laurenweinstein.org/@lauren" class="u-url mention" rel="nofollow noopener" target="_blank">@lauren</a> Not only that, but <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> being.located in <a href="https://infosec.space/tags/Trumpist" class="mention hashtag" rel="nofollow noopener" target="_blank">#Trumpist</a> <a href="https://infosec.space/tags/USA" class="mention hashtag" rel="nofollow noopener" target="_blank">#USA</a> means they gotta have to follow said laws and that means if flexed upon using <a href="https://infosec.space/tags/FOSTA" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSTA</a> & <a href="https://infosec.space/tags/SESTA" class="mention hashtag" rel="nofollow noopener" target="_blank">#SESTA</a> or god forbid made-up claims to commit <a href="https://infosec.space/tags/TransGenocide" class="mention hashtag" rel="nofollow noopener" target="_blank">#TransGenocide</a> and prosecute <a href="https://infosec.space/tags/Trans" class="mention hashtag" rel="nofollow noopener" target="_blank">#Trans</a> minors and/or their parents and/or medical professionals, THIS WILL BLOW UP IN THEIR FACES like a grenade used as ball gag and fuse pulled!<ul><li>It's absolutely trivial to <a href="https://www.youtube.com/watch?v=wVyu7NB7W6Y" rel="nofollow noopener" target="_blank">abuse</a> <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Govware</a> <a href="https://infosec.space/tags/Backdoors" class="mention hashtag" rel="nofollow noopener" target="_blank">#Backdoors</a> and thus track people down. <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> by design and architecture WILL BE COMPLICIT IN IT!</li></ul>For comparison: <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@monocles</a> doesn't demand <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> like a <a href="https://infosec.space/tags/PhoneNumber" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumber</a> or anything at all and if you don't trust them either (which is fair - never trust anyone, neither Signal nor <a href="https://infosec.space/tags/monocles" class="mention hashtag" rel="nofollow noopener" target="_blank">#monocles</a> nor me!) you can not only <a href="https://github.com/greyhat-academy/lists.d/blob/main/xmpp.servers.list.tsv" rel="nofollow noopener" target="_blank">choose from various providers</a> but literally <a href="https://infosec.space/tags/SelfHost" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHost</a> your own (even as an <a href="https://infosec.space/tags/OnionService" class="mention hashtag" rel="nofollow noopener" target="_blank">#OnionService</a> 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>) and thus have full control of all the comms.<ul><li>And I'd rather recommend <a href="https://infosec.exchange/@micahflee" class="u-url mention" rel="nofollow noopener" target="_blank">@micahflee</a> 's <a href="https://infosec.space/tags/OnionShare" class="mention hashtag" rel="nofollow noopener" target="_blank">#OnionShare</a> over Signal just because that's even simpler and basically "fully decentralized" and "<a href="https://infosec.space/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a>" that it's even more flexible.<a href="https://onionshare.org" rel="nofollow noopener" translate="no" target="_blank">https://onionshare.org</a></li></ul>

Kevin Karhan :verified:<a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@delta</a> <a href="https://kolektiva.social/@leaf" class="u-url mention" rel="nofollow noopener" target="_blank">@leaf</a> <a href="https://mastodon.social/@n0iroh" class="u-url mention" rel="nofollow noopener" target="_blank">@n0iroh</a> the closest "<a href="https://infosec.space/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a> / <a href="https://infosec.space/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#P2P</a>" I've seen is <a href="https://infosec.space/tags/OnionShare" class="mention hashtag" rel="nofollow noopener" target="_blank">#OnionShare</a> [<a href="https://onionshare.org" rel="nofollow noopener" target="_blank">made by</a> <a href="https://infosec.exchange/@micahflee" class="u-url mention" rel="nofollow noopener" target="_blank">@micahflee</a>]... Tho I think the true <a href="https://infosec.space/tags/future" class="mention hashtag" rel="nofollow noopener" target="_blank">#future</a> will be <a href="https://infosec.space/tags/decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralized</a>, <a href="https://infosec.space/tags/federated" class="mention hashtag" rel="nofollow noopener" target="_blank">#federated</a> and <a href="https://infosec.space/@kkarhan/113896637368898514" rel="nofollow noopener" target="_blank">similar to eMail</a>...<ul><li>Personally <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMEMO</a> is a good fit. I do think that <a href="https://infosec.space/tags/deltaChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#deltaChat</a>'s approach to using <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PGP</a>/MIME is good and can work even in more restrictive scenarios (i.e. corporations when <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> & <a href="https://infosec.space/tags/Messaging" class="mention hashtag" rel="nofollow noopener" target="_blank">#Messaging</a> require indexed archives for compliance reasons!)...</li></ul>

Jeff Horton :canada:Students: "I thought this class was about cloud computing and how useful and cheap it is, why do you keep telling us that it is terrible and expensive?"Me: "Experience"<a href="https://mstdn.ca/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloud</a> <a href="https://mstdn.ca/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#aws</a> <a href="https://mstdn.ca/tags/gcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#gcp</a> <a href="https://mstdn.ca/tags/azure" class="mention hashtag" rel="nofollow noopener" target="_blank">#azure</a> <a href="https://mstdn.ca/tags/computing" class="mention hashtag" rel="nofollow noopener" target="_blank">#computing</a> <a href="https://mstdn.ca/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a>

Kevin Karhan :verified:<a href="https://hollow.raccoon.quest/@raccoon" class="u-url mention" rel="nofollow noopener" target="_blank">@raccoon</a> nodds in agreement<ul><li>The correct term would've been <a href="https://infosec.space/tags/CashGrab" class="mention hashtag" rel="nofollow noopener" target="_blank">#CashGrab</a> <a href="https://infosec.space/tags/content" class="mention hashtag" rel="nofollow noopener" target="_blank">#content</a> to encompass <a href="https://infosec.space/tags/ingame" class="mention hashtag" rel="nofollow noopener" target="_blank">#ingame</a>-<a href="https://infosec.space/tags/cosmetics" class="mention hashtag" rel="nofollow noopener" target="_blank">#cosmetics</a> and other lazy, low effort high price post-launch additions...</li></ul>I mean people also call <a href="https://infosec.space/tags/Discord" class="mention hashtag" rel="nofollow noopener" target="_blank">#Discord</a> instances "<a href="https://infosec.space/tags/Server" class="mention hashtag" rel="nofollow noopener" target="_blank">#Server</a>" when it's literally a "<a href="https://infosec.space/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a>" application running on <a href="https://infosec.space/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#aws</a> aka. "<a href="https://infosec.space/tags/MoneyBurningParty" class="mention hashtag" rel="nofollow noopener" target="_blank">#MoneyBurningParty</a>"...

Aria Burrell 🇨🇦What are some good <a href="https://xn--xxa.computer/tags/FaaS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FaaS</a> / <a href="https://xn--xxa.computer/tags/Serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#Serverless</a> Function / Hosted <a href="https://xn--xxa.computer/tags/Lambda" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lambda</a> providers that support <a href="https://xn--xxa.computer/tags/Golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#Golang</a> <a href="https://xn--xxa.computer/tags/Go" class="mention hashtag" rel="nofollow noopener" target="_blank">#Go</a> ?I'm on Digital Ocean right now and while I generally love their stuff, they only seem to have support for Go 1.20.

Matt BacchiAfter re:Invent I spent some time reading about serverless sustainability (both in general and specifically within AWS) and did a write up on the state of sustainability at the end of 2024. Great news: there are some interesting trends and tools to help you tailor your operations to be more carbon aware.Check out my blog at <a href="https://bacchi.org/posts/survey-serverless-sustainability" rel="nofollow noopener" translate="no" target="_blank">https://bacchi.org/posts/survey-serverless-sustainability</a><a href="https://hachyderm.io/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a> <a href="https://hachyderm.io/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#aws</a> <a href="https://hachyderm.io/tags/sustainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#sustainability</a> <a href="https://hachyderm.io/tags/lambda" class="mention hashtag" rel="nofollow noopener" target="_blank">#lambda</a> <a href="https://hachyderm.io/tags/climate" class="mention hashtag" rel="nofollow noopener" target="_blank">#climate</a> <a href="https://hachyderm.io/tags/greencomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#greencomputing</a> <a href="https://hachyderm.io/tags/lowcarboncomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#lowcarboncomputing</a> <a href="https://hachyderm.io/tags/greensoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#greensoftware</a>

Frankie ✅<a href="https://mastodon.social/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#tech</a> <a href="https://mastodon.social/tags/technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#technology</a> <a href="https://mastodon.social/tags/computing" class="mention hashtag" rel="nofollow noopener" target="_blank">#computing</a> <a href="https://mastodon.social/tags/servers" class="mention hashtag" rel="nofollow noopener" target="_blank">#servers</a> <a href="https://mastodon.social/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a>

🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸> You can now develop <a href="https://mastodon.social/tags/AWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AWS</a> <a href="https://mastodon.social/tags/Lambda" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lambda</a> functions using the <a href="https://mastodon.social/tags/Nodejs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nodejs</a> 22 runtime<a href="https://aws.amazon.com/blogs/compute/node-js-22-runtime-now-available-in-aws-lambda/" rel="nofollow noopener" translate="no" target="_blank">https://aws.amazon.com/blogs/compute/node-js-22-runtime-now-available-in-aws-lambda/</a><a href="https://mastodon.social/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a> <a href="https://mastodon.social/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a> <a href="https://mastodon.social/tags/node" class="mention hashtag" rel="nofollow noopener" target="_blank">#node</a> <a href="https://mastodon.social/tags/awsLambda" class="mention hashtag" rel="nofollow noopener" target="_blank">#awsLambda</a> <a href="https://mastodon.social/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloud</a> <a href="https://mastodon.social/tags/amazon" class="mention hashtag" rel="nofollow noopener" target="_blank">#amazon</a>

Recent searches

Search options

Administered by:

Server stats:

#serverless