Radxa Introduces the Palmshell SLiM X4L with Intel N100 Processor and 2.5GbE RJ45 Port
The Radxa X4L, also known as the Palmshell SLiM X4L, is a compact device powered by Intel’s quad-core N100 processor. With features like a 2.5GbE LAN port, Wi-Fi 6E, and dual 4K@30Hz display support, it’s well-suited for multimedia and general-purpose use. Unlike the Palmshell SLiM X2L released this year, the X4L integrates the Intel Alder

I like this comment on Slashdot in the above link:

LLMs don’t have an understanding of anything. They can only regurgitate derivations of what they’ve been trained on and can’t apply that to something new in the same ways that humans or even other animals can. The models are just so large that the illusion is impressive.

So true.

Radxa Enhances Compact RK3582-Based Networking Device with Dual 2.5GbE Ports
Radxa recently introduced a compact networking device powered by the hexacore Rockchip RK3582 System-on-Chip. This new model builds on the design of the previous Radxa E20C but features dual 2.5GbE RJ45 ports, enhancing its networking capabilities. The Radxa E52C is built on the Rockchip RK3582 SoC, which includes a 6-core CPU composed of a dual-core

Generative AI Doesn’t Have a Coherent Understanding of the World, MIT Researchers Find
Long-time Slashdot reader Geoffrey.landis writes: Despite its impressive output, a recent study from MIT suggests generative AI doesn’t have a coherent understanding of the world. While the best-performing large language models have surprising capabilities that make it seem like the models are implicitly learn … ⌘ Read more

@bender@twtxt.net Ull Twt to find the references later. But my memory is quite good 🤣

I’ve been testing our new APRS digipeater, that allows us to report our geographic position via radio.

@bender@twtxt.net Fair point, could be. I probably have to implement it first or create some kind of a mockup to spare me the effort of some feature that I rip out again. :-)

@xuu@txt.sour.is Yep!

@movq@www.uninformativ.de Riiiight, I now remember reading that a long time ago. :-)

@bender@twtxt.net I now read the German Wikipedia article on fog. These are some really beautiful pictures:

• https://upload.wikimedia.org/wikipedia/commons/a/a9/Nebelbank_in_der_W%C3%BCste_Namib_bei_Aus_%282018%29.jpg
  
• https://upload.wikimedia.org/wikipedia/commons/1/17/Space_Shuttle_Challenger_moving_through_fog.jpg
  
• https://upload.wikimedia.org/wikipedia/commons/9/96/Fog_Bow_%2819440790708%29.jpg
  
• https://upload.wikimedia.org/wikipedia/commons/a/ac/360_degrees_fogbow.jpg

To @anth@a.9srv.net’s points, I think this should be written as “Client recommendations” and “Serve recommendations”. Separate from the “Twtxt format” spec.

@bender@twtxt.net Agreed 👍

@lyse@lyse.isobeef.org agree on the HTTP stuff. I mean we could mention that for optimization see RFC yadda yadda should be followed for caching. but not have it part of the spec proper.

@bender@twtxt.net I’ve worked with this guy before. Paid him to do some freelance work. Not very good IMO. So haven’t hired him ever again. But he keeps saying hi every now and then on Signal. And then every few months or so asking stuff like this ☝️ – Last time it was money for private school fees for his child.

How am I suppose to know whether stuff like this (sound serious) is for realz or not? 😅

I need money for my mother’s heart surgery, there is a shortfall of about 2 million rupiah from a total of 40 million, can you help me with any amount?

Hmmm 🧐

😜

@bender@twtxt.net 😜

@bender@twtxt.net 😛

(Updated) Olimex Showcases Development Board Design Based on ESP32-P4 RISC-V SoC
Olimex Showcases Develoment Board Design Based on ESP32-P4 RISC-V SoC ⌘ Read more

New Raspberry Pi USB 3 Hub and Touch Display 2 Released with Enhanced Features
The Raspberry Pi community has launched two new accessories to enhance their single-board computers: the $12 USB 3 Hub, providing four-way USB 3.0 connectivity, and the $60 Touch Display 2, offering a higher-resolution, slimmer touch interface for interactive use. The USB 3 Hub provides high-speed data transfer up to 5 Gbps across four downstream USB

