ju
@ju@snac.nugole.it
I really got out of my comfort zone with this one!
I had this idea in my mind for the past week or so and I really wanted to try something drastically different from my usual digital pieces.
I wasn’t sure about it for so long, but I actually love it!
#art #illustration #digitalArt #Fall #Autumn #Birds #BirdsOfMastodon #Cute #CutePosting #Artist
Brokeback Mountain 2
Fun fact: the time it takes us to create one comic is roughly the same as a transatlantic flight. Except there are no free drinks, no movies and the turbulence is emotional.
If you've ever wished you could buy us that airplane tomato juice: Patreon is basically that, but better.
You'll get exclusive comics, behind-the-scenes content, and the warm feeling of keeping two sleep-deprived artists alive!
Red Hat Being Phased Out of Existence (Like Many Other Companies That IBM Bought)
I am not surprised. Red Hat was already pulling some shenanigans with the CentOS drama and then IBM sealed the deal. When big tech buys you out often you die slowly. This is not new or uniq to IBM + RedHat.
A demon appeared in the summoning circle. It was wearing pyjamas.
"I summoned thee to give me knowled-"
"Really?" the demon said. "You have the internet these days, the world's knowledge a click away. Nobody's summoned me in years."
"You have all knowledge. Why did I summon thee?"
"... oh shit."
Someone is advocating to stick all our docs in an AI “Skill” to surface information instead of having people search for and actually read the documentation.
Not only is that the wrong approach for AI-driven data exposure, it’s also just fucking stupid. Our docs search is good. And if you have the brain atrophy that leads you to rely on AI, it can already do the web search for you and return results.
#Covid, casi raddoppiati in un mese. "Ma per la gran parte delle persone è come un raffreddore". Si sa che i sequel funzionano meno.
Banconota da 10 pesos dell'Uruguay, 1887, con Cavour e Garibaldi.
https://commons.wikimedia.org/wiki/File:BilleteGaribaldi.jpg
@GustavinoBevilacqua Garibaldi è unico uomo al mondo che in un periodo aveva il seggio in 3 parlamenti di 3 paesi diversi, Italia, Francia e Uruguay. Che mito.
Tra l'altro per le tue ricerche saintsimoniane, Garibaldi si dette alla politica solo a 27 anni, prima se ne disintetessava, ma poi, da marinaio, incontrò il socialista utopista Barrault su una nave che andava in esilio e venne convertito alla rivoluzione.
...
@ju ha fretta di chiudere prima dell'inverno
Va' che traffico c'era stasera in cortile.
...hazz..ti tocca fare il turno di notte di posteggiatore abusivo 😱🫣
(😆😜 Belle bestie 🥰😍)
@stefano_zan wow 🤩
Una gara?
@kristiana no, non so perché hanno i numeri sulle fiancate. È solo un gruppo di collezionisti-turisti che sta girando l'Italia per visitare i carrozzieri di supercar. 🙄🤷🏽♂️
Ah giusto.
So che tutti voi lo volevate sapere.
Non potevate farne a meno.
Ma...
Oggi...
Sono...
Quindici...
Anni...
Di...
Attività...
Tanti auguri a noi
Consideratevi tutti già pagati da bere virtualmente!
Congratulazioni per non essere ancora esplosi di fronte alle richieste della vostra amabile clientela!
@GustavinoBevilacqua @rapitadaglialieni
Prendo come un grandissimo risultano il non essere in galera.
@Yaku @rapitadaglialieni
Avete aperto con la scuola che era giá iniziata, quindi nel primo anno di attività vi siete risparmiati il calvario dei libri di scuola che arrivano\non arrivano. Siete machiavellici!
Auguri! 👏🏼👏🏼🥳🥳💪🏼💪🏼
Thank you, @dch@bsd.network
One of the peculiarities of littleFedi is that it was developed and tested first on the BSDs, then on illumos, and only later on Linux.
The first public instance, my own @stefano@rpi0w.stefanomarinelli.it account, runs on a Raspberry Pi Zero W with NetBSD.
I don’t think many social platforms have started out on NetBSD in recent years.
#NetBSD #FreeBSD #littleFedi #Fediverse
I want to publicly thank @dch
The FreeBSD port of littleFedi was already ready at release time, and it’s really well done.One of the peculiarities of littleFedi is that it was developed and tested first on the BSDs, then on illumos, and only later on Linux.
The first public instance, my own @stefano@rpi0w.stefanomarinelli.it account, runs on a Raspberry Pi Zero W with NetBSD.
I don’t think many social platforms have started out on NetBSD in recent years.
#ThankYou #RunBSD #NetBSD #FreeBSD #OpenBSD #illumos #OwnYourData #Fediverse #littleFedi
Whoever makes decisions at Mozilla around Firefox is thinking with a glute-based substrate, to put it lightly.
It's a good thing desktop Firefox hasn't lost about:config, because between Profiles, Accounts, the VPN, the Relay, and now the ugly Rounded Tabs nonsense, I find myself having to turn off unwanted pish more and more often.
On which note: in about:config, search for Nova and toggle all 5 entries to false and you should be back to normal tabs. #firefox
@narpoleptic My main objection to the rounded Nova tabs is that my brain sees them and goes “oh, search box”. They look like you ought to be able to type inside them.
Turning that off took care of that, so thank you.
Speaking of which, what’s with the excessively-rounded corners that are sweeping the UI world currently? It’s one of the least appealing features of Apple’s Liquid Glass. It feels like we’re back in 2010 when `border-radius` hit CSS & suddenly everyone was “Look! Rounded corners!”
@angusm @narpoleptic Fashion repeats when the last round is long enough in the past to be either forgotten or looked upon kindly because if nostalgia.
Frequency increases with a decreasing number of options. Corners can either be pointed, slightly rounded or very rounded. That's a limited set of options, so history repeats fast.
Besides, while rounded corners have been invented before, but they have not yet been invented by everybody. This time it's Apple's time to invent them.
@HolgerPieta @angusm @narpoleptic Give me back my 2012-style skeumorphic icons and jelly bean coloured window scroll bars!
Just had to deal with a bunch of wind turbine conspiracy theories at #StateOfEU, this polite political event I’m at in Brussels. Damn we‘re fucked. Fucked. Our notional political elite is believing in utter complete garbage.
Turbines kill birds. They don’t you jerk. Your cat is more a danger to birds. #StateOfEU
Edit: for clarification - the number isn’t zero. But it’s not a significant issue.
We know beyond any doubt that wind as part of the renewable energy mix is vital. It’s cheaper than nuclear. And sure, turbines make some noise - so don’t build them next to homes. Which you don’t anyway. #StateOfEU
Also making the case for new nuclear in France right now after the headaches nuclear had with cooling water this summer. WHAT? #StateOfEU
“And those turbines you see in Brandenburg approaching Berlin are so UGLY!” he went on. Climate change, that’s ugly. #StateOfEU
And there was another line. “It’s rich landowners in Brandenburg taking the subsidies from the state to build wind turbines”. This is an equality / distribution issue, not an energy issue! Think of the opposite: “we shouldn’t build turbines there because the land owners are rich!” Errrr… #StateOfEU
This is the ethical point here: NOTHING is more important than combatting climate change. Nothing. Without a liveable planet nothing else works. I’ll have a debate about the numbers, and how to decarbonise. But I’ve no time for whataboutism, nimbyism or conspiracy theories. #StateOfEU
Complex software behaving in unexpected and sometimes harmful ways has been a persistent problem since software was invented. The phenomenon used to be called “bugs” or “defects”, but I guess “going rogue” sounds cooler. It also implicitly frames “rogue” behavior as some kind of inexplicable exception, as if software is somehow usually trustworthy. https://www.nytimes.com/2026/09/25/technology/openais-ai-us-government-websites.html?unlocked_article_code=1.EFE.RfLT.x6YBjHa1PMz6
“Our software went rogue!” No. You programmed it wrong.
If you don’t want your system to be able to lock people out of the pod bay doors, you can just program or configure it to not have the capability to lock people out of the pod bay doors. This remains true whether your system is written in assembly language or C++ or Python or uses some fancy machine learning model.
“It never occurred to us that our system that has exclusive control over the pod bay doors would take control over the pod bay doors” seems like something you might have thought about a bit more before you connected it to the pod bay doors.
Per la connession usa connman che meh...comunque permette di configurare dns e ntp.
Bonus1: usa iptables, è possibile configurare un firewall vero senza ricorrere ad altre applicazioi.
Bonus2: è predisposto come client per wireguard.
For #ThrowbackThursday and the first day of October, here's one of our former foster kittens, Ravioli. He had ghost stripes!
Hi Folx!
I'm Raeyn, and I like to make things. Things include:
- Dice jewellery (much of it pride flag themed)
- Other pride things, including
-- Seed bead bracelets when the mood takes me (non pride ones too)
-- Tiny-ass cross-stitch flags for keychains/necklaces (like, 1" across)
-- Bigger cross-stitch flags for hanging (3" across)
- Rude cross-stitch patterns (the Sweary Fruit series)
- Bigger, snarky wall art
There's also semi-precious gemstone earrings and necklaces, and slightly dubious seed bead rings.
- Craft supplies, namely:
-- Stitch markers for both knitting and crochet
-- Needle minders for embroidery/cross-stitch folx
All of it is made by me and me alone, and I'm always happy to discuss commissions if it's within my ability to do (especially other pride flags).
So uh, yeah. Consider shopping from a one woman, disabled, queer outfit. Pay for my craft supplies! xD
what inspired me this week: @littlefedi_official
I LOVE smol, frugal and tiny computing.
@sushee @littlefedi_official We don't usually need large and crowded hotels to live, but a smol, tiny and comfortable house we can call "home".
In questi giorni non potevo scrivere al computer ma mi stava frullando in mente un #ragionamendo
da scienziato politico della #magnagraecia dal titolo "Il campo largo non esiste"
Se vi piace mettere like, se non vi piace facitv e cazz vuostr https://paper.wf/ragionamendo/il-campo-largo-non-esiste
@gino in realtà la legge elettorale sarebbe un proporzionale con premio di maggioranza, quindi mettere su una coalizione del modello "Campo Largo", non solo ha senso ma non parteciparvi penalizzerebbe i 5 Stelle.
Tutto questo ammesso e non concesso che la legge vada a compimento nella maniera che conosciamo, dato che ora come ora sembra scritta esclusivamente per Fratelli di Italia e nella bozza all'articolo 1 la Meloni ha fatto scrivere "Salvini e Tajani pezzi di merda" in times new roman 50
@unknow l'idea è che nessuno raggiunge il premio e quindi è solo proporzionale, come ho scritto forse un poco una chiavica
@gino Eh ma il punto è che ci sono un po' troppe variabili per dire che il pareggio sia certo, quindi al momento formare un alleanza ha senso. Poi se si arriva al pareggio esiste l'opzione non certa ma comunque possibile che si arrivi a un governo PD - FDI e per i 5 Stelle sarebbe un win-win perchè da un lato potrebbero dire "mica l'abbiamo rotta noi l'alleanza" e dall'altro potrebbero presentarsi come unica opposizione a sinistra (AVS non la considero perchè è una costola del PD nata per garantire un posto di lavoro a tutta la famiglia Fratoianni)
@unknow sì sono d'accordo che non sia prevedibile un pareggio, resta comunque tutto abbastanza incasinato, con l'aggiunta dei franchi tiratori
che fanno fallire la legge elettorale e si va subito al voto con la precedente. In tutto ciò continuo a pensare che Conte possa abbandonare la nave del Campo largo in ogni momento magari per ragioni che non ci sono ancora note, calcoli elettorali a parte
Eh no, non basta la buona volontà per compiere un gesto rivoluzionario.
Leggetevi la storia di Felice Orsini, se non la sapete.
@GustavinoBevilacqua ma è parente?
Di chi?
@GustavinoBevilacqua ma come chi! Il nostro Putiniano di ferro,
Boh!
(quella inglese non è invischiata in una causa legale <https://en.wikipedia.org/wiki/Alessandro_Orsini_(sociologist)>)
RE: https://littleone.littlefedi.social/@littlefedi_official/01a0f644-8ed6-7a7d-ade6-46f4c0a74f41
littleFedi is out!
The Little Computer People Present littleFedi: Our First Public Release
"Hi,
We would like to show you a small project we've built and used over the last few years.
It's a Mastodon-like platform that federates using its own protocol and can work even without HTTPS or public Internet access. Many of us have restrictions on our communications, and this project has helped us stay in touch and have our own social network. We'd love to show it to you and hear what you think, because your OwnYourData message really resonates with us."
The Story
And this email sat ignored for weeks.
It came from an anonymous, generic mailbox, with an even more anonymous and suspicious subject. The spam filter had classified it as, well, spam, for other reasons too. Only when I checked the spam folder again, weeks later, did I move it to the Inbox. "Why not?", I thought. And I asked to see what they had built.
There was no way for me to connect to one of their instances. They trusted me and sent me the code which, although fragmented and loosely put together, compiled and ran natively on FreeBSD. But before that: "We only ask you to never say anything, at least until we're ready. We don't want to be visible and, inevitably, judged or attacked. We tried something else before and backed away. Our software isn't high quality and we know it. But it works, for us, and we have fun building it. When it works we're happy, shut away in our rooms, often in the middle of the night. Sometimes, joking, we say we're like little people living inside our computers and that, thanks to this software, we can talk to each other."
At that moment I smiled and thought of a 1985 video game, from my childhood, that was quite revolutionary at the time: "You're like Little Computer People". They liked it. And that's how the group got its name: the Little Computer People.
My first test went well. I was immediately struck by the lightweight interface. "We have old computers, slow hardware. It has to be light. It just has to!". Abundance led to waste. And yet I preferred that light interface, even if incomplete, to many of today's heavy social interfaces, commercial or not. But the code had gaps, pieces held together with duct tape, unfinished parts. They knew it, they had told me, and they were ashamed of it. "You should be proud of what you're doing. It's beautiful", I wrote to them. "We'll never release it."
The battle, if we can call it a battle, was a long one. They weren't far from making it ActivityPub compatible, and there was already a basic draft implementation (tested only with snac). "We don't want to show it, we don't feel up to it. We don't want to step on the toes of others like snac or GoToSocial, who have done a far better job than we have". I tried to convince them, also because the implementation was moving forward and the results were really encouraging. But no, they didn't feel ready. Until, luckily, one of them made a proposal: "We could release it... but we don't want to be seen. We want to stay in our computers and enjoy our code. We don't want to read praise, criticism or comments. We just want to have fun. Would you like to be one of the Little Computer People too? The human who talks to humans while we keep having fun?". I felt honoured and accepted. Explaining, among other things, that Open Source is not a battle. We are not in an arena, where the existence of one solution means crushing another.
This software is not a slight against Mastodon or snac or GoToSocial, but one more choice. Nobody gains. Nobody loses. It's there. It exists. It's something beautiful, one more thing in the world. They agreed, leaving the license undecided and keeping the strictest confidentiality.
The software had no name. But after we came up with the group's name, we affectionately called it our "little social". After the first real, complete ActivityPub federation (with proper tests), the current name was chosen among the alternatives: littleFedi.
"You have more experience... what should we implement?". I thought about it, looked at what was still "in the oven" and what I'd really like to have. I made a list, detailed and very long. But the most important part, for me, was blogging.
Then something happened, and development had to stop. Some devs could no longer work on it. Others weren't able to touch what the others had built. There was only one person who could carry on, albeit slowly, but their computer had broken and they could only communicate by smartphone. They couldn't buy another computer. And yet, a few days later, they received one. Ready to go. With FreeBSD inside.
littleFedi risked stopping right there, with part of the team still against any public release, at least at that point. But sometimes things work themselves out just when you least expect it, and in a short time the "little" humans were back in their computers, having fun, unwinding, creating something beautiful. Until a hot day this summer, when I asked their permission to make my first littleFedi instance public, running on my Raspberry Pi Zero W. One of them was against it at first. Then changed their mind. And I did it, announcing it to the world: https://rpi0w.stefanomarinelli.it/@stefano/blog/2026/07/01/littlefedi-light-yet-complete/
They don't want to interact with the world, but I still decided to show them the comments - all positive. That evening, the private test instance started showing (without me knowing) balloons and streamers every time we logged in. It was a party. And that made my next task easier, leading to the first public instance: littleOne
When I announced it, a lot of friends chose to join the test, and thanks to them a huge number of issues were found and fixed. A huge thank you to them. I acted as a bridge between them and the team, fixing and implementing what I could myself. I'm not primarily a dev but a system administrator, and I prefer not to touch what I don't know. The enthusiasm of the Little Computer People, though, was obvious even without them saying it: bugs were fixed in minutes, hours at most. We merged test branches quickly, so the friends on littleOne could try them.
Towards a Release
The last two months saw a lot of development, but mostly focused on reviewing and cleaning up the code. With one single goal: a first public release. The chosen license, after some thought, is MIT. The point is to give it to the world. This software was born from people who want to communicate with other people, and that's what matters. It's a means, not an end. Because those who don't have freedom dream of freedom without restraints.
There is much more documentation than what we're releasing today, along with tests and internal material that still needs to be reviewed. Some parts describe the project as it was designed, not necessarily as it was later implemented. Others haven't been checked enough yet to be published as reliable documentation. So we chose to release now what's ready: all the code needed to run littleFedi and enough documentation to get started. Not everything has been tested and certified in all the combinations we'd like, but what we're releasing is mature enough to be tried and used.
As of today, littleFedi is available from the downloads page at https://littlefedi.org. There won't be versioned releases for now, just snapshots of the code, both as source and as prebuilt binaries. What matters today is putting the tool in people's hands. Later, when things are ready enough, we'll probably move to good old git, on the BSD Cafe Forgejo. The sources already point there, but that project is currently private (and intentionally empty).
What Is littleFedi
So what exactly are we releasing today?
littleFedi starts from a very simple idea: owning your own social space shouldn't require complex infrastructure. In its basic form it's a single static binary, a configuration file, SQLite and your media on the filesystem. You copy it to a machine and start it. The minimum "certified" target today is my Raspberry Pi Zero W running NetBSD, powered over USB by my switch. It's designed for small, single-user instances, but also for larger ones, with the option to use S3 for media storage (the main space problem of single-user Mastodon instances) or PostgreSQL instead of the built-in SQLite. How large can an instance be, exactly? We don't know yet. The code is there, ready to be tested. We'll leave that for you to find out! You can also already migrate the storage (live), not the databases yet (but there's a partially implemented draft, so that will come too).
There are some rather unusual features, bringing together some of the nice ideas found in other implementations. It's written in Go, and Go allowed us to do something I care about a lot: FreeBSD, illumos, Linux, NetBSD and OpenBSD are not secondary ports of software designed only for Linux. Each one has its own operational documentation. It has a low power mode, lets you schedule a post or set, post by post, an expiration (propagated to other instances). It has a light and simple web interface, yet complete, with no frills, reasonably usable even without JavaScript. Care went into making the PWA pleasant and usable and, even with a few bugs left, it's in my opinion one of the best ways to use littleFedi. And, yes, if you don't want to use its web interface, littleFedi also speaks the Mastodon API: many existing clients can connect directly. It supports emoji reactions. It supports push notifications. Post visibility follows the usual Fediverse model, with two additional variants: Local and Local Unlisted. Because not every post we write needs to leave our instance. And, speaking of federation, it has a fairly clean approach: by default, it federates with everyone. But it also supports blocklists and allowlists. Yes, allowlists: you can choose a list of instances to federate with, and that's it. Only those. Activities to and from all the others will be silently dropped, to give you an experience tailored to your expectations. "Filter bubble?". If you want to call it that. I call it the freedom to decide who your instance talks to.
And there's no need to doom scroll for fear of missing something: timelines are chronological, yes. But there's an optional Catch-up for when you come back after a few hours or days. It lives on a separate page and never decides what shows up in your timeline. If it shows you something, it also tells you why.
But there are too many features to list here, it would become a boring list. The only way is... to try it. Worth mentioning, in my opinion, for how peculiar they are, are two main features: littleMesh and Blog.
littleMesh, Blog and OwnYourData
The first, littleMesh, is an alternative transport mode for federation. Remember the first email, when they talked about their own federation able to work even without public Internet? That idea didn't go away. It evolved into littleMesh. Two littleFedi instances can communicate even behind NAT or CGNAT, with no public address, DNS or inbound ports. All it takes is an external lighthouse. If you also want to talk to the traditional Fediverse, an HTTPS gateway comes into play. ActivityPub, though, stays ActivityPub.
The blog feature is something I had in mind for a long time, and many of the friends who tried it on littleOne loved it. I like how WordPress federates into the Fediverse, but it's a CMS that federates. I wanted something different: a Fediverse platform, with a decent editor, that generates a static site. Simple, BSSG style, but complete and "eternal". HTML files, no need for JavaScript or images. Text is text, and I've always wondered why extra computation should be needed to show…words. When I saw the first draft, I fell in love with it. And I know those sites will still be readable in 10, 20, 30 years. Even without littleFedi. Because social networks are, by nature, ephemeral, but our ideas and thoughts sometimes deserve to stay. And above all, you're not publishing the same thing twice. The post is the same one. It federates normally and, if you choose it as a blog post, littleFedi also generates a static version of it. There's no CMS to keep in sync with the social network.
But littleFedi doesn't want to cage you or hold you back. It supports account migration (to and from other instances), and it also lets you export a full archive with all your content, which can then be imported into another littleFedi instance. Sure, in that case domain and handle will change, but the content will stay, just at a different address. OwnYourData: it doesn't matter which drawer it's in, as long as it's your drawer. And, just like Mastodon, you can self destruct your instance: take it off the Fediverse, politely saying goodbye to the other instances and asking them to remove our keys and content from their databases. Because the Little Computer People don't want to make noise or bother anyone. They just want to communicate, and leave with a smile when it's time.
Ready?
In the last few weeks some friends have taken a look at the code and confirmed what we already knew. It may not be textbook code, but we're releasing it. There are well-engineered parts, others much less so, some to be reworked, many to be analysed, but it's a step. If we aimed for perfection we would never release, and promises are promises.
I'm ready. The Little Computer People are ready. And the code is there, for anyone who wants to try this new communication project. The roadmap is already full of nice things to do, and more will be added. We're not in a hurry, it's not a competition. We want to do things properly.
For your first instance, all you need is a computer and a reverse proxy. Download the source and build it, or grab the prebuilt binary from the downloads page:
./littlefedi init ./littlefedi --config littlefedi.tomlAnd you're ready to federate with the world.
Happy communicating, and use it well. We're going back into our computers.
Stefano - @stefano@bsd.cafe
@stefano Yippeeeeeeeee! Play time 😉😀
Thank you & congratulations Stefano and the Little Computer People.
Mastodon.social has been down for almost an hour. Happy to have this other place to check in with the rest of the Fediverse. Hello friends 👋
...
...
immagino
ecco
.
@ju Se GTS fa come mastodon, quando vede un account gli dà un suo ID locale che è diverso da quello originale.
Quindi deve ricordare tutti quelli che ha visto, anche di sfuggita (citazioni di gente che non hai mai letto eccetera) nel caso li veda di nuovo.
snac invece tiene l'ID originale (che insieme al nome dell'istanza comunque è sufficiente) quindi dovrebbe evitare tali problemi.
@ju Ah e probabilmente si ricorda anche l'intero profilo, non solo l'ID originale (che sarebbe sufficiente ad andare a riprendere il profilo se serve). Ora tenerlo per un giorno va be' si risparmia di andare a chiedere continuamente, ma poi si potrebbe tranquillamente cancellare (ma mi pare che GTS non sia particolarmente bravo a cancellare quello che non serve più).
Cioè ma boh...ma fammeli cancellare ad un certo punto?
Ma non solo gli account, anche i post: i post non fatti da me che qualcuno in qualche angolo del fediverso ha scritto nel 2022, possiamo cancellarli ad un certo punto? Magari tenerli solo se sono nei segnalibri...
Ora certo io ieri ho fatto un attimo una puttanata perchè pensavo che gli accounts nella relativa tabella fossero solo quelli fuori dall'istanza e invece...no. Bisogna avere una tabella users e una tabella accounts e naturalmente l'utente compare sia negli users sia negli accounts e no, non c'è nessuna constraint che ti impedisce di cancellare accidentalmente un accounts che sta anche nella tabella users...insomma...mi son cancellata da me.
Ma insomma... 😕
Vabbeh...
Ah e non ho trovato una documentazione su cosa siano le varie tabelle, mi rimarrà per sempre il dubbio su cosa fosse "tombstones".
@ju tombstones sono i post che sono stati cancellati e si ricorda la posizione che avevano in un thread (in particolare, a cosa rispondevano, e cosa rispondeva a loro), senza ricordare il contenuto. C'è anche un corrispondente tipo di oggetto di ActivityPub.
1/2
@ju Su mastodon, quando un post viene cancellato il thread s'incasina completamente e diventa impossibile ritrovarlo a partire da una risposta "dopo" un post cancellato. Evidentemente GTS vuole evitare che succeda questo.
Ovviamente l'ideale sarebbe che queste cose se le ricordasse solo l'istanza da cui venivano in origine questi post cancellati... ma è probabile che questa istanza sia mastodon e quindi non succederà mai.
2/2
Entra cliente.
La serve @rapitadaglialieni
Intanto voleva una confezione di pastelli con "solo colori chiari".
Certo signò, li fanno solo per te.*
Le diciamo che se li vuole solo chiari, deve prendere quelli sfusi.
- Ma li avete quelli più cicciotti?
- No abbiamo quelli medi (diam. 3.8 ndr.)
Li guarda...
- Ah, ma non li avete più piccoli?
- No signora, sfusi abbiamo solo quelli medi.
Nel frattempo potrebbe fare pace col cervello eh?
- No perché mi servono per colorare
Mi sfugge un "ma pensa" forse a voce troppo alta.
Sicuramente a voce troppo alta perché improvvisamente s'è zittita.
* esistono, sono confezioni speciali che ogni tanto qualche produttore fa, ma sono difficili da trovare e da vendere.
@Yaku @rapitadaglialieni > No perché mi servono per colorare
Che non pensaste che li usa come dildo.
@oblomov @rapitadaglialieni che diavolo è la Sharpie challenge?
@Yaku @oblomov @rapitadaglialieni a me viene in mente solo Homer piccolo che vuole vedere quanti pastelli a cera riesce a ficcarsi su per il naso, sarà una cosa simile?
@las_lallero non abbiamo modo di saperlo purtroppo
@oblomov @rapitadaglialieni
@Yaku @las_lallero @rapitadaglialieni diciamo che non si infilano nel naso.
@Yaku @las_lallero @rapitadaglialieni
Al maschile consiste nel provare ad infilarlo su per l'uretra.
Al femminile è quanti si riesce ad infilare in vagina (uno accanto all'altro, chiaramente, tipo quando ne prendi un mazzo in mano)
@Yaku @oblomov @rapitadaglialieni vabbè ma la scala tra le due opzioni è troppo diversa scusami
@las_lallero @Yaku @rapitadaglialieni chiaramente nulla ti impedisce di applicarla anche/solo ai buchi comuni.
@las_lallero @Yaku @oblomov @rapitadaglialieni
"Pronto soccorso hate this one weird trick!"