Sir Uriel Fanelli

@smallcircles@social.coop Well, I play drums, but I don’t have a band, so I started experimenting with AI to make music. I play the drums myself — everything else is AI-generated, but the lyrics. The result is epic metal in Latin, which is probably not the kind of thing you easily find on the market today. https://m.keinpfusch.net/share/L5rKU39jta Honestly, I was surprised by how good the result turned out. In some ways, it feels more inspired than a lot of generic heavy metal from past decades. That’s why I sometimes find the strong rejection of AI music a little theatrical. Modern music production has already relied for years on heavy editing, autotune, quantization, synthetic sounds, and industrial production pipelines. We accepted all of that as part of the evolution of music, so I’m not sure AI is such a dramatic break from the past. Of course AI won’t replace human creativity, emotion, or musicianship. This was replaced by pop music already. But as a creative tool, especially for independent people who don’t have a full band or a studio behind them, I think it can open some genuinely interesting possibilities.

@smallcircles@social.coop @strypey@mastodon.nzoss.nz Honestly, I was mostly thinking about the discussions around Mastodon when it transitioned from 32-bit to 64-bit IDs. That said, your point does make sense to me. If, in the future, people start implementing new extensions — groups, marketplaces, or other features — they may gradually end up evolving in somewhat separate ecosystems. I think this is also part of the reason why projects such as Lemmy , federated marketplace experiments, or even Mobilizon can be difficult to integrate cleanly with the wider network: each tends to develop its own assumptions, semantics, and workflows. So I can see the argument for stronger capability discovery mechanisms, whether at the instance level or, in some cases, even at the individual user level.

@strypey@mastodon.nzoss.nz @evan@cosocial.ca @cwebber@social.coop @Mastodon@mastodon.social I'm afraid, my social skills aren't good enough for this. And since English is not my first language, I know that I will sound too aggressive or confrontative, just when I just want  to be clear. Quite often I need to edit using an AI, to be clear without looking aggressive. But I can't do it in person. What I'm saying is, the standard should be completely exhaustive, so that we don't discuss how to implement things, we just implement things. Whether a variabile should be 32 or 64 bit long like a discussion between Pleroma and Mastodon, should be specified in the standard. Cannot be that Eugen Rocko decides it is 64, and others must adapt, cause "If you heard about our documentation changing to specify IDs as 64 bit numbers yesterday…". In the telecommunication field, this is pure nonsense. You must be able to have a call with ANY phone device, ANY company, ANY country.

@elizayer and now, you will realize how unpopular you get, when you say that there is nothing to steal from people with no more skills or creativity.

@supertobi so, no flat earth, yet flat Nurnberg?

@amministratore @fediverso ed è dovuta dal fatto che l’istanza risulta abbandonata e priva di moderazione. incredibile  come Mastodon possa autoamministrarsi senza alcun system engineer. Che cazzo abbiano fatto la AI a fare, quando Mastodon puo' gia' amministrare un server, e anche se stesso?

@denkbeteiligung@digitalcourage.social @EUCommission@ec.social-network.europa.eu it takes the time it takes, as everythig

@strypey@mastodon.nzoss.nz @autistics@fedigroups.social @wronglang@bayes.club Although I find this when trying to express anything clearly and precisely in a text-only medium. Not just technical ones. the lack of body language could have a big price, IMHO.