@bender@twtxt.net such as?

Quando o gov corta na ciência, não é porque não sabe o seu valor.
Quando o gov corta na educação, não é porque não sabe gerir a sociedade.
Quando o gov corta nos programas sociais, não é porque não reconhece o seu papel social.

É agenda: este gov de direita, tal como qualquer outro, tem como base programática o desmantelamento do estado social e da coisa pública. E nisso tem sido extremamente eficaz e competente.

Uma esquerda que denuncia a suposta incompetência ou burrice das pessoas no poder dá-lhes o crédito de estarem empenhados numa sociedade melhor pra todes, e que ao falhar nisso é uma questão de incompetência.

E quando essa denúncia é feita através de comentários sarcásticos e apontamentos de “hipocrisia”, servindo mais para afirmar superioridade intelectual do que realmente denunciar e avançar alternativas, é uma trágica forma de clicktivismo que continua extremamente em voga – e a direita agradece.

tl;dr: tratar as medidas opressivas/autoritárias/securitárias de qualquer direita como fruto de burrice ou incompetência não é só um erro, é alimentar e até legitimar o seu discurso

Making some amateur radio experiments!

@sorenpeter@darch.dk Section 7 on emojis: Exactly that, it’s an avatar for text interfaces. The metadata name needs tweaking, but that’s a cool idea. If I implemented this in my client, I’d make the text avatar overridable by the user, though. Otherwise I’d probably only see boxes for everbody in my terminal. :-D

@xuu@txt.sour.is LOL :-D

Thank you, @eapl.me@eapl.me! No need to apologize in the introduction, all good. :-)

Section 3: I’m a bit on the fence regarding documenting the HTTP caching headers. It’s a very general HTTP thing, so there is nothing special about them for twtxt. No need for the Twtxt Specification to actually redo it. But on the other hand, a short hint could certainly help client developers and feed authors. Maybe it’s thanks to my distro’s Ngninx maintainer, but I did not configure anything for the Last-Modified and ETag headers to be included in the response, the web server just already did it automatically.

The more that I think about it while typing this reply, the more I think your recommendation suggestion is actually really great. It will definitely beneficial for client developers. In almost all client implementation cases I’d say one has to actually do something specifically in the code to send the If-Modified-Since and/or If-None-Match request headers. There is no magic that will do it automatically, as one has to combine data from the last response with the new request.

But I also came across feeds that serve zero response headers that make caching possible at all. So, an explicit recommendation enables feed authors to check their server setups. Yeah, let’s absolutely do this! :-)

Regarding section 4 about feed discovery: Yeah, non-HTTP transport protocols are an issue as they do not have User-Agent headers. How exactly do you envision the discovery_url to work, though? I wouldn’t limit the transports to HTTP(S) in the Twtxt Specification, though. It’s up to the client to decide which protocols it wants to support.

Since I currently rely on buckket’s twtxt client to fetch the feeds, I can only follow http(s):// (and file://) feeds. But in tt2 I will certainly add some gopher:// and gemini:// at some point in time.

Some time ago, @movq@www.uninformativ.de found out that some Gopher/Gemini users prefer to just get an e-mail from people following them: https://twtxt.net/twt/dikni6q So, it might not even be something to be solved as there is no problem in the first place.

Section 5 on protocol support: You’re right, announcing the different transports in the url metadata would certainly help. :-)

Section 7 on emojis: Your idea of TUI/CLI avatars is really intriguing I have to say. Maybe I will pick this up in tt2 some day. :-)

Perfect, @eapl.me@eapl.me, it’s fixed again. In fact this editor seems to support the Unicode line separator character all too well, otherwise it would not have replaced it in the first place. :-D Time to switch to a more unintelligent editor. ;-)

Thanks, @bender@twtxt.net. I try to.

I haven’t noticed any smell of fog, @bender@twtxt.net. Might @nff@www.noizhardware.com’s experience stem from a similar phenomenon that creates a lovely smell after a good, air-cleaning rain shower?

