Searching txt.sour.is

Twts matching #HTML
Sort by: Newest, Oldest, Most Relevant
thecanine
twtxt.net
 (2d ago)

I noticed Google put out this article: https://android-developers.googleblog.com/2025/09/lets-talk-security-answering-your-top.html it’s very current day Google, but the comments under the YouTube video are pretty on point and I saw a few familiar faces there. There is also, unexpectedly, ways to contact Google.

First a form for “teachers, students, and hobbyists”, that I filled politely, as someone who falls under their hobbyist category. It can be filled both anonymously, or with an e-mail attached, to be contacted by them (I chose the second option).

Also a general feedback and questions form, that I was not as polite in and used to send them the following message:

I have already provided some feedback, in the teacher, student and hobbyists form/questionaire, as well as an open letter I’ve recently sent to the European Commission digital markets act team, as I do believe your proposal might not even be legal, given the fact it puts privacy-focused alternative app stores at risk (https://f-droid.org/cs/2025/09/29/google-developer-registration-decree.html) and it was proposed this early, after Google lost in court to Epic Games, over similar monopoly concerns. Why should we trust Google to be the only authority for all developer signatures, right after the European courts labeled it a gatekeeper?

Assuming this gets passed, despite justified developer backlash and at best questionable legality, can you give us any guarantees, this will not be used to target legal malware-free mods, or user privacy enhancing patchers, like the ones used for applying the ReVanced patches? I have made a few mods myself, but I am in no way associated with the ReVanced team. I just share many peoples concerns, Google Chrome has been conveniently stripped of its manifest v2 support, that made many privacy protecting extensions possible and now you’re conveniently asking for the government IDs, of all the developers, who maintain these kinds of privacy protections (be it patches, or alternative open-source apps) on Android.

⤋ Read More
lwn-net
feeds.twtxt.net
 (3d ago)

[$] Last-minute /boot boost for Fedora 43
Sudden increases in the size of Fedora’s initramfs
files have prompted the project to fast-track a proposal to increase
the default size of the /boot partition for new installs of
Fedora 43 and later. The project has also walked back a few
changes that have contributed to larger initramfs files, but the
ever-increasing size of firmware means that the need for more room is
unavoidable. The Fedora En … ⌘ Read more

⤋ Read More
lwn-net
feeds.twtxt.net
 (3d ago)

Ubuntu 25.10 released
Ubuntu\
25.10, “Questing Quokka”, has been released. This release includes
Linux 6.17, GNOME 49, GCC 15, Python 3.13.7,
Rust 1.85, and more. This release also features Rust-based
implementations of sudo and coreutils; LWN covered the switch to the
Rust-based tools in March. The 25.10 version of Ubuntu flavors
Edubuntu, Kubuntu, Lubuntu, Ubuntu Budgie, Ubuntu Cinnamon, Ubuntu
Kylin, Ubuntu MATE, Ubun … ⌘ Read more

⤋ Read More
macrumors
feeds.twtxt.net
 (4d ago)

New TAG Heuer Smartwatches Now ‘Made for iPhone’
TAG Heuer today announced the Connected Calibre E5 smartwatch, now featuring “Made for iPhone” certification as the watchmaker abandons Google’s Wear OS.

Image

Three years after launching the Calibre E4, the Connected Calibre … ⌘ Read more

⤋ Read More
thecanine
twtxt.net
 (5d ago)

My open letter, to the European Commission digital markets act team:

Hello,

I am joining other developers, concerned about Googles new plan, to approve every app and effectively destroy most of the competing 3rd party stores this way. The biggest one of these alternative stores, most known for their focus on user and developer privacy, already states, this would make it impossible for them to operate: https://f-droid.org/cs/2025/09/29/google-developer-registration-decree.html
Even communities like the XDA forum, where new developers are often introduced to the world of Android development, would likely be strongly impacted, as making, publishing and installing Android apps is made less accessible.

I am not just writing on their behalf, I run a small website myself (https://thecanine.ueuo.com/), that both provides legal modifications, for some android apps - for example adding an amoled dark theme, to the most popular XMPP chat client for Android, or increasing one of Androids keyboard apps height. This all comes after Googles previous changes to the Android operating system, that prevent users from installing old apps (old to Google, can mean only a couple of months, without an update - https://developer.android.com/google/play/requirements/target-sdk and the target version gets increased every year). I rely on apps developed by a single developer, even for things like making the pixel art presented on my website and sideloading as a way to make these apps work, before developers can catch up to Google’s new requirements - if Google is allowed to slowly kill these options, us digital artists will soon lose the tools we need to create digital art.

⤋ Read More
golem-de
feeds.twtxt.net
 (6d ago)

(g+) Souveräne Maildienste fßr Privatnutzer: Briefgeheimnis gesichert
Fßr viele Privatnutzer lohnt sich ein eigener Mailserver nicht und Üffentliche Maildienste unterscheiden sich teils erheblich - eine Orientierungshilfe. Ein Ratgebertext von Erik Bärwaldt ( E-Mail, Spam)

Image

⌘ Read more

⤋ Read More
golem-de
feeds.twtxt.net
 (6d ago)

KI im Klassenzimmer: Wie Schüler und Lehrer mit dem “neuen Normalzustand” umgehen
Tools wie ChatGPT sind längst in den Schulen angekommen. Wie sich der Unterricht dadurch verändert - und wie sich Risiken vermindern lassen. Ein Bericht von Oliver Jessner ( KI, Wissenschaft)

Image

⌘ Read more

⤋ Read More
golem-de
feeds.twtxt.net
 (1w ago)

(g+) Arbeit: Wann ist der richtige Zeitpunkt zur ProjektĂźbergabe?
Bei Herzensprojekten fällt der Abschied oft schwer. Trotzdem ist eine Übergabe zum richtigen Zeitpunkt wichtig - für Entwickler und für das Projekt. Ein Ratgebertext von Jakob Rufus Klimkait ( Arbeit, CRM)

Image

⌘ Read more

⤋ Read More
golem-de
feeds.twtxt.net
 (1w ago)

Präventive Fahndung mit PrismX: Der Radikalisierung per KI zuvorkommen
Das KI-Tool PrismX eines indischen Studenten analysiert Postings in sozialen Medien und erstellt eine Risikoeinschätzung fßr die Radikalisierung einer Person. Ein Bericht von Lars Lubienetzki ( Tools, KI)

Image

⌘ Read more

⤋ Read More
golem-de
feeds.twtxt.net
 (1w ago)

(g+) Der vernetzte Arbeitsplatz: Wie MCP die Arbeit mit KI-Agenten verändert
MCP ist ein bemerkenswertes Protokoll, das die Schnittstelle zwischen verschiedenen KI-Modellen standardisiert: Wir erklären, wie man es sinnvoll nutzen kann. Ein Praxistest von Markus Kammermeier ( KI, API)

Image

⌘ Read more

⤋ Read More
alexonit
twtxt.alessandrocutolo.it
 (1w ago)

Hello again everyone! A little update on my twtxt client.

I think it’s finally shaping a bit better now, but… ☝️

As I’m trying to put all the parts together, I decided to build multiple parallel UIs, to ensure I don’t accidentally create a structure that is more rigid than planned.

I already decided on a UI that I would want to use for myself, it would be inspired by moshidon, misskey and some other “social feeds” mock-ups I found on dribbble.

I also plan on building a raw HTML version (for anyone wanting to do a full DIY client).

I would love to get any suggestions of what you would like to see (and possibly use) as a client, by sharing a link, app/website name or even a sketch made by you on paper.

I think I’ll pick a third and maybe a fourth design to build together with the two already mentioned.

For reference, the screens I think of providing are (some might be optional or conditionally/manually hidable):

  • Global / personal timeline screen
  • Profile screen (with timeline)
  • Thread screen
  • Notifications screen or popup (both valid)
  • DM list & chat screens (still planning, might come later)
  • Settings screen (it’ll probably be a hard coded form, but better mention it)
  • Publish / edit post screen or popup (still analysing some use cases, as some “engines” might not have direct publishing support)

I also plan on adding two optional metadata fields:

  • display_name: To show a human readable alternative for a nick, it fallback to nick if not defined
  • banner: Using the same format as avatar but the image expected is wider, inspired by other socials around

I also plan on supporting any metadata provided, including a dynamically parsable regex rule format for those extra fields, this should allow anyone to build new clients that don’t limit themselves to just the social aspect of twtxt, hoping to see unique ways of using twtxt! 🤞

⤋ Read More
lwn-net
feeds.twtxt.net
 (1w ago)

Alpine Linux plans /usr merge
The Alpine Linux project has announced
plans to change its base filesystem hierarchy:

In the future, /lib, /bin, and /sbin
will be symbolic links to their /usr counterparts, and every package
shall be installed under the /usr paths. For now,
/usr/bin and /usr/sbin will continue to be independent paths,
but that might change if the Filesystem Hierarchy Standard (FHS) gets
updated.

The merge will take place in the upcomi … ⌘ Read more

⤋ Read More
alexonit
twtxt.alessandrocutolo.it
 (2w ago)

Hi everyone, here’s a little introduction of my twtxt client (still WIP).

The client I’m developing is a single tenant project that runs entirely in the browser (it might use an optional backend).

It’s entirely based on native web-components and vanilla JS, it is designed to act closer to a toolkit than a full-fledged client, allowing users to “DIY” their own interface with pure html or plain javascript functions.

Users can also build their own engines by including a global javascript object that implement the defined internal API (TBD).

I’m planning to build a system that is easy enough to build and use with any skill level, using only pure html (with a homebrew minimal template engine) or via plain JS (I’ll be also providing some pre-made templates too).

Everything can be self-hosted on any static hosting provider, this allows to spread twtxt within communities like Neocities and similarly hosted websites (basically any Indieweb/Smallweb/Digital garden website and any of the common GitHub/Lab/Berg/lify Pages).

It will be probably named something like TxtCraft or craf.txt but I’m not really sure yet… 🤔 (Maybe some suggestions could help)

I’m still in the experimental phase, so there’s no decent source-code to share yet, but it will soon enough!

⤋ Read More
prologic
twtxt.net
 (2w ago)
↳ In-reply-to » @bender Really? 🤔

And I need to make something absolutely clear as well here. Twtxt was completely and utterly dead back in {Aug 2020](https://yarn.social/about.html) when I came across the spec and its simplicity and realised the lost opportunity. Since then we’ve continued to grow a small but thriving community. The extensions we’ve built over time have stood and lasted the test of time for the past ~5 years. We need not break things too badly, because what we have today and was designed years ago actually works quite well™ (despite some flaws).

⤋ Read More
prologic
twtxt.net
 (2w ago)
↳ In-reply-to » @bender Really? 🤔

@zvava@twtxt.net Going to have to hard disagree here I’m sorry. a) no-one reads the raw/plain twtxt.txt files, the only time you do is to debug something, or have a stick beak at the comments which most clients will strip out and ignore and b) I’m sorry you’ve completely lost me! I’m old enough to pre-date before Linux became popular, so I’m not sure what UNIX principles you think are being broken or violated by having a Twt Subject (Subject) whose contents is a cryptographic content-addressable hash of the “thing”™ you’re replying to and forming a chain of other replies (a thread).

I’m sorry, but the simplest thing to do is to make the smallest number of changes to the Spec as possible and all agree on a “Magic Date” for which our clients use the modified function(s).

⤋ Read More
prologic
twtxt.net
 (2w ago)
↳ In-reply-to » I just created a zs blogging template which I'm going to use for https://prologic.blog and I might starting writing long-form again soon™ 🔜 So far the "blogging" template/engine (if you weill) is quite simple. It comprises essentially of an index.md a prehook and a few utilities:

@bender@twtxt.net Yes I did about a week or so ago. It took me a lot of effort to get the content even rendered in the first place. LOL I had to basically export my blog as HTML (can you believe that?!) – The Hugo export just didn’t work at all 🤣

⤋ Read More
prologic
twtxt.net
 (2w ago)

I just created a zs blogging template which I’m going to use for https://prologic.blog and I might starting writing long-form again soon™ 🔜 So far the “blogging” template/engine (if you weill) is quite simple. It comprises essentially of an index.md a prehook and a few utilities:

$ git ls-files
.gitignore
.zs/config.yml
.zs/editthispage
.zs/include
.zs/layout.html
.zs/list
.zs/months
.zs/now
.zs/onthispage
.zs/posthook
.zs/postsbymonth
.zs/prehook
.zs/scripts
.zs/styles
.zs/tagcloud
.zs/taglist
.zs/years
archives/.empty
assets/css/site.css
assets/js/main.js
index.md
posts/hello-zs-blog.md
posts/on-tagging.md
posts/second-post.md
tags/.empty

⤋ Read More
prologic
twtxt.net
 (2w ago)
↳ In-reply-to » Here is just a small list of things™ that I'm aware will break, some quite badly, others in minor ways:

I would personally rather see something like this:

2025-09-25T22:41:19+10:00	Hello World
2025-09-25T22:41:19+10:00	(#kexv5vq https://example.com/twtxt.html#:~:text=2025-09-25T22:41:19%2B10:00) Hey!

Preserving both content-based addressing as well as location-based addressing and text fragment linking.

⤋ Read More
lyse
lyse.isobeef.org
 (3w ago)
↳ In-reply-to » is there consensus on what characters should(n't) be allowed in nicks? i remember reading somewhere whitespace should not be allowed, but i don't see it in the spec on twtxt.dev — in fact, are there any other resources on twtxt extensions outside of twtxt.dev?

@zvava@twtxt.net @movq@www.uninformativ.de I’m not entirely sure about the spaces, but maybe they were omitted to simplify parsing of mentions in the form of @<nick url>. If the next token after the @<nick does not look like a URL, it’s not a mention but regular text. This is just wild guessing, though.

Looking at the regex and tests in the original twtxt reference implementation seems to confirm that theory in the sense as it relies on whitespace as the delimiter:

https://lyse.isobeef.org/tmp/screenshot-2025-09-17-21-30-25.png

Another thing about nicks is that the original twtxt reference implementation converts nicks to all lowercase:

https://lyse.isobeef.org/tmp/screenshot-2025-09-17-21-20-39.png

You probably know this already, the original twtxt file format specification can be found here: https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html

As for extensions, I don’t know of anything outside of twtxt.dev that has actually been (partially) implemented. However, there is also the issue tracker of the official reference implementation. You might wanna dig through that. For example, there is an alternative suggestions of multiline messages: https://github.com/buckket/twtxt/issues/157

⤋ Read More