@strypey@mastodon.nzoss.nz @evan@cosocial.ca @cwebber@social.coop @Mastodon@mastodon.social I get it. But here's the crux: my perspective may carry some bias from the telco world—think SS7 signaling, MAP, CAP, TCAP, all meticulously defined down to the bit level. In that realm, I never had to wonder if the other side truly adhered to ITU-T standards. If they declare "G.711," that's it—done deal. The same holds for G.722 or G.729 when voice codecs are in play. Contrast this with ActivityPub, where I've implemented the W3C spec faithfully, only for everything to crumble due to some undocumented "variant," or disputes over key propagation. None of this should happen if the presentation layer is rigorously specified. That said, if voice calls à la WhatsApp are on your radar, Article 7 of the DMA is worth a look. Even beyond pure telco, SIP uses SDP to negotiate sessions and codecs dynamically, ensuring smooth interoperability. Yet no one second-guesses the codecs themselves: Opus (RFC 6716, the IETF standard for WebRTC) is crystal clear, with G.711 and G.722 as fallback anchors for legacy compatibility. Nobody dares claim, "Sorry, this is my version" (well, Cisco and Microsoft have a storied history of such mischief, but they're the IT rogues—not role models). Here in the ActivityPub ecosystem, though, "my own take on the standard" is rampant—and the spec simply isn't precise enough to prevent it.

Qui trovi una lista di domini e la loro esposizione diretta al potere esecutivo statunitense. https://keinpfusch.net/sul-discorso-degli-autistici-inventati

@smallcircles@social.coop @strypey@mastodon.nzoss.nz There was this funny moment where Lemmy and Mastodon developers were in each other’s issue trackers explaining why the other side had implemented something incorrectly, and then the discussion simply faded out. To be honest, this is also one of the reasons why I am always a bit cautious about sounding offensive in these discussions. I come from the telecom world, and if, for example, a company like Logica publicly said that Mavenir had “the wrong implementation” of SS7, people would probably panic immediately. Because in telecom, that would effectively mean that depending on the equipment involved, you might not be able to call certain countries — or sometimes even customers of another provider inside your own country. The reaction would escalate very quickly. I can almost imagine people treating it as outright protocol heresy. This is why I fear to sound offensive. But this issue is heresy to me.

@alineblankertz@indieweb.social you clearly never read Marx, so you have ZERO idea of what "capitalism" actually means, I guess you just think is something which has to do with rich people. And if you don't know the proper definition of capitalism, I wonder if you know what the symptoms are.

@simontatham I don't think I could have used Thunderbird, in 2000! sure, thunderbird started in 2003, but at the time there was Eudora, which was even more powerful and supported IMAP4.1 very well. So you could have done it with Eudora, too.

@strypey@mastodon.nzoss.nz I will try to understand where I could contribute. The fact that I know many legacy telco protocols in considerable detail may still be useful, but I also believe that ActivityPub should start looking more decisively toward the future rather than remaining anchored to patterns inherited from the past. If you want my synthetic opinion as a system architect — or, as people prefer to say nowadays, a “platform engineer” — it would be roughly this: “ActivityPub is currently trying to do two things at the same time: it serializes and transports data, while also implicitly describing how the receiving side is expected to process that data — what constitutes a poll, a status, a like, a follow action, and so on. In distributed systems, this pattern already has a well-known name: RPC. From my perspective, the real question is therefore not whether ActivityPub should evolve in that direction, but how. Personally, I think a gradual transition toward a proper RPC-oriented model would make a great deal of sense, and gRPC would probably be an excellent fit for that evolution.” I would honestly prefer a “weakened gRPC” — a pragmatic, federation-friendly RPC model that keeps the good parts of typed contracts, explicit operations, streaming where useful, and clear interoperability rules — rather than continuing with what increasingly feels like SOAP on steroids: verbose objects, implicit behaviours, underspecified semantics, and a lot of hidden procedural meaning disguised as document exchange. One thing I believe ActivityPub could improve significantly is capability discovery. Right now, interoperability often relies on implicit assumptions, observed behaviour, and trial-and-error between implementations. Modern RPC systems such as gRPC usually provide explicit service reflection, feature negotiation, schema discovery, and version awareness. In a heterogeneous federated ecosystem, being able to formally discover which features a remote server actually supports would greatly improve interoperability and robustness, while reducing the current dependence on conventions and reverse engineering. And all of this could be described through a single .proto specification file, explicitly and unambiguously defining the RPCs, their semantics, supported features, and interoperability expectations. Which would end ambiguity. I suspect, this idea would make me quite unpopular there.

@tao I see your argument, but... given the amount of proofs which happens every year, to assess them against "the rest of the knowledge" doesn't scales that well. So get prepared, AI will enter the game hard, and more and more, every year.

@MostlyHarmless@thecanadian.social and Bob's boobs

@centralscrutinizer@ors.novababilonia.me @evan@cosocial.ca @strypey@mastodon.nzoss.nz @Mastodon@mastodon.social @cwebber@social.coop "Der Musolini", to be precise. With the german pronunciation like this: https://www.youtube.com/watch?v=eYcUGO-ISXQ LOL.

@fedimedia @google @android @app @opensource vedo che continuate a mescolare cose: quella tecnologica e quella legale. Il vostro telefono NON e' MAI stato davvero vostro, come non lo e' un OS come WIndows, o MacOS. Vi viene concesso l' uso, mediante una licenza. "Licenza" non vuol dire passaggio di proprieta'. Significa che vi e' concesso l'uso. E ovviamente, qui entrano in gioco le condizioni di utilizzo. Legalmente, quindi , non cambia nulla. Android non era vostro prima, e non e' vostro dopo. Tecnologicamente, sinora c'e' stato un tradeoff abbastanza razionale tra la sicurezza della supply chain e la liberta' degli sviluppatori. Ma.... siamo in un anno nel quale gli attacchi alla supply chain si stanno moltiplicando e stanno diventando sempre piu' perniciosi, e specialmente ne aumenta la portata. Metti una libreria maliziosa su qualcosa di molto usato, e milioni la scaricano, o la usano per i loro programmi. Quindi, mi spiace, se volevate protestare per il modello di "acquisto" del SW, ovvero del modello a "licenze", siete fuori tempo di 30 anni, come minimo. Se il problema che alzate e' tecnologico, la misura e' giustificabile, e al massimo dovreste proporre la VOSTRA soluzione contro gli attacchi alla supply chain del sofware. Sono in attesa di leggerla.

@Profpatsch@mastodon.xyz @strypey@mastodon.nzoss.nz The definition of an RPC system is that the caller has control over the callee, just that they are talking over the network instead of the same process space Well, I can understand why RPCs are often perceived as being more “control-oriented”, because in practice you are explicitly invoking something like this_is_a_like_please_act_accordingly() inside the callee. But at the same time, when an ActivityPub message says that an object is a “Like”, what is really happening conceptually? The sender is still expressing an intended semantic effect, and the receiver is still expected to interpret that effect and react accordingly. Soo.... is not an RPC, sure, but the effect is as predicable as an RPC. So from my perspective, the distinction sometimes feels more about how semantics are described and negotiated, rather than about one model being purely declarative and the other purely imperative.

Uhm... io parlavo della nave mercantile che li lancia. Supponiamo pure che il drone arrivi, la posizione della nave e' nota. Anche se gli aerei fossero in standby 20m , quanto puo' scappare un mercantile, in 20 minuti?

@strypey@mastodon.nzoss.nz Why? From my POV this is akin to telling someone you're sorry they have ginger hair or green eyes. It's just a part of who I am. I am thinking to the price it implies in social life. I had to do several training to re-learn "body language", by example, since this channel is way important, up to reading the whole work of Vera Birkenbihl, and some of her students too. Plus, the need of precision makes me read as "ambiguous" almost everyone else.  So basically you can go from "Sheldon" to "Patrick Jane", but this is all cortex, no feelings. Sure, it gives me some superpower too. I can look at a signaling gateway, and say:  "oh, this is a OTA SMS to SIM,  the UDH starts with  02 70 00". But, this hardly improves social relations, unless there is some attack on mobile devices, based on OTA to SIM protocol. So you get love from colleagues and the managers. In short, I don't think is a neutral as having red hairs. Why people thinks this is funny or cool? Do they? well, just look at "Sheldon movies &co", or "The good doctor". Seems cool, right? Spoiler: IMHO is not.

@strypey@mastodon.nzoss.nz but is not ready. It starts an federate, works with tusky, but registration doesn't works, I have issues with pinafore, and more to fix....please specify, is not usable yet. The tumblr-like WebUI is kinda nice, but requires improvements, too. Is a WIP, and I am developing it alone. It will take time.

@Profpatsch@mastodon.xyz @strypey@mastodon.nzoss.nz I do not think the Mastodon APIs are really in scope for this discussion at all, unless the intention is to rely on ActivityPub C2S directly. What we are discussing here is federation itself, meaning the S2S side of the protocol and the interoperability guarantees between independently implemented servers. The client API layer is almost a separate concern entirely, e.g misskey has neither C2S neither Mastodon API,  because even very different client-facing APIs can still interoperate correctly if the federation contract underneath is sufficiently precise and unambiguous.

@Profpatsch@mastodon.xyz @strypey@mastodon.nzoss.nz The simple fact that a gRPC call eventually maps to local code does not really change the underlying contract. What matters is that the RPC definition describes clearly what is expected, what is returned, and what semantic guarantees exist between the two parties. What actually happens internally in the receiving implementation is ultimately the responsibility of the implementer on that side. One server may store data in PostgreSQL, another in memory, another may trigger asynchronous workflows internally — but from the protocol perspective, the contract remains stable and explicit. and that’s a good design, because AP is precisely not an RPC system, but a distributed system based on “common conventions” In the end, I think this is largely a matter of definitions. The real question, or at least the question I think should be discussed, is whether ActivityPub would be better expressed as an RPC-style protocol, since RPC seems to cover many of the same requirements more explicitly and with less room for divergent interpretation. From that point of view, the advantage would not be that RPC somehow dictates the internal behaviour of every implementation, but that it makes the external contract much clearer: these are the calls, these are the expected inputs and outputs, and these are the semantics both sides agree on. That would reduce the risk of interoperability depending on “this is my interpretation of the protocol”, which is exactly the kind of ambiguity that becomes painful once different projects start federating beyond the original use case.

@smallcircles@social.coop After years of listening to heavily manufactured pop bands — whether Korean, Japanese or otherwise — with autotune everywhere, and after decades of dancing to techno made almost entirely with synthesizers and machines, isn’t it at least a little curious to suddenly draw the line at AI-generated music?

@strypey@mastodon.nzoss.nz @wafrn Is it anything like @wafrn? I like their ATProto sidecar concept, but all the eye candy in the interface is a bit much for me. Aktor  started headless, to be honest. But yet I understood , like GtS also did, there is some need for admin interface and more. So, at the end, I decided to add some UI. So I had to ask myself what's the UI i liked more, and tumblr was the one. I don't think it's the same of wafrn, since I wasn't able to compile it in the past, so I started it from scratch.

@MostlyHarmless@thecanadian.social omeopatic ones. At least, you have water to drink.

@strypey@mastodon.nzoss.nz It's mostly already done; I know. Email SMTP "federates" since ages, SIP protocol "federates", XMPP "federates", and so on. But, their RFC is readable and unambiguous. I am now developing my own software for AP instances. ActivityPub has way too many flavours, to be really interoperable. The process of getting it interoperable with pleroma, mastodon, and then GtS. is driving me crazy. So, a standard which has NO real "standard" in it, is just an eternal work in progress. Who designed this "standard", despite having the W3C accepting it, did a terrible job IMHO. I should not hit in the "mastodon is doing it like that, pleroma does it differently from GtS" issue. yet, I do. ... and I reckon the law I'm proposing would finish the job; this "new law" is done, is already part of the Digital Markets Act (DMA), Regulation (UE) 2022/1925, Article 7, Comma 1 &  2. https://www.eu-digital-markets-act.com/Digital_Markets_Act_Article_7.html So you wish this was also for your country?  Sorry if I can't get your point, it not really clear to me if you advocate for more than the EU regulation, or not.

@royaards@newsie.social Cost of living (especially energy) is undeniably on the rise to to the war in the Middle East, I’m not sure I agree completely. Much of the oil and many derivatives currently on the market were actually purchased long ago, often through mechanisms such as futures contracts and long-term supply agreements. The same applies to the food supply chain: these systems move slowly. Agriculture follows seasonal cycles, and in many cases crops are harvested only once a year, so the effects tend to appear with a significant delay. Of course, one could argue that media and governments are using this narrative to justify certain market dynamics or lobbying interests, rather than describing a simple direct cause-and-effect relationship. The reality is that modern supply chains are extremely long and complex. Because of that, it seems difficult to attribute immediate price changes entirely to events that have only just occurred.

@alineblankertz@indieweb.social you could have read about the Gartner's Hype Curve instead. So you don't reinvent the wheel.

Una nave russa o no che lanciasse droni da quelle posizioni avrebbe zero possibilita' di sopravvivere alla reazione dell'aereonautica. Mi sembra n piano stupido.

of course. when he talks about the massive commercial deficit with the UE, he is saying the EU industry is winning , in the US market. US industry is s**t, mostly because of the lack of public infrastructures.

@royaards@newsie.social uhm... expenditure for defense is, in Europe, below 4% of GDP. Depicting as a dominant economical  force requires  imagination.

@wronglang@bayes.club @strypey@mastodon.nzoss.nz It happened to me many times in the past as well. To be completely transparent, in this case I am even using suggestions from an AI with prompts such as “please do not make me sound rude or offensive”. And honestly, it works surprisingly well for emails, long-form discussions, or social posts like these, where there is enough space to add nuance and clarify intent. I am less sure it would work equally well in a fast real-time chat. The problem is that when you try to express technical opinions very clearly and precisely, especially in architecture or protocol discussions, people can sometimes perceive that clarity itself as being harsh, confrontational, or dismissive, even when no hostility is intended at all. Unfortunately, for reasons, I am not able to renounce precision or directness.

@strypey@mastodon.nzoss.nz @evan@cosocial.ca well,  I am not finished yet with my software, so maybe I will discover some other ambiguity to get crazy with... ok, if you say I'm welcome to sound very pedantic, I can. Besides, my software is here: https://git.keinpfusch.net/loweel/aktor so far the federation seems to work, now I need to fix bugs, nd check against other software like misskey, by example.

Con cinque chili di esplosivo? Uhm. Qui bisogna uscire dal cartone animato e arrivare alla realta'. QUel tipo di drone va bene se tu in un solo attacco ne lanci decine, o centinaia. Come si fa effettivamente. Da quelle posizioni , tipo da un mercantile nel tirreno, FORSE arrivi a lanciarne uno o due, poi vieni affondato senza pieta', per via aerea. Poi c'e' il problema della deniability. Putin e la sua guerra ibrida lavorano molto in deniability. E' una cosa che pero' e' molto limitata: hacker russi attaccano un ospedale, Mosca nega di averci a che fare. Questa condizione pero' e' persa in mare. Se un sottomarino affonda uno dei mercantili russi, e' possibile per noi negare. Quindi affrontare una guerra ibrida nell'unica situazione dove ce l'ha anche il tuo avversario e' un'idea, detta come va detta, del cazzo.

@strypey@mastodon.nzoss.nz @evan@cosocial.ca @cwebber@social.coop I don't think this link will work.

@strypey@mastodon.nzoss.nz because here are no IT people who are competent enough to achieve this. It was done for the phone network, for the mobile network, so you can call someone regardless who their ISP is. But, when it comes to IT, the stupid, american idea of "standards de facto" will create a separate protocol per company.

@strypey@mastodon.nzoss.nz I get it. English is like AP; the flexibility and extensibility is both a feature and a bug ; ) maybe the next protocol for federation shold name like DezentralisierteSozialnetzwerkserverföderierungsübertragungsprotokoll, DSSFÜP for make it easy and clear. Diagnosed autistic here, can relate : ) sorry to read that. Why people thinks this is funny or cool?