@sorenpeter@darch.dk #NSFS #NotSafeForSorenpeter

@eapl.me@eapl.me Neat.

So for twt metadata the lextwt parser currently supports values in the form [key=value]

https://git.mills.io/yarnsocial/go-lextwt/src/branch/main/parser_test.go#L692-L698

@sorenpeter@darch.dk on 4 for gemini if your TLS client certificate contains your nick@host could that work for discovery?

the smell of fog is soo gud <3

the smell of fog is soo gud <3

I realise now that the referred post might just be fiction. I am slow Ferengi these days. LOL.

@wbknl@twtxt.net are you still in Russia? It could be hard mailing anything to there these days. I read your “russia is eternally cold”, and became curious. Patagonia is the only place I know on South America that it has rounded mountains, though they can be anywhere. Originally from Chile, or Argentina? My curiosity doesn’t need feeding, by the way. It’s all good if it doesn’t. :-)

This morning (and a little bit of the afternoon) the idea of having a full referenced archive of twtxts on the web has consumed me a bit. I am talking about something similar to the email archives one see online, but for twtxts, and a more personal level. Such archive would be available, even if the involved feeds are long gone, because feeds will be treated as received emails.

@eapl.me@eapl.me here are my replies (somewhat similar to Lyse’s and James’)

1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

4. Discovery: User-agent for discovery can become better. I’m working on a wrapper script in PHP, so you don’t need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that’s the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

6. Languages: If the need is big then make a separate feed. I don’t mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it’s about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

7. Emojis: I’m not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

(Updated) Banana Pi Showcases BPI-CanMV-K230D Zero with Canaan K230D Chip Design
(Updated) Banana Pi Showcases BPI-CanMV-K230D Zero with Canaan K230D Chip Design ⌘ Read more

SolidRun HummingBoard i.MX8M IIOT SBC with NVMe, RS232, RS485, and LTE Support
SolidRun has launched a single-board computer tailored for Industrial Internet of Things and Human-Machine Interface applications, built around the i.MX8M Plus System-on-Module from NXP. Its carrier board includes features like RS232, RS485, dual CAN-FD, and dual 1Gb Ethernet and more. According to the official announcement, the HummingBoard i.MX8M IIOT carrier board is compatible with the … ⌘ Read more

@eapl.me@eapl.me Regarding supporting languages:

That said, coming from platforms like X and Masto, where switching languages is easy, I naturally read content and write into my timeline in at least three languages. Changing my “account” is not a simple as switching languages, and in those platforms have another meaning (“I’m a different person”). Supporting that would be beneficial for some, though I’m not sure how many would use it.

I think this is more of a client concern in my opinion. Like @lyse@lyse.isobeef.org said earlier though, sometimes he and @movq@www.uninformativ.de “Twt” in German. I don’t (nor anyone else I’m aware of) have a problem with this. It seems to be that a “client” could detect this and deal with this appropriately or give a user appropriately controls.

For me (_personally__ I’ve never found it a problem. I use extensions like “Simple Translate” anyway, so it doesn’t matter a great deal to me.

@eapl.me@eapl.me Just responding to some of your specific ideations here:

Sure! From my research, Gemini (and likely Gopher as well) don’t have a similar header, so if a client is using those protocols, they won’t be able to inform your server.

So, it’s worth considering, would twtxt 2.0 only support HTTP/S?

I’m not sure how to standardize “Discovery” across different protocols for serving feeds, HTTP, Gopher, Gemini, etc. beyond what you initially suggested. But here’s the thing, the User-Agent HTTP Header isn’t the only aspect to “discovery”. Discovery in practise is more of an organic property of @-mentions across feeds in the first place, something that crawlers take advantage of.

@slashdot@feeds.twtxt.net Oh come one?! Web5?! Since when was this even thing?! 😱 🤦‍♂️ I could grample with Web 1.0, Web 2.0 and even Web 3.0 (to a container degre), but Web 4.0 and Web 5.0 ?! Come on?! 😱 Get the fuck out! (GTFO) 😠

Thanks @lyse@lyse.isobeef.org! I’m replying here https://text.eapl.mx/reply-to-lyse-about-twtxt

Jack Dorsey’s Block Scraps ‘Web5’ Project
Block will abandon development of its Web5 decentralized internet project and reduce investment in music streaming service Tidal to focus on bitcoin mining hardware and self-custody wallets, the payments company announced in its third-quarter letter to shareholders. The Jack Dorsey-led firm cited strong market demand for its bitcoin mining products and Bitkey wallet as key drivers behind the st … ⌘ Read more

Damn, it’s certainly broken. Thank you for letting me know! I’m editing my .txt file by hand, and it seems WinSCP editor doesn’t support that character and replaced them all =/

notiz.pulli ⌘ https://notiz.blog/p/Ctu

@prologic@twtxt.net thanks

@wbknl@twtxt.net That it pretty cool 😎

This is beautiful and made my day

Will Republicans Bring Back Windows 95 and VHS Tapes?

Americans, congrats on a landslide victory!

On my blog: Real Life in Star Trek, Time’s Arrow, part 1 https://john.colagioia.net/blog/2024/11/07/time-s-arrow-1.html #scifi #startrek #closereading

Forlinx FET MX95xx C System on Module for Industrial and IoT Applications
Forlinx Embedded has introduced the FET-MX95xx-C System on Module, built around the high-performance NXP i.MX95xx processor for industrial, automotive, and IoT applications. Key features include a 10GbE port, dual GbE ports, CAN interfaces, camera support, and multiple wireless protocols. Unlike the FET3562J-C SoM, this new Forlinx device is powered by the NXP i.MX95xx processor. It

I built another small shelf for the drill press. I upcycled the wooden sticks from New Year rockets that littered the neighborhood. I really love the rustic look of it: https://lyse.isobeef.org/tmp/tischbohrmaschinenregal/

Image

When I glued the shelf between the posts of the stand, I tightened the long clamp too hard, ripping the back panel and shelf board apart. So, I had to reglue them. :-)

Righto, @eapl.me@eapl.me, ta for the writeup. Here we go. :-)

Metadata on individual twts are too much for me. I do like the simplicity of the current spec. But I understand where you’re coming from.

Numbering twts in a feed is basically the attempt of generating message IDs. It’s an interesting idea, but I reckon it is not even needed. I’d simply use location based addressing (feed URL + ‘#’ + timestamp) instead of content addressing. If one really wanted to, one could hash the feed URL and timestamp, but the raw form would actually improve disoverability and would not even require a richer client. But the majority of twtxt users in the last poll wanted to stick with content addressing.

yarnd actually sends If-Modified-Since request headers. Not only can I observe heaps of 304 responses for yarnds in my access log, but in Cache.FetchFeeds(…) we can actually see If-Modified-Since being deployed when the feed has been retrieved with a Last-Modified response header before: https://git.mills.io/yarnsocial/yarn/src/commit/98eee5124ae425deb825fb5f8788a0773ec5bdd0/internal/cache.go#L1278

Turns out etags with If-None-Match are only supported when yarnd serves avatars (https://git.mills.io/yarnsocial/yarn/src/commit/98eee5124ae425deb825fb5f8788a0773ec5bdd0/internal/handlers.go#L158) and media uploads (https://git.mills.io/yarnsocial/yarn/src/commit/98eee5124ae425deb825fb5f8788a0773ec5bdd0/internal/media_handlers.go#L71). However, it ignores possible etags when fetching feeds.

I don’t understand how the discovery URLs should work to replace the User-Agent header in HTTP(S) requests. Do you mind to elaborate?

Different protocols are basically just a client thing.

I reckon it’s best to just avoid mixing several languages in one feed in the first place. Personally, I find it okay to occasionally write messages in other languages, but if that happens on a more regularly basis, I’d definitely create a different feed for other languages.

Isn’t the emoji thing “just” a client feature? So, feed do not even have to state any emojis. As a user I’d configure my client to use a certain symbol for feed ABC. Currently, I can do a similar thing in tt where I assign colors to feeds. On the other hand, what if a user wants to control what symbol should be displayed, similar to the feed’s nick? Hmm. But still, my terminal font doesn’t even render most of emojis. So, Unicode boxes everywhere. This makes me think it should actually be a only client feature.

@bender@twtxt.net cos I live outside the United States and they don’t send to my country

@bender@twtxt.net I have my radio shack a mess

@prologic@twtxt.net Yeah, the principle of data economy. :-)

Btw. if you blindly run the command again in a few days, your query might match new feeds that are not included in today’s list. Hence, some accounts might be dropped without a warning. But then, they probably don’t care.

Hehe, thank you guys, I’m still alive :)

