Show newer

When service X is down, everyone rushes to Twitter to write about it.

I spent years wondering where I would address my rants in case Twitter was down.

Today happened, the Fediverse remained healthy and up, and nobody here gave a sh*t about it.

To future historians—not just of computing, but of humanity—the current period will be a dark age.

How was Facebook used by students in the 2010s? We cannot show you, that version of Facebook is not hosted anywhere.

How did MySpace look around 2009? We don't really know, the Wayback Machine only shows a limited amount of static content, and there may only be a few surviving screenshots

What correspondence did Vint Cerf have as president of the ACM with other luminaries of computing industry and research? We do not know; Google will not publish his emails.

What was it like playing Angry Birds on an iPhone 3G? We do not know; Apple is no longer distributing signed receipts for that binary.

What did the British cabinet discuss when they first learned of the Coronavirus pandemic? We do not know; they chatted on a private WhatsApp group.

What books were published analysing the aftermath of the Maidan coup in Ukraine? We do not know; we do not have the keys for the Digital Editions DRM.

How was the coup covered in televised news? We do not know; the broadcasters used RealVideo and Windows Media Encoder and we cannot read those files.

We have to ask ourselves how we are going to preserve and transmit knowledge about our age to the next generations. Knowledge about an age where information is produced, consumed and discarded within hours, days or months, or where it's only stored on the server rooms of a handful of corporations, with no guarantees that those businesses will exist in the future, and with no way of accessing that information unless a certain set of regulatory, hardware, software pre-conditions are met.

That's why projects like the Internet Archive deserve more recognition and funding. That's why web scraping should not only be a civic right, but a civic duty to the next generations. Otherwise all the knowledge about the great age of information will be transmitted orally - with all the distortions that such transmission implies.

I probably shouldn't watch these videos after I've just spent 350 euros to change the pickups and fix the truss rod on my Ibanez.

Now the DIY side of me feels like tossing my guitar, take on the "Brian May" challenge and build my own from scratch.

The only problem I've got is space, I guess. A urban 80 m² apartment is big enough to host my own DIY space to tinker with electronics, but not to store all the machinery required to work with wood and metal.

...unless I 3D-print all the components, maybe...?

Historical moment:
First federated comment to a gitea instance from another instance:

We are 🤏 close to a fully federated ActivityPub based git platform. All we need is federated PRs and some level of control access to keep bots and trolls away from flooding the comments

I always forget how much more waiting is involved in a Windows or macOS update compared to Linux.

The migration of from to is almost complete.

CI/CD pipelines aren't operative yet, but everything else should be working. And we've also got a "sign in with " button that uses my instance - how cool is that?

Gitlab used to take about 5 GB of RAM and a lot of CPU to run just the basics. Gitea takes barely 100 MB of RAM and it's so light on the CPU that it could even run on a Raspberry Pi. Thanks to this migration alone I've managed to downgrade my 16 GB VPS to 8 GB and save about $60/month, while having basically the same features (except for integrated CI/CD) and a much faster response time. I should have probably done this earlier.

There's only one heads up: in the process of migrating the users I couldn't (obviously) decrypt the hashed passwords, so users are required to use the "forgotten password" link to reset it, or use one of the available SSO methods. I'll probably send a communication soon to all registered users.

I'm in the process of moving my repos from to (both self-hosted).

Gitlab sucks up about 3 GB of RAM on a server with low traffic, and after they decided to break git twice (first by pushing people to use their own git binary instead of the vanilla one, then with the "commit-graph requires overflow generation data but has none" doom bug that can randomly break your repos forever), I've decided that they are not a reliable partner for my code hosting needs anymore.

I'm in the process of looking for a Gitea alternative for CI/CD. Sure, I can get back to webhooks and scripts as a workaround, but I'd like something more natively integrated. Drone CI is an alternative apparently, but it doesn't seem that well natively integrated with Gitea either. Any thoughts?

"As a user of something open source you are not thereby entitled to anything at all".

Sure, and then these devs complain when nobody uses their projects and opt for some shitty closed-source alternative full of trackers instead.

I understand the argument behind this reasoning - people work on open-source stuff mostly in their free time, mostly unpaid, and therefore you can't have the same expectations that you'd have on a paid product.

But this attitude ("I'm doing you a favour to give you something for free, so just shut the fuck up, use it as it is and don't complain"), coupled with "just open a PR if you want feature X or bug Y to be fixed" (as if everyone was an experienced developer who knows how the project is structured) is exactly the reason why most of the people stay away from open-source software.

Be more humble, listen to people and have more sense of ownership for what you produce. Otherwise you'll just be a jerk that builds stuff that nobody wants to use.

"After we reminded GitHub of (a) the pending questions that we'd waited a year for them to answer and (b) of their refusal to join public discussion on the topic, they responded a week later, saying they would not join any public nor private discussion on this matter because “a broader conversation about the ethics of AI-assisted software seemed unlikely to alter your stance”".

To me, this is the biggest reason why must die in a huge ball of fire and leave no traces behind.

They make big profits with FLOSS software, included the code that I've developed and hosted on their platform over the past >10 years.

They don't share any of those profits back with me and other FLOSS developers.

They claim to be on the developers' side, but they offer no chances of appeal nor legal support to developers when a DMCA takedown requests comes in and developers lose months or years of work, often without explanation.

They claim to be the largest FLOSS platform on the planet, but their own source code is not open, and they already refused multiple times to open it up.

They trained their co-pilot with my code and tons of other FLOSS code, when they could have simply used their own codebase, or that of Office/Windows, if they're really in good faith and into the idea of giving back to the world.

And, when we ask them to sit and talk together because we have legitimate concerns (especially around the amount of open-source licenses that the co-pilot violates, since the underlying code isn't Github's intellectual property and licenses must be respected), they behave like jerks and say "well, our conversation won't change your mind anyway [about the fact that we're filthy jerks], so it doesn't even make sense to have it".

Change my mind ABOUT WHAT? It's my f*cking code, intellectual property and licenses that you're talking about, and I'm entitled to decide how you use it, or at least opt out of your programs if I don't like them, you filthy pieces of shit!

If I had ripped your own source code and gave it away for free, with no references nor credits about the original authors, and you asked me for explanations, would I be able to get away with "my explanations aren't going to change your mind anyway, so I don't even want to talk to you"? Or would you unleash your whole army of lawyers against me? So just because individual FLOSS developers can't rely on an army of lawyers like you do we're expected to be your unpaid slaves, you scum of the earth?

These disgusting parasites are still bent on their parent company's embrace-extend-exterminate strategy, nothing has changed since Ballmer's times. But keep in mind that, unlike with Windows, they are NOT the authors of the content on their platform. WE are the authors. If we all pull our code out of Github and move it to Gitlab, Gitee or other solutions, they'll be left with nothing. Let's make sure that this is indeed the case and Github joins the cemetery of evil projects with no added value.

I have been testing for the past few days three replacements for 's notifications: , and 's Unified Push project. A few observations after a bit of tinkering:

1. The idea behind is amazing. An open protocol to share push notifications over any asynchronous channel (websocket, Redis, MQTT etc.) is what open-source apps have needed for years. Sure, there will always be those who say "push notifications are a distraction, and I'm happy to ditch them". But individual choices/behaviors shouldn't shape the development of a technology - especially when people want a genuine open alternative to something that they like/need to use.

2. UnifiedPush support from individual apps is still scarce. So far I've only found the NextCloud app itself (which only supports UP-NextPush), and . Support on has allegedly been implemented in the latest release, but I haven't yet managed to make it work. Let's roll up our sleeves and make sure that more and more of the apps that we like support open notification services!

3. The notification providers' client apps themselves are still quite buggy, and documentation still very sparse. I have used UP-Example from F-Droid to test the UP services. Only ntfy managed to deliver notifications end-to-end to my devices. Gotify reported an "unknown error" without many details from the logs. UP-NextPush is still very unstable both on the client and server side and I couldn't manage to deliver any notifications.

4. The protocol (and the apps that implement it) needs to slowly be extended to cover as many as possible of the features that have been implemented in the past decade. Action buttons, icons from URLs, custom background images, updates to existing notifications etc.: a couple of these features have been (partly) implemented by 1-2 providers, but we need open standards (especially for action buttons and gestures) if we want to ensure inter-compatibility.

So mostly relies on comments in the code to figure out what a certain block of code is about.

So the best way to prevent copilot from using your code is to avoid comments.

Who would have known that the best advice to protect software licenses would have been the worst possible advice when it comes to code maintainability?

Vatican praises U.S. court abortion decision

Heaven forbid a woman’s right to choose should limit the supply of altar boys for Catholic bishops to bugger.

#catholicChurch #vatican #pope #catholicism #religion #fundamentalism #childAbuse #abortion #humanRights

People value being able to log in to a platform, connect with who they want to connect with, consume the media they enjoy, find the information that’s relevant and then be gently nudged off the platform in a way that fits their time management goals. Social media could have a healthy, meaningful place in people’s lives. But that’s just not the way it’s being designed right now.

Custom lists (prompting users to organize their contacts in lists, and then consume content from those lists instead of the algorithmically curated main timeline) have a huge value - something I already realized when started to move too far from a chronological timeline and started inserting trending tweets and other shit.

Spotting conflict and prompting users to resolve their discrepancies in private instead of the public timelines can also make social media much less toxic, since 1-1 interactions are more personal and less likely to be as abrasive as public conflicts where each of the parties feels the urge to "defend" their side in front of others.

We also need to clearly condemn the social media that are exploiting and abusing our psychological reward mechanisms (the "keep digging this endless bucket and you'll find what you're looking for") to create addiction cycles similar to those of created by substance abuse and gambling. Social media should prompt users to set the amount of daily time that they expect to spend on them, and then gently nudge them off if they spend too long, instead of rewarding them when they spend all of their time doom scrolling.

Most of the people feel a sense of disgust and revulsion when they realize that they've spent too much time on social media instead of doing something productive in real life. We don't want to use social media that make us feel bad by design and steal our time from family, friends and work. If those social media don't change their approach, then their usage needs to be discouraged just like we discourage tobacco usage.

is basically selling code that other people wrote, without providing them with any compensation nor credits, and disregarding any possible license incompatibilities.

And will probably get away with it because the whole thing is "AI-curated", so no human purposefully violated any intellectual property.

What leaves me speechless is that Github is making so much profit out of other people's open-source code, and they also claim that in a couple of years "there will be no more code sitting on local machines", but they are very, very wary from releasing THEIR own source code (like Gitlab and Gitea did) so people can run their own instances.

I'm still on Github because that's where all the devs and projects are. But all of my projects are now on a self-hosted Gitlab instance, mirrored to Github (and I'm even considering dropping that mirror). If you don't want Github to get rich from your code while giving you nothing in return, you should probably do the same.

A well-run business can’t afford to switch to a new approach—one that ultimately will replace its current business model—until it is too late

Here's a computer problem, 9/10 developers can't solve it.

you have two computers,

One you are able to upgrade any of the parts or even use an entire server room full of computers as good as money can buy

The other is a computer-like device picked randomly from anywhere on the planet statistically it's going to be a low end android phone

You have to display an image on the 2nd device

where do you choose to do the bulk of the work required to render the page?

Worst timing for to go down, after doing a factory reset of my old PixelC last night and trying to reinstall the apps.

I hope the folks at @fdroidorg
can fix it soon 🤞

It's interesting to see so many discussions around , sentient AI and so on.

It's just a shame that, beyond the two partisan camps ("it's human!"/"it's not human!"), there isn't much room to ask a simple question: if an AI had ever to become sentient, how would we know that?

We're way beyond the Turing test here. You can now entertain a long conversation with an AI without even realizing that you're not talking to a human.

So how do we know if the AI is actually coming up with independent thoughts or just mimicking and elaborating on pieces of the huge datasets it's been trained on?

How do we know if those thoughts were genuine or just words that statistically maximized a sophisticated cost function?

And how do we even define "independent" and "genuine" thoughts? Humans say and do a lot of things just to maximize social acceptance or personal gain: does it mean that our thoughts and actions are sometimes "less" human?

We are discussing a lot about human intelligence and sentient models, but we haven't even come up with a shared definition of what makes something "sentient" or "conscious". How can we even get to agree on something that we haven't even agreed on how to measure?

K-9 has been acquired by and will soon become mobile, and I have a mixed feeling about it.

I have recently migrated to K-9 as an Android mail client after the drama that recently happened with .

Being an independent developer of an open-source mail client for mobile isn't easy. The developer of FairEmail has recently been quite open about the levels of stress he has been going through - also because of Google's harassment always looking for ways to take down his app.

So the shielding of Mozilla can definitely help and ensure that an email app keeps getting developed and supported. Sure, it's also an implicit admission that they've screwed up so much their mobile app strategy that they had to pick an open-source app built by a random guy and ask him if that could become the new Thunderbird mobile.

But I can't help with the feeling that independent developers who build stuff that big tech mafia dislikes can only keep doing so if they are protected by another company or by a foundation.

Show older

A platform about automation, open-source, software development, data science, science and tech.