Bene. Fai un danno da X, e perdi una nave che costa X * 20. Non sembra geniale.

@strypey@mastodon.nzoss.nz @evan@cosocial.ca @cwebber@social.coop @Mastodon@mastodon.social You are German? This absolutely must not be a barrier to participating in SocialCG/WG. Born Italian, moved in Germany. But I think is more about being a little , like most people in IT since 30 years, inside some kind of spectrum. I crave for clarity, i NEED clarity, and quite often, english does not sound as clear as I wish. Which is frustrating. Italian is logic, little context based. German is tremendously context based, but at least is taxonomic, meaning precise. English to me sounds like someone is trying to sell me things, rephrasing things instead to aim at the point. Plus, some people is not easier than me to communicate with, take by example "Lain", the creator of pleroma. Putting me and him/her in some elevator is a perfect definition of blasting compound, I guess. Even if you don't feel comfortable speaking in voice meetings, Well, in real life I'm masquerading pretty well, since I did all the "soft skill" trainings available in my company. So I participate to meetings, sure. And sound very professional.  The issue is, I don't like it at all. And people here in Germany calls me "Der Musolini", because of quite a stubborn personality. So masquerading it doesn't work 100%, so to say. I repeat. The germans. Germans. Call . Me . Stubborn. Got it? But let's go to the point: I don't think is necessary to participate , in order to make a criticism. I mean, what would be my contribution? Asking for precision every time, or repeating "a standard must be precise"? Isn't very, very little? Isn't OBVIOUS?

@simontatham you could have used thunderbird, and defined retention rates per folder. So that, "keep the last 50" would happen automagically, and this would have given you peace of mind....

E lo sono. Ho avuto bisogno, quando vivevo in Italia sull' Appennino (in una zona boschiva abbastanza isolata) di un veicolo che potesse fare cose. Non ho mai pensato ad una porcheria del genere, per la semplice ragione che con un culo cosi' leggero, con la neve, le strade di montagna non le fai, e il 4x4 non ti aiuta. Anzi. Ho scelto un semplice Rocky di daiatsu, e un carrello per portare la roba, attaccato dietro. Ma in citta', non esiste alcuna ragione di averlo. Era una cosa che mi serviva, e quella roba che vendono non serve.

@vitaut@mastodon.social check your calendar. We invented machines for this.

@denkbeteiligung@digitalcourage.social @EUCommission@ec.social-network.europa.eu perfection is the worst enemy of good

@centralscrutinizer@ors.novababilonia.me @evan@cosocial.ca @strypey@mastodon.nzoss.nz @Mastodon@mastodon.social @cwebber@social.coop LOL. Which part precisely? I think, 23 years of blogging should have made it clear... at least to my italian followers  😀 .

@royaards@newsie.social Not within such a short timespan. Of course, a year from now — when the crisis is likely over — prices may still remain high, and at that point the very same arguments I make will probably be used to justify why the cost of living continues to increase even after the emergency itself has ended. With the full support of some press and media. For example, crops being sold today were largely grown using last year’s fuel, last year’s fertilizers, and last year’s production costs. Because of that, it is difficult for me to see a purely ->immediate<- cause-and-effect relationship that would justify sudden price increases overnight.

@strypey@mastodon.nzoss.nz is the DMA, not the DSA. DSA says nothing about interoperability, so don't waste your time on DSA

@smallcircles@social.coop I’m not really sure what SX or CALM are, to be honest. But in general, I’m not particularly interested in crusades, moral panics, or witch hunts around technology. To me, AI is simply another tool — like many others before it. It can be used well, badly, creatively, commercially, intelligently, or stupidly, depending on the people using it. I tend to look at it more as a technology to understand and experiment with than as something to worship or fear.

@Zambunny@livellosegreto.it cambia alimentatore. non e' un'operazione difficile e un alimentatore non costa molto. Ovviamente, sapere se e' un portatile o meno poteva giovare.