Hey @eapl.me@eapl.me, your feed is broken. All U+2028 got transformed into newlines.

Fsck democrats! Don’t mourn, organize!

I wish I had someone who could send me the Hacker Decals and Patch from Hackerboxes. Mail forwarding systems are so expensive!

I have lots of things to do at home. All I need is more energy.

Na #musiquinta do #protesto, confesso que fui fã dos Homens da Luta, pré-festival da canção, e tenho pena de terem desaparecido do mapa… Os melhores animadores de manifestações. E o povo, pá?

https://youtu.be/pZonZntFU7Y

@bender@twtxt.net i am a huge fan of CW. My training sessions gave me 50wpm proficiency. But one needs to keep practicing.

@bender@twtxt.net yes. Today, FT8 is widely used, but I prefer Robust Packet and telegraphy.

T Display S3 AMOLED Plus with Enhanced 1.91″ Display and Real Time Clock
The T-Display S3 AMOLED Plus is an upgraded development board based on the ESP32-S3 microcontroller with a dual-core LX7 processor. It features a 1.91″ AMOLED display with a 240×536 resolution, using RM67162 IPS AMOLED technology for sharp colors and full viewing angles with QSPI interface support. Similar to the LILYGO T4 S3 launched last year,

@wbknl@twtxt.net It’s probably okay for things like Twtxt which are designed to be in the open anyway 👌

@prologic@twtxt.net right. Encryption is not allowed by legislation.

@wbknl@twtxt.net The only thing I know about the HAM Radio space is that it’s considered “taboo” to encrypt the traffic. So that makes secure IP a bit difficult to say the least right? 🤔

@bender@twtxt.net yes, I am. @prologic@twtxt.net IP over hamradio works fine. We can request IPv4 or IPv6 addresses.

@wbknl@twtxt.net Ahh none that I’m aware of. I’ve thought about getting into HAM Radio myself, but haven’t so far…

@bender@twtxt.net I mean I’ve thought about it! It’s an intriguing idea to be able to have basic IP over HAM Radio 🤔

@prologic@twtxt.net i think i didn’t explain myself correctly. I was wondering how many twtxt.net users are hams.

@wbknl@twtxt.net How do you mean? How do you think that would even work? 🤔

I wonder how many hamradio operators use twtxt.net

FYI 👋 I will be deleting the following inactive users from my pod (twtxt.net) soon™:

$ ./tools/inactive_users.sh 730

@thgie@twtxt.net last seen 732 days ago
@will@twtxt.net last seen 740 days ago
@shaneflores@twtxt.net last seen 752 days ago
@magnus@twtxt.net last seen 757 days ago
@nickmellor@twtxt.net last seen 757 days ago
@birb@twtxt.net last seen 763 days ago
@screem@twtxt.net last seen 772 days ago
@servusdei@twtxt.net last seen 774 days ago
@alex@twtxt.net last seen 790 days ago
@andreottica@twtxt.net last seen 801 days ago
@fox@twtxt.net last seen 822 days ago
@anx@twtxt.net last seen 829 days ago
@olav@olav.bonn.cafe last seen 855 days ago
@caesar@twtxt.net last seen 866 days ago
@jim@twtxt.net last seen 869 days ago
@rell@twtxt.net last seen 882 days ago
@readfog@twtxt.net last seen 886 days ago

If anyone on this lists sees this post and wishes to preserve their feed/account for some reason (beyonds backups I maintain), please login at least once over the next coming weeks to get off this list. I will re-run this tool again, and then nuke blindly anything that matches >730 days of inactivity.

@xuu@txt.sour.is Haha 🤣 and 😢

@bender@twtxt.net Hah 😅