My very strong opinion on the use of Twtxt is if you intend to use it, you should be prepared to let people pull your feed or at least check it and regular rentals.

Otherwise get out and go use something that’s either a distributed (Mastodon, AT, etc) or centralized (Facebook, X, etc) network.

⤋ Read More
In-reply-to » After the behaviour of a clearly very angry feed author over the past few days, I'm very tempted to give up on Twtxt and allow it to go back to being dead. What really is the point of building and supporting a way to exchange little pieces of text with one another in a completely decentralised way, if you're just going to keep humping up against such hostility? I don't know why I do this anymore.

I just find a very frustrating when you have these very small number of people that lash out unnecessarily and get so angry over nothing.

⤋ Read More
In-reply-to » After the behaviour of a clearly very angry feed author over the past few days, I'm very tempted to give up on Twtxt and allow it to go back to being dead. What really is the point of building and supporting a way to exchange little pieces of text with one another in a completely decentralised way, if you're just going to keep humping up against such hostility? I don't know why I do this anymore.

@cuaxolotl@sunshinegardens.org I think we’ve done that here right? 🤔 we seem to have collectively formed a community of folks that are interested in interacting with one another in a completely decentralized way and minimal way.

⤋ Read More
In-reply-to » After the behaviour of a clearly very angry feed author over the past few days, I'm very tempted to give up on Twtxt and allow it to go back to being dead. What really is the point of building and supporting a way to exchange little pieces of text with one another in a completely decentralized way, if you're just going to keep bumping up against such hostility? I don't know why I do this anymore.

@bender@twtxt.net Agreed. I just find it an abhorrent that certain folks just don’t even bother to spend the few mins that it takes to reach out. Compares to hours of their time to cause havoc and mischief. Seriously wut da fuq?! 🤦‍♂️

⤋ Read More

After the behaviour of a clearly very angry feed author over the past few days, I’m very tempted to give up on Twtxt and allow it to go back to being dead. What really is the point of building and supporting a way to exchange little pieces of text with one another in a completely decentralized way, if you’re just going to keep bumping up against such hostility? I don’t know why I do this anymore.

⤋ Read More

PineNote Community Edition Is an Upcoming E-Ink Tablet with Community-Built OS
PINE64 is preparing to launch the PineNote Community Edition, an update to the original PineNote Developer Edition e-paper tablet introduced in 2022. This version retains the same hardware features as the Developer Edition but will include an OS contributed by the PINE64 community developers. According to the product page, the PineNote Community Edition is powered

⤋ Read More
In-reply-to » @movq, having an issue fetching a twtxt context. I am getting:

@movq@www.uninformativ.de I’m assuming jenny is doing some kind of validation and verifying if that Twt really does exist on the feed uri? 🤔 But the hash is all kinds of wrong now because @gallowsgryph for whatever reason decided it might be a good idea to have a 2nd # url that doesn’t actually point to the same Twtxt feed (bad idea).

⤋ Read More
In-reply-to » Simplified twtxt - I want to suggest some dogmas or commandments for twtxt, from where we can work our way back to how to implement different feature like replies/treads:

@movq@www.uninformativ.de How hard would it be to implement something like (#<2024-10-25T17:15:50Z https://www.uninformativ.de/twtxt.txt>)in jenny as a replacement for (#twthash) and have it not care about if is http(s) or a g-protocol?

⤋ Read More
In-reply-to » Simplified twtxt - I want to suggest some dogmas or commandments for twtxt, from where we can work our way back to how to implement different feature like replies/treads:

@Codebuzz@www.codebuzz.nl Speed is an issue for the client software, not the format itself, but yes I agree that it makes the most sense to append post to the end of the file. I’m referring to the definition that it’s the first url = in the file that is the one that has to be used for the twthash computation, which is a too arbitrary way of defining something that breaks treading time and time again. And this is the case for not using url+date+message = twthash.

⤋ Read More
In-reply-to » (#pqhbula) @anth that doesn't work because you need encode that URL, like so http://a.9srv.net/tw.txt#:~:text=2024%2D10%2D08-,2024%2D10%2D23T18%3A59%3A49%2D07%3A00

The text parameters are percent-decoded before matching. Dash (-), ampersand (&), and comma (,) characters in text parameters are percent-encoded to avoid being interpreted as part of the text directive syntax.

⤋ Read More
In-reply-to » Ya know; Rather than being an asshole and getting all angry, just be reasonable and reach out to the community or folks fetching (or trying) your feed.

Seems he want “get permanarely unfollowed and ignored”. Btw did you unfollow him? I see follow in your feed

⤋ Read More

Raspberry Pi Expands AI Line with AI HAT+ Offering up to 26 TOPS
The Raspberry Pi AI HAT+ is the latest addition to the Raspberry Pi AI product line, offering up to 26 TOPS of compute power for AI applications. Building on the features of the Raspberry Pi AI Kit and AI Camera, the AI HAT+ enhances AI processing capabilities with two available models: a 13 TOPS version

⤋ Read More

UP Squared Pro 710H Featuring Alder Lake-N and Hailo-8 Processors with Linux Support
The UP Squared Pro 710H developer board is designed for AI and edge computing, featuring Intel Atom x7000RE, Intel Processor N Series, and Intel Core i3-N305 processors for flexible performance. It efficiently handles real-time, intensive tasks, addressing the demands of applications such as industrial IoT, smart cities, and autonomous systems. This AAEON developer board can … ⌘ Read more

⤋ Read More

Ya know; Rather than being an asshole and getting all angry, just be reasonable and reach out to the community or folks fetching (or trying) your feed.

Most clients respect caching if your feed is transported I’ve HTTP.

Otherwise you can add the # refresh hint to clients on your feed.

No need to be an obnoxious ass and flood your own feed. That will just get you permanarely unfollowed and ignored.

⤋ Read More

Simplified twtxt - I want to suggest some dogmas or commandments for twtxt, from where we can work our way back to how to implement different feature like replies/treads:

  1. It’s a text file, so you must be able to write it by hand (ie. no app logic) and read by eye. If you edit a post you change the content not the timestamp. Otherwise it will be considered a new post.

  2. The order of lines in a twtxt.txt must not hold any significant. The file is a container and each line an atomic piece of information. You should be able to run sort on a twtxt.txt and it should still work.

  3. Transport protocol should not matter, as long as the file served is the same. Http and https are preferred, so it is suggested that feed served via Gopher or Gemini also provide http(s).

  4. Do we need more commandments?

⤋ Read More
In-reply-to » Huh. I had long forgotten about text fragment URLs. Seems relevant for linking to discussions around linking to individual twtxt posts. https://alfy.blog/2024/10/19/linking-directly-to-web-page-content.html

According to this it was only published as a specification/standard last year. It’s no wonder 💭

⤋ Read More
In-reply-to » Huh. I had long forgotten about text fragment URLs. Seems relevant for linking to discussions around linking to individual twtxt posts. https://alfy.blog/2024/10/19/linking-directly-to-web-page-content.html

@anth@a.9srv.net I admit I didn’t know about text fragments. How new is this? 🤔

⤋ Read More

Ventana to Launch Veyron V2 RISC-V Platform for HPC in 2025
Ventana Micro Systems Inc., a leader in high-performance RISC-V platforms, has announced that its Veyron V2 accelerated compute platform will begin shipping in 2025. The Veyron V2 platform is designed to target AI, data centers, and emerging workloads. The Veyron V2 builds on Ventana’s expertise in RISC-V technology, offering flexibility to integrate third-party IPs and

⤋ Read More

HiFive Premier P550 Runs Linux on ESWIN EIC7700X RISC-V Platform
SiFive recently introduced the HiFive Premier P550, a high-performance RISC-V development board for demanding applications. Designed in a compact Mini-DTX form factor, it supports Linux development and is optimized for RISC-V operating systems across various industries. This embedded platform is powered by the ESWIN EIC7700X SoC, featuring a Quad-Core SiFive P550 64-bit CPU with a

⤋ Read More
In-reply-to » Encrypted Chat App 'Session' Leaves Australia After Visit From Police Session, a small but increasingly popular encrypted messaging app, is moving its operations outside of Australia after the country's federal law enforcement agency visited an employee's residence and asked them questions about the app and a particular user. 404 Media reports: Now Session will be maintained by an entity in Switzerland. The mo ... ⌘ Read more

@slashdot@feeds.twtxt.net wut da fuq?! What happened? What da hell was the Australian federal police even doing or asking? da fuq? I didn’t even know Session was based in Australia?! 🇦🇺 Oh my 😱 – I think this is worth enough to raise this with my local Federal MP (Elizabeth Watson Brown). This is nuts. The Australia FP can get bent 🤦‍♂️ I’d like to learn more about wtf happened here, seriously this is unacceptable and an overreach at first glance.

⤋ Read More

Encrypted Chat App ‘Session’ Leaves Australia After Visit From Police
Session, a small but increasingly popular encrypted messaging app, is moving its operations outside of Australia after the country’s federal law enforcement agency visited an employee’s residence and asked them questions about the app and a particular user. 404 Media reports: Now Session will be maintained by an entity in Switzerland. The mo … ⌘ Read more

⤋ Read More
In-reply-to » So, uh, did anyone but me notice that the last character of a twt hash is always either an a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.

@asquare@asquare.srht.site No need to apologise 😅 All very good points 👌

⤋ Read More
In-reply-to » (#bh5hvtq) @prologic With respect, a client can not identify whether an edit took place. Not unless that same client witnessed both the original twt and the edited one. This won't be the case if a person you're following is joining a thread started by people you aren't following after the first twt of that thread has already been modified. Or if you're knocked offline by a multi-hour power outage that spans then entire time window between a twt getting uploaded and modified.

@asquare@asquare.srht.site This is absolutely true! 💯 However the natural behavior of editing a post is the same as forking. So from a community perspective, we’re actaully okay with how that works in reality. I think we’re all getting a bit too hung up on “exactness”. One of the things I think we’re finding hard to reconcile is the fine line between a decentralised ecosystem and distributed system.

I want it very much to remain decentralised. That means Content-based addressing makes sense, because you can have integrity about what a Twt Hash means. I don’t really mind if a thread gets forked because the OP was edited, that’s actually how forking works anyway 😅

⤋ Read More
In-reply-to » So, uh, did anyone but me notice that the last character of a twt hash is always either an a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.

@prologic@twtxt.net With respect, a client can not identify whether an edit took place. Not unless that same client witnessed both the original twt and the edited one. This won’t be the case if a person you’re following is joining a thread started by people you aren’t following after the first twt of that thread has already been modified. Or if you’re knocked offline by a multi-hour power outage that spans then entire time window between a twt getting uploaded and modified.

⤋ Read More
In-reply-to » So, uh, did anyone but me notice that the last character of a twt hash is always either an a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.

@prologic@twtxt.net With respect, a client can not identify whether an edit took place. Not unless that same client witnessed both the original twt and the edited one. This won’t be the case if a person you’re following is joining a thread started by people you aren’t following after the first twt of that thread has already been modified. Or if you’re knocked offline by a multi-hour power outage that spans then entire time window between a twt getting uploaded and modified.

⤋ Read More
In-reply-to » So, uh, did anyone but me notice that the last character of a twt hash is always either an a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.

In any case, yes Content addressing can break threads when the original content is edited that’s for sure, however we’ve since agreed and realized that technically speaking, we can actually identify from a clients perspective, whether an edit took place.

⤋ Read More