#X25

BLACKVOID ⚫️blackvoid
2026-02-01

A little update on the (and Jelly) transcoding for the models, DS425+ and DS225+.

A new version of the i915.ko version has been published (the one) that now supports tone mapping correctly.

Article has been updated and it is referring to this as a "v2" solution. v1 solution is still posted as a fail safe until some github scripts have been updated to the new solution.

blackvoid.club/unlocking-plex-

2025-11-19

/* This is ALPHA test software. This code may break your machine, randomly fail to work with new releases, misbehave and/or generally screw up. It might even work. */

github.com/torvalds/linux/blob

#linux #kernel #x25

2022-04-16

Conectando a BANnet X.25 con módem de 9600 baudios

fediverse.tv/w/eH9q2DHB4PkL21L

Hacker Newsh4ckernews
2025-11-04

Launch HN: Plexe (YC X25) – Build production-grade ML models from prompts

plexe.ai/

Hacker Newsh4ckernews
2025-10-30

Launch HN: Propolis (YC X25) – Browser agents that QA your web app autonomously

app.propolis.tech/#/launch

2025-10-30

If I could turn back time, I’d come up with a slogan so bad that X.25 would have certainly won the Protocol Wars:

I PEE
YOU PEE
WE ALL PEE
FOR I.P.

#retrocomputing #x25 #tech

BLACKVOID ⚫️blackvoid
2025-09-22

New blog post:
Bring hardware transcoding back to models with some custom modules, courtesy of the RRorg team.

blackvoid.club/unlocking-plex-

Hacker Newsh4ckernews
2025-09-18
Kevin Karhan :verified:kkarhan@infosec.space
2025-09-05

@wyatt does that card do #TokenRing and #X25 too?

  • Otherwise it's just 3 flavours of #Ethernet...

#WhatsMissing: #Ethernet232 aka. #EthernetModem!

infosec.space/@kkarhan/1148860

Hacker Newsh4ckernews
2025-04-23

Launch HN: Cua (YC X25) – Open-Source Docker Container for Computer-Use Agents

github.com/trycua/cua

Kevin Karhan :verified:kkarhan@infosec.space
2025-02-14

@dalias @lauren
@pixelschubsi

Also the blatant dismissal of absolitely basic #OpSec & #ComSec is just flabberghasting.

Only #decentralized, #OpenSource & #OpenStandards can actuall survive long-term and remain #secure.

It's the same reasons we use #PGPG/MIME & #SSH and not #X400 & #X25!

IOW: Think "How can you weaponize Signal?" and see what you csn do just holding key people in contempt...

The less #info a provider has, the less they can be forced to snitch upon customers.

"#JustUseSgnal!" is a form of dangerous "#TechPopulism" aimed at bamboozling #TechIlliterates who don't know better, abusing information asymetry to pull rank instead of investing the time and effort to *explain "how" and "why" this is indeed a good or bad idea.

The only ones that have a chance to beat that are @delta / #deltaChat but that's just #PGP/MIME #eMail in a nice UI...

  • You may now laugh at me and think my "#TinfoilHat sits too tight" but I'm shure sooner or later I'll be evidenced as correct...
Kevin Karhan :verified:kkarhan@infosec.space
2025-02-03

@fale @binford2k I mean, it's true.

  • That's why #eMail & #HTTP 1.x are still used to this day yet noone uses ICQ and only few businesses use #X25 & #AS2...
2024-10-09

Nuevo Monográfico!
"La historia de Telenet, y la Comercialización de la conmutación de paquetes en los Estados Unidos"
#gemini #x25 #redes
gemini://texto-plano.xyz/peron

oneguynickoneguynick
2024-04-30

MFJ bids us Farewell:

MFJ and ARRL catalogs sat near my Computer Shopper as dreams of things I could not afford. I was sad to hear that MFJ is finally shutting its doors, even if it is apparent to some degree that time has passed.  

There was something special about flipping page after page, wishing for something. The posters of an Icom IC-706 or DEC Alpha that graced my walls seem so distant in time now.

hackaday.com/2024/04/29/farewe

2024-01-25

RJE: распределенные вычисления эпохи мезозоя

Говорят, что современная технология разделения ресурсов в концепции ЦОД берет свое начало с появления RJE — Remote job entry , или удаленной пакетной обработки. Утверждение спорное, однако сам по себе механизм RJE интересен прежде всего с исторической точки зрения, поскольку его можно считать как минимум предтечей различных терминальных систем. Вот об этом механизме, а также об использовавшем его железе мы сегодня и поговорим.

habr.com/ru/companies/serversp

#RJE #мейнфреймы #IBM #Remote_Batch #OS/360 #System/360 #Synchronous_transmitreceive_(STR) #BSC #Bisync #Houston_Automatic_Spooling_Priority #HASP #HDLC #X25

Hans Hübnerhanshuebner
2023-12-17

The synchronous serial interface of my VAX failed and needed repair - Not a fun task given the amateurish setup in my basement. After extracting the machine and fixing a couple of cracked solder joints on the DSW42-AA, it is now back on TELEBAHN. After re-assembly, the setup looks neater than before, but I still dread the next time something fails.

A VAX and a Sun connected to a cisco router through serial ports, plus associated cables, support hardware and the console screen.
2023-10-26

Stuff To Read: OSI: The Internet That Wasn’t – IEEE Spectrum

If you were a geek and online in (not least) UK academia in the 1980s and early 1990s, you were probably not using TCP/IP except on the local LAN of the Computer Science department. This was because people who sat on committees and who were therefore very Clever™ had decided what your network should be like, viz: a horrible glorified phone network where other prefabricated computer services would TellYouWhatYouNeedToKnow™.

This is the story of that network:

https://spectrum.ieee.org/osi-the-internet-that-wasnt

Aside: one of the more interesting things about this design was that it shared later architectural aspects with Tor Onion Networking – viz: The Dark Net – e.g. Circuit-Switching, probably for equally architectural reasons.

#janet #osi #x25

https://alecmuffett.com/article/107966

Hans Hübnerhanshuebner
2023-10-20

My TELEBAHN gear is back up after the convention weekends

A VAX 4000-105A and a SPARCstation IPX connected to a cisco 2810 router through synchronous serial lines using the X.25 protocol, plus associated networking hardware.
From: =?iso-8859-10?Q?=e6strid?=astrid@infosec.exchange
2023-10-04

your call could not be completed because (check one)
[_] busy
[_] broken
[_] inscrutable protocol error
[_] collect call declined
[_] incompatible codecs
[_] you mumbled while dialing
[_] your ship hasn't come in

#x25

table describing the reasons a call can fail, from ITU specification X.25.  partial transcript:

TABLE 5-7/X.25
Coding of clearing cause field in clear indication packet

DTE originated
Number busy
Out of order
Remote procedure error
Reverse charging acceptance not subscribed
Incompatible destination
Fast select acceptance not subscribed
Ship absent
Invalid facility request
Access barred
Local procedure error
Network congestion
Not obtainable
ROA out of order

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst