Der ganze Vorgang ist archetypisch für die seit Jahrzehnten völlig ohne Not stattfindende politische Selbstverzwergung Europas.
A comment on heise about the recent AWS outage.
(Too bad thereās no good translation for the great word āSelbstverzwergungā.)
Iām paraphrasing: Europe (and other regions) depend on US IT services, a lot, without an actual need. We saw AWS, Google, and Microsoft build large datacenters and then we thought āwelp, shit, nothing we can do about that, guess weāll just be an AWS customer from now on.ā Nobody really went ahead and built German/European alternatives. And now we completely depend on the US for lots of our stuff.
The article even claims that thereās now a shortage of sysadmins in the EU? Iām not so sure. But Iād welcome it, makes my job more secure. š¤£
Hosting services, datacenters, software, everything, itās all US stuff. Why do we accept this, why not build alternatives ā¦
@aelaraji@aelaraji.com And I read the following funny response to that:
Bluesky: Users verify their age by adding a payment method or uploading a photo ID.
Mastodon: Users verify their age by posting pictures of the vintage computer equipment in their homes.
https://beige.party/@maxleibman/114848276288629121
š
@prologic@twtxt.net This person isnāt particularly happy with this study:
https://mastodon.social/@grimalkina/114717549619229029
I donāt know enough about these things to form an opinion. 𫤠I sure wish it was true, though. š
Saw this on Mastodon:
https://racingbunny.com/@mookie/114718466149264471
18 rules of Software Engineering
- You will regret complexity when on-call
- Stop falling in love with your own code
- Everything is a trade-off. Thereās no ābestā 3. Every line of code you write is a liability 4. Document your decisions and designs
- Everyone hates code they didnāt write
- Donāt use unnecessary dependencies
- Coding standards prevent arguments
- Write meaningful commit messages
- Donāt ever stop learning new things
- Code reviews spread knowledge
- Always build for maintainability
- Ask for help when youāre stuck
- Fix root causes, not symptoms
- Software is never completed
- Estimates are not promises
- Ship early, iterate often
- Keep. It. Simple.
Solid list, even though 14 is up for debate in my opinion: Software can be completed. You have a use case / problem, you solve that problem, done. Your software is completed now. There might still be bugs and they should be fixed ā but this doesnāt āaddā to the program. Donāt use āsoftware is never doneā as an excuse to keep adding and adding stuff to your code.
Unless your Terms of use update email looks and reads the same as the one I got yesterday from mastodon.social, I donāt wanna know about it, nor do I agree to it.
@movq@www.uninformativ.de why Gopher to babble, and not just HTTP? I mean, may as well just write plain text files on your machine, and leave them there, right?
Gopher and Mastodon are two completely different things. Thatās where my confusion comes from.
@bender@twtxt.net Both Gopher and Mastodon are a way for me to ābabbleā. š I basically shut down Gopher in favor of Mastodon/Fedi last year. But the Fediverse doesnāt really work for me. Itās too focused on people (I prefer topics) and I dislike the addictive nature of likes and boosts (Iām not disciplined enough to ignore them). Self-hosting some Fedi thing is also out of the question (the minimalistic daemons donāt really support following hashtags, which is a must-have for me).
Iāll probably keep reading Fedi stuff, I just wonāt post that much, I think.
@movq@www.uninformativ.de how does Gopher relates to Mastodon? Are you getting off the Fedi completely?
Gopher server is back online and Iāll be phasing out Mastodon.
gopher://uninformativ.de
(No, I wonāt do multi-protocol twtxt again. š )
And on a similar note, cross-post from Mastodon:
What I love about HTML and HTTP is that it can degrade rather gracefully on old browsers.
My website isnāt spectacular but I donāt think it looks horrible, either. And itās still usable just fine all the way down to WfW 3.11:
Itās not perfect, but itās usable. And that makes me happy. Almost 30 years of compatibilty.
The biggest sacrifice is probably that I donāt enforce TLS and that HTTP 1.0 has no Host: header, so no vhosts (or rather, everything must come from the default vhost). (Yes, some old browsers send Host:, even though they predate HTTP 1.1. Netscape does, but not IBM WebExplorer, for example.)
(On the other hand, it might completely suck on modern mobile devices. Dunno, I barely use those. š¤Ŗ)
Confession:
Iāve never found microblogging like twtxt or the Fediverse or any other āmodernā social media to be truly fulfilling/satisfying.
The reason is that it is focused so much on people. You follow this or that person, everybody spends time making a nice profile page, the posts are all very āego-centricā. Seriously, it feels like everybody is on an ego-trip all the time (this is much worse on the Fediverse, not so much here on twtxt).
I miss the days of topic-based forums/groups. A Linux forum here, a forum about programming there, another one about a certain game. Stuff like that. That was really great ā and it didnāt even suffer from the need to federate.
Sadly, most of these forums are dead now. Especially the nerds spend a lot of time on the Fediverse now and have abandoned forums almost completely.
On Mastodon, you can follow hashtags, which somewhat emulates a topic-based experience. But itās not that great and the protocol isnāt meant to be used that way (just read the snac2 docs on this issue). And the concept of ālikesā has eliminated lots of the actual user interaction. ā¹ļø
7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) š
And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! š± #Twtxt #Update
@movq@www.uninformativ.de I didnāt say I was leaving, just not that active here atm. I might be more active on mastodon at https://norrebro.space/@sorenpeter but Iām also rethinking that too tbh.
@prologic@twtxt.net Hmm, speaking of locally running āAIā stuff: Someone on Mastodon has this in their profile description:
My profile pic is AI modified to prevent deepfakes. I used local Stable Diffusion on my solar powered 7900XTX to average a few selfies.
That sounds like a fun thing to do. Do I have a chance of doing that on my old box from 2013 without a dedicated GPU? š
The Mastodon admins say that itās probably because of the size of my account (~600 MB), so the export process times out. And I understand that. Here on twtxt, I always use auto-expiring links when I post images or videos. It just gets too much data otherwise. I think Iāll just set my Mastodon account to auto-delete posts after ~180 days or something like that. Nobody cares about old posts anyway.
@kat@yarn.girlonthemoon.xyz Oh, yes, itās probably going to be something like gotosocial or snac. Itās got to be as lightweight as possible. (I call this whole thing āMastodonā, but youāre right, thatās not quite correct. š )
I think I should try self-hosting some Mastodon thingy again.
The āexport dataā feature on the Mastodon instance Iām using seems to be broken. Iāve contacted the admins but we couldnāt find the issue ā yet. I donāt want to bother them too much, itās a free service after all.
But this means that everything I post over there is very, very volatile. It could all be gone in 5 minutes and Iāll have no way to restore it. Hmm.
If we donāt keep insisting on simplify and āThe beauty of twtxt is, you put one file on your server, done. One.ā, then people should just use ActivityPub-based software like Mastodon, PixelFed, etc. which are getting a lot of attention and uses migrating to the fediverse from meta/x here in Denmark over the last couple of months.
@andros@twtxt.andros.dev Awesome! Iāve seen the demo earlier on mastodon, things are getting better and better with each update š Good luck!
Wow, it seem my #Webmentions implementation works from Mastodon via brid.gy
On my blog: Getting the Most from Mastodon (and Friends) https://john.colagioia.net/blog/2024/10/20/most-mastodon.html #mastodon #socialmedia
(#2024-09-24T12:45:54Z) @prologic@twtxt.net Iām not really buying this one about readability. Itās easy to recognize that this is a URL and a date, so you skim over it like you would we mentions and markdown links and images. If you are not suppose to read the raw file, then we might a well jam everything into JSON like mastodon
(#2024-09-24T12:39:32Z) @prologic@twtxt.net It might be simple for you to run echo -e "\t\t" | sha256sum | base64, but for people who are not comfortable in a terminal and got their dev env set up, then that is magic, compared to the simplicity of just copy/pasting what you see in a textfile into another textfile ā Basically what @movq@www.uninformativ.de also said. Iām also on team extreme minimalism, otherwise we could just use mastodon etc. Replacing line-breaks with a tab would also make it easier to handwrite your twtxt. You donāt have to hardwrite it, but at least you should have the option to. Just as i do with all my HTML and CSS.
@prologic@twtxt.net, there is a parser bug on parent. Specifically on this portion:
"*If twtxt/Yarn was to grow bigger, then this would become a concern again. *But even Mastodon allows editing*, so how
+much of a problem can it really be? š
*"
@movq@www.uninformativ.de going a little sideways on this, ā*If twtxt/Yarn was to grow bigger, then this would become a concern again. But even Mastodon allows editing, so how much of a problem can it really be? š *ā, wouldnāt it preparing for a potential (even if very, very, veeeeery remote) growth be a good thing? Mastodon signs all messages, keeps a history of edits, and it doesnāt break threads. It isnāt a problem there.š It is here.
I think keeping hashes is a must. If anything for that āfeels goodā feeling.
how little data is needed for generating the hashes? Instead of the full URL, can we makedo with just the domain (example.net) so we avoid the conflicts with gemini://, https:// and only http:// (like in my own twtxt.txt) or construct something like like a webfinger id nick@domain (also used by mastodon etc.) from the domain and nick if there, else use domain as nick as well
@quark@ferengi.one Check out this thread if you havenāt already: https://mastodon.social/@sundogplanets/112464533481477428
I think we already know Itās likely to be a disaster.
On my blog: Toots 𦣠from 08/12 to 08/16 https://john.colagioia.net/blog/2024/08/16/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 08/05 to 08/09 https://john.colagioia.net/blog/2024/08/09/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 07/29 to 08/02 https://john.colagioia.net/blog/2024/08/02/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 07/22 to 07/26 https://john.colagioia.net/blog/2024/07/26/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 07/15 to 07/19 https://john.colagioia.net/blog/2024/07/19/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 07/08 to 07/12 https://john.colagioia.net/blog/2024/07/12/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 07/01 to 07/05 https://john.colagioia.net/blog/2024/07/05/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 06/24 to 06/28 https://john.colagioia.net/blog/2024/06/28/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 06/17 to 06/21 https://john.colagioia.net/blog/2024/06/21/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 06/10 to 06/14 https://john.colagioia.net/blog/2024/06/14/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 06/03 to 06/07 https://john.colagioia.net/blog/2024/06/07/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 05/27 to 05/31 https://john.colagioia.net/blog/2024/05/31/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 05/20 to 05/24 https://john.colagioia.net/blog/2024/05/24/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 05/13 to 05/17 https://john.colagioia.net/blog/2024/05/17/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 05/06 to 05/10 https://john.colagioia.net/blog/2024/05/10/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 04/29 to 05/03 https://john.colagioia.net/blog/2024/05/03/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 04/22 to 04/26 https://john.colagioia.net/blog/2024/04/26/week.html #linkdump #mastodon #socialmedia #week
The wording can be more subtle like āThis feed have not seen much activity within the last yearā and maybe adding a UI like I did in timeline showing time ago for all feeds
I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.
The ānot receiving repliesā could partly be fixed by implementing a working webmentions for twtxt.txt
On my blog: Toots 𦣠from 04/15 to 04/19 https://john.colagioia.net/blog/2024/04/19/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 04/08 to 04/12 https://john.colagioia.net/blog/2024/04/12/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 04/01 to 04/05 https://john.colagioia.net/blog/2024/04/05/week.html #linkdump #mastodon #socialmedia #week
On my blog: Toots 𦣠from 03/25 to 03/29 https://john.colagioia.net/blog/2024/03/29/week.html #linkdump #mastodon #socialmedia #week
