this post was submitted on 17 Feb 2026
192 points (99.5% liked)

196

6027 readers
1114 users here now

Community Rules

You must post before you leave

Be nice. Assume others have good intent (within reason).

Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.

Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.

Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".

Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.

Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.

Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.

Avoid AI generated content.

Avoid misinformation.

Avoid incomprehensible posts.

No threats or personal attacks.

No spam.

Moderator Guidelines

Moderator Guidelines

  • Don’t be mean to users. Be gentle or neutral.
  • Most moderator actions which have a modlog message should include your username.
  • When in doubt about whether or not a user is problematic, send them a DM.
  • Don’t waste time debating/arguing with problematic users.
  • Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
  • Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
  • Ask the other mods for advice when things get complicated.
  • Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
  • Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
  • Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
  • Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
  • Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
  • First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
  • Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
  • No large decisions or actions without community input (polls or meta posts f.ex.).
  • Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
  • Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.

founded 1 year ago
MODERATORS
 

*the image of cat and the green > symbols were there before I edited the image

I was feelin lazy, so here we go, have a post-

should probably post more, i feel good doin things.

anyway--- i hope u are doing well! <3

all 27 comments
sorted by: hot top controversial new old
[–] riwo@lemmy.blahaj.zone 21 points 1 month ago* (last edited 1 month ago) (2 children)

what is serverless api? is it local?

[–] panda_abyss@lemmy.ca 39 points 1 month ago (1 children)

No, it’s an API where on requests a server is started up to run your code.

You don’t run the server, someone else does — hence “serverless”.

[–] infinitesunrise@slrpnk.net 5 points 1 month ago* (last edited 1 month ago) (1 children)

The moment I realized AWS Lambda is a scam was the moment I learned that you have to check if you need to clean up your runtime environment at function start, because it will sometimes reuse the same server between runs, because it's a server that they don't even bother to have behave as if it isn't.

[–] panda_abyss@lemmy.ca 7 points 1 month ago (1 children)

Hurray, “stateless function calling” now with 100% more state!

[–] python@lemmy.world 2 points 1 month ago

mhm we can have a little state... as a treat

[–] chisel@piefed.social 27 points 1 month ago (3 children)

The concept is that you basically upload code directly to the hosting service, then set up an endpoint that points to the code, and magically run it. "Serverless" because you never deal with server setup/config/load balancing/etc... And can pretend that your code runs on nothing if you so please.

[–] rtxn@lemmy.world 16 points 1 month ago (1 children)

Like saying that a Dockerfile or compose.yaml is "containerless" because you don't have to manually provision a container?

The future is fucking stupid.

[–] Retail4068@lemmy.world -4 points 1 month ago* (last edited 1 month ago) (1 children)

No, nerds actually getting riled up over the pedantics of this naming scheme is the sad thing. Like honestly, it's a hoot watching you all get riled up over the pretty decent and descriptive name.

REEEEEEEEEEEEEEEEEEEE THE SERVER IT'S REALLY THERE, IT'S JUST OBFUSCATED 🤣🤣🤣🤣

[–] Smorty@lemmy.blahaj.zone 10 points 1 month ago

calm down.... let the people yap.

[–] django@discuss.tchncs.de 15 points 1 month ago (2 children)

Is my delivered pizza flourless, because i don't deal with the flour and just get the pizza?

[–] python@lemmy.world 11 points 1 month ago (1 children)

Wouldn't it be more like your delivered Pizza is ovenless, because you don't need to set up/maintain your own oven?

[–] django@discuss.tchncs.de 2 points 1 month ago

Why not both?

[–] elfpie@beehaw.org 11 points 1 month ago

I guess it's a bakeless pizza.

[–] festnt@sh.itjust.works 4 points 1 month ago

it's also the same situation with wireless devices. it's not that there are no wires, it's that you don't have to deal with any wires

[–] hazl@lemmy.blahaj.zone 19 points 1 month ago

Just like so many "no code" solutions that only become truly useful once I figure out how to expose and modify the obfuscated code. But I don't talk about Microsoft anymore.

[–] NigelFrobisher@aussie.zone 5 points 1 month ago* (last edited 1 month ago) (1 children)

Had an argument with my architect about this once. He said its because serverless functions can be run on the edge as well, making them totally portable. I said that already exists and it’s called fucking executables.

[–] tiramichu@sh.itjust.works 8 points 1 month ago* (last edited 1 month ago) (3 children)

The real meaning of 'serverless' isn't that there's no server, but that the server is outside the scope of what you have to think about.

The least abstracted level is bare metal. You provision the server, install an operating system, and manage system level dependencies and security updates and all of it yourself.

Then virtual machines, where you manage the VM but not the host it runs on.

Then containerisation where you manage the container and dependencies, but no longer have to think about the OS or the OS security updates.

Then finally serverless, where you as an engineer concern yourself primarily with only the code, and the platform takes care of the rest.

So it sounds kinda weird as a name, but the intent is right, because it's all about where the boundary of responsibility is drawn.

Someone always has to think about the server, but in serverless that someone isn't you.

[–] kunaltyagi@programming.dev 1 points 1 month ago

I'll have oversimplification for 10 dollars please.

Virtual Machine: looks into, needs machines Cloud: looks into, is just renting Containers: looks into, we're now shipping the devs laptop Server less: looks into, has servers. Loft of them

[–] infinitesunrise@slrpnk.net 1 points 1 month ago

Except that you do still have to think about them, because the fact that they're still just servers means that they can and will have outages. They also tend to be insanely expensive on relative compute cost compared to a server that you still call a server, which means a lot more thinking about your budget.

[–] jan@lemmy.blahaj.zone 2 points 1 month ago* (last edited 1 month ago)

> NOSQL
> Look inside.
> SQL... and not only that, bunch of other stuff too.

[–] Xerxos@lemmy.ml 2 points 1 month ago

Of course it's called serverless because there are less servers! /s

[–] Septimaeus@infosec.pub 1 points 1 month ago* (last edited 1 month ago)

One of the many IT buzz phrases that make a lot more sense if you did things The Old Way but confuse the juniors tasked with learning it. Guess who needs to be convinced to adopt any new technology? Yes, people whose concept of “server” can be quite particular. So this corner of jargon jungle is specific to IT field sales IMO.

My favorite example has to be “Infrastructure as Code.” I’ve been chewed out for not using that one specifically. It’s never going to happen.

[–] AllHailTheSheep@sh.itjust.works 1 points 1 month ago

the term is incredibly stupid. however, serverless services like cloud run are super cool in that you can scale down to 0, which makes it ideal for things that only get used once in a while. the containers only take 2 or 3 seconds to spin up as well, and the no config scaling support is pretty nice.

[–] Retail4068@lemmy.world -4 points 1 month ago (1 children)
[–] Smorty@lemmy.blahaj.zone 2 points 1 month ago (1 children)

calm down lemmy world user, why do you put a link to the same post... you are commenting on?

[–] Retail4068@lemmy.world 0 points 1 month ago

It's a comment 🤣