Search
268 results for “omegabyte”
-
Was going through old physical photos, weeding out all the old 'nameless landscape and mountain' shots, prints with people on them that I now have no recollection of.... etc, as one does at this time of year.
Found this interesting one - that's my desk at work back in '96. The IBM tower behind the desk was the TV station's web server. The hardware stack on top was the ISDN connection to our ISP. At that time, local ISP's didn't offer web hosting of the kind we wanted/needed.
If you want a giggle, check out the Wayback Machine snapshot of the site.
Heh, the system specs:
'Our webserver is an IBM PC Server 320 with 3 gigabytes of hard disk space, 156 megabytes of RAM, running on an Intel Pentium 90mhz processer (with the ability to upgrade to dual Pentiums).'https://web.archive.org/web/19961230143005/http://www.itv.ca/
#YEG #CITV #Internet #Website #RetroTech #WaybackMachine #WebDesign #OldSchoolComputing #Alberta #Canada #Television #Broadcasting BroadcastingHistory
-
Was going through old physical photos, weeding out all the old 'nameless landscape and mountain' shots, prints with people on them that I now have no recollection of.... etc, as one does at this time of year.
Found this interesting one - that's my desk at work back in '96. The IBM tower behind the desk was the TV station's web server. The hardware stack on top was the ISDN connection to our ISP. At that time, local ISP's didn't offer web hosting of the kind we wanted/needed.
If you want a giggle, check out the Wayback Machine snapshot of the site.
Heh, the system specs:
'Our webserver is an IBM PC Server 320 with 3 gigabytes of hard disk space, 156 megabytes of RAM, running on an Intel Pentium 90mhz processer (with the ability to upgrade to dual Pentiums).'https://web.archive.org/web/19961230143005/http://www.itv.ca/
#YEG #CITV #Internet #Website #RetroTech #WaybackMachine #WebDesign #OldSchoolComputing #Alberta #Canada #Television #Broadcasting BroadcastingHistory
-
Was going through old physical photos, weeding out all the old 'nameless landscape and mountain' shots, prints with people on them that I now have no recollection of.... etc, as one does at this time of year.
Found this interesting one - that's my desk at work back in '96. The IBM tower behind the desk was the TV station's web server. The hardware stack on top was the ISDN connection to our ISP. At that time, local ISP's didn't offer web hosting of the kind we wanted/needed.
If you want a giggle, check out the Wayback Machine snapshot of the site.
Heh, the system specs:
'Our webserver is an IBM PC Server 320 with 3 gigabytes of hard disk space, 156 megabytes of RAM, running on an Intel Pentium 90mhz processer (with the ability to upgrade to dual Pentiums).'https://web.archive.org/web/19961230143005/http://www.itv.ca/
#YEG #CITV #Internet #Website #RetroTech #WaybackMachine #WebDesign #OldSchoolComputing #Alberta #Canada #Television #Broadcasting BroadcastingHistory
-
Do I know any #zipdrive experts? I have two USB zip drives (100 megabytes). On both as soon as I power them on the green and amber lights turn on, and stay on. There's a second amber led on the PCB which flashes irregularly.
The device doesn't enumerate as a USB device at all, it appears entirely dead. The eject button similarly does nothing.
Does anyone know of any common board level issues with these devices?
-
It astounds me that so many companies - large, well-funded companies whose businesses utterly depend on email communications with their customers - so frequently send me multipart/alternative email containing a multi-megabyte text/HTML part, and a completely blank text/plain part.
For those of you who aren't email and MIME nerds, the MIME type declaration "multipart/alternative" means "here are message parts containing more than one presentation of the same information, so show the user whichever one is most appropriate for them".
And so users like me, who use a plaintext/console mail reader, or who have a preference for plain text selected in their reader, open a message like this and are greeted by a completely blank message.
Well done, Company! Excellent, no notes.
Maybe you should hire someone who cares about and understands email standards? Hint, hint - I'm available.
#email #MIME #multipart #MultipartAlternative #TextHTML #TextPlain #plaintext #standards #incompetent #incompetence
-
@thomasfuchs The #FirstHardDrive I coveted, IIRC, was 3 megabytes for $5K (maybe 5MB for $3K) for an #Atari800 in the very early #1980s. Hard to imagine in this day of $10 32GB microsd cards and 8GB #RaspberryPi #SBCs
-
Also, the two, 2TB drives I ordered? With shipping, $45.
Y'all I remember saving up $200 to purchase a 1.2gig drive.
More than that, I remember a cousin who has 1 megabyte of storage and we were all like, "How will you ever fill that up?"
-
more cleveland free-net history:
"Originally Free-Net ran on an AT&T 3B2/400 computer with 4 megabytes of RAM and 72 MB of hard disk storage.
The CPU was a WE 32100 chip with a 10 megahertz clock operating under AT&T’s Unix System V operating system. Software was written in C.
AT&T donated $50,000 worth of computer equipment and software."
source: https://web.archive.org/web/20120828035003/http://blog.case.edu/archives/2012/07/index
-
Well I can call that a resounding victory. Dual booting Sorbet Leopard + Mac OS 9.22 on a #MacMiniG4
It was good for one reason: seeing long-hated Internet Explorer launch instantly and use 17 megabytes of RAM. Somewhere along the way we must have done something wrong.
Now onto the part where I install #Morphos. Something I never did. Hopefully the install will work from USB with same OpenFirmware commands.
-
#nibrans is a #publicdomain nibble based rANS coder.
nibrans is an #singleheader #SSE2 accelerated encoder and decoder for the rANS arithmetic coding format. rANS offers near-optimal data compression while having an adaptable frequency structure, unlike Huffman coding which uses a static structure. nibrans encode and decode data at a rate of up to 75-95 megabytes per second.
Website 🔗️: https://github.com/BareRose/nibrans
#free #opensource #foss #fossmendations #programming #library #compression
-
Bash csh zsh ksh tksh fish are powerful
Entire networks can be controlled and build with them.
Let's take for example command line tools to control media output
For me e.g mplayer and vlc -I cli are much more interesting when it comes down to standard control of media playback. I prefer to use MOC (mocp) Music 🎼 on Console, instead of bulky RAM hungry programs, which go on the internet to fetch data that I never asked for and thus burn bandwidth
The memory footprint of Music on Console is so low that you can use it on a system which has been built more than two and a half decades ago.
The only graphical media playback program I know that can do that also has been written by my friend Andy Loafoe and that is alsaplayer
Andy programmed alsaplayer when he saw Delitracker playing on my Amiga systems
We're talking the period when Linux was barely moving in Xwindows when you had window managers like fvwm twm and few others.
The alsa audio interface was also just Born.It is within this context that Andy envisioned alsaplayer. It should be modular just like delitracker Amiga, it should be lightweight daily tracker runs on an Amiga 500 with just half A megabyte of chip ram
That should still be memory left to do other the things so straight calls were made to widget libraries.Within a few weeks to a few months of coding alsaplayer came out of Alpha and went Bèta in code stability.
Because everything was written with efficiency in mind and it was programmed as portable as possible, alsaplayer can still be used many decades after It has been written, one of the main reasons is that it has been coded by a command line programmer
#programming #Bash #csh #zsh #ksh #tksh #fish #alsaplayer #MOC #mocp #VLC #widgets #libraries
-
Bash csh zsh ksh tksh fish are powerful
Entire networks can be controlled and build with them.
Let's take for example command line tools to control media output
For me e.g mplayer and vlc -I cli are much more interesting when it comes down to standard control of media playback. I prefer to use MOC (mocp) Music 🎼 on Console, instead of bulky RAM hungry programs, which go on the internet to fetch data that I never asked for and thus burn bandwidth
The memory footprint of Music on Console is so low that you can use it on a system which has been built more than two and a half decades ago.
The only graphical media playback program I know that can do that also has been written by my friend Andy Loafoe and that is alsaplayer
Andy programmed alsaplayer when he saw Delitracker playing on my Amiga systems
We're talking the period when Linux was barely moving in Xwindows when you had window managers like fvwm twm and few others.
The alsa audio interface was also just Born.It is within this context that Andy envisioned alsaplayer. It should be modular just like delitracker Amiga, it should be lightweight daily tracker runs on an Amiga 500 with just half A megabyte of chip ram
That should still be memory left to do other the things so straight calls were made to widget libraries.Within a few weeks to a few months of coding alsaplayer came out of Alpha and went Bèta in code stability.
Because everything was written with efficiency in mind and it was programmed as portable as possible, alsaplayer can still be used many decades after It has been written, one of the main reasons is that it has been coded by a command line programmer
#programming #Bash #csh #zsh #ksh #tksh #fish #alsaplayer #MOC #mocp #VLC #widgets #libraries
-
Bash csh zsh ksh tksh fish are powerful
Entire networks can be controlled and build with them.
Let's take for example command line tools to control media output
For me e.g mplayer and vlc -I cli are much more interesting when it comes down to standard control of media playback. I prefer to use MOC (mocp) Music 🎼 on Console, instead of bulky RAM hungry programs, which go on the internet to fetch data that I never asked for and thus burn bandwidth
The memory footprint of Music on Console is so low that you can use it on a system which has been built more than two and a half decades ago.
The only graphical media playback program I know that can do that also has been written by my friend Andy Loafoe and that is alsaplayer
Andy programmed alsaplayer when he saw Delitracker playing on my Amiga systems
We're talking the period when Linux was barely moving in Xwindows when you had window managers like fvwm twm and few others.
The alsa audio interface was also just Born.It is within this context that Andy envisioned alsaplayer. It should be modular just like delitracker Amiga, it should be lightweight daily tracker runs on an Amiga 500 with just half A megabyte of chip ram
That should still be memory left to do other the things so straight calls were made to widget libraries.Within a few weeks to a few months of coding alsaplayer came out of Alpha and went Bèta in code stability.
Because everything was written with efficiency in mind and it was programmed as portable as possible, alsaplayer can still be used many decades after It has been written, one of the main reasons is that it has been coded by a command line programmer
#programming #Bash #csh #zsh #ksh #tksh #fish #alsaplayer #MOC #mocp #VLC #widgets #libraries
-
Bash csh zsh ksh tksh fish are powerful CLI tools
Entire networks can be controlled and build with them.
Let's take for example command line tools to control media output
For me e.g mplayer and vlc -I cli are much more interesting when it comes down to standard control of media playback. I prefer to use MOC (mocp) Music 🎼 on Console, instead of bulky RAM hungry programs, which go on the internet to _fetch data that I never asked for$ and thus burn bandwidth
The memory footprint of Music on Console is so low that you can use it on a system which has been built more than two and a half decades ago.
The only graphical media playback program I know that can do that also has been written by my friend Andy Loafoe and that is alsaplayer
Andy programmed alsaplayer when he saw Delitracker playing on my Amiga systems
We're talking the period when Linux was barely moving in Xwindows when you had window managers like fvwm & twm and few others.
The alsa audio interface was also just born.It is within this context that Andy envisioned alsaplayer. It should be modular just like Delitracker Amiga, it should be lightweight Delitracker runs on an Amiga A500 with just half A megabyte of chip ram
That should still be memory left to do other the things so straight calls were made to widget libraries which explains the simplicity yet great usability of the UI. For as far as I remember Andy has also written an API for AlsaplayerWithin a few weeks to a few months of coding alsaplayer came out of Alpha and went Bèta in code stability.
Because everything was written with efficiency in mind and it was programmed as portable as possible, alsaplayer can still be used many decades after It has been written
One of the main reasons is that it has been coded by a command line programmer
Alsaplayer has been ported to many different Operating System Architectures including freeBSD
For me working on the command line has always been logical, graphic user interfaces were only used when absolutely necessary think about GEOS on the C64
I started coding on the Casio FX 700p programmable calculator. I went so far to make program code that was in the book more efficient by crunching all the commands with two letter abbreviations.
The power of the Command Line something the Young Ones should Learn
Alsaplayer manpage
#programming #Bash #csh #zsh #ksh #tksh #fish #alsaplayer #MOC #mocp #VLC #widgets #libraries #Amiga #RetroComputing
-
@sabine_depew Meinen #A2000 hatte ich von 1991 bis 2001. Mit RAM-Erweiterung auf 9MB, Co-ProzessorCard und interner 40 Megabyte-SCSI-HD. Leider gab es das coole #Amiga 1000-Gehäuse nie mit der Leistung eines #A4000. Vielleicht baue ich mir sowas mal 🙂
-
@sabine_depew Meinen #A2000 hatte ich von 1991 bis 2001. Mit RAM-Erweiterung auf 9MB, Co-ProzessorCard und interner 40 Megabyte-SCSI-HD. Leider gab es das coole #Amiga 1000-Gehäuse nie mit der Leistung eines #A4000. Vielleicht baue ich mir sowas mal 🙂
-
@sabine_depew Meinen #A2000 hatte ich von 1991 bis 2001. Mit RAM-Erweiterung auf 9MB, Co-ProzessorCard und interner 40 Megabyte-SCSI-HD. Leider gab es das coole #Amiga 1000-Gehäuse nie mit der Leistung eines #A4000. Vielleicht baue ich mir sowas mal 🙂
-
Yes source based distro's have been around since the very beginning - in fact, MCC Interim Linux and #SLS weren't far from that mark, except that they merely tried to make it a bit more convenient by packaging up tarballs to be exploded during installation. And there's always #LFS.
If you think about Slackpkg - and you consider that you can actually re-install the entire system by compiling every single component of the default (full) install with the evocation of a single command, followed by the customization of your entire system by installing every kind of software imaginable through the use of #sbopkg or some other automated, dependency resolving package manager that uses #SlackBuilds (which are downloaded, then exectuted, and subsequently download the latest release of he software package desired, which is in turn compiled, packaged, and exploded) - you actually have a fully source based distro installed on your box.
That's right - Slackware is (can be forced to be) an entirely source based distro installed on your device.
And choosing to convert from a point release to Slackware -current switches you from a point release to a #Rolling_Release distro.
*Debian Testing, aka at this time, Trixie is a rolling release. #Arch_Linux is a rolling release, SourceMage and Lunar Linux are source based distros based on #Sorcerer_Linux, the original fully source based Linux distro released when Linux was only about 8yrs old in 2000, and the #Gentoo or #Funtoo source based Linux distros.
SystemD my ass. That has nothing to do with nothing in that conversation - it's completely non-sequitur and truth be told, most source based distros (Arch, Gentoo) support the type of init system that *YOU CHOOSE. For Debiantards such as myself, well..... There's #Devuan - and that's very refreshing to actually have control over your system again with true init scripts. But I rarely use Devuan, even though I've been associated with the initiative since its inception, after leaving the #Mageia team several years ago.
As I state in almost all of my profiles, I'm a Slacker, since 1993 (Slackware Linux), and I'm also a bit of a #Debiantard. On the BSD side, after leaving #Jolix (386BSD) for Slackware, I've pretty much settled on either #OpenBSD or #Dragonfly_BSD, w/the awesome #HAMMER2 FS. I still have a lot of love for #FreeBSD and of course #NetBSD - where I spend a lot of time in my proper #Korn Shell....
But what the heck does any of this have to do with a comparison of using Gentoo Linux being akin to using SystemD?
I don't like SystemD - but if you're a realist, that doesn't mean you forgo using distros that only have that init tooling. You just roll with the punches and keep following the innovations that support you - NO ONE STILL RUNS WINDOWS XP in production - at least, no one outside of state mental hospitals, that's just insane to do in a forward facing business environment.
But a lot of companies do leverage OpenRC, SysVinit, etc., instead of SystemD - that's not going away, and SystemD itself and Poetering have their own up and coming challengers.
SystemD is (supposed to be, originally) a way to boot your box. Yes, it's indeed encroached upon other landscapes since, but not all of those constructs are even considered by many mainstream distros - it's not a fact of life. Other init systems thrive in the UNIX world to this day and will continue to do so.
Likewise, Source based Linux distros are just one among many distros that exist, and may or may not leverage SystemD as their init systems - to really get a good grasp of this, I recommend doing a few Arch Linux installs - with and without SystemD as the base init system. Heck, even Debian still supports your regular, good old #syslog, and at every turn during your updates, reminds you how to keep it enabled since the whole journalctl crap just isn't as elegant, IMO.
Personally, I think more concurrent options are usually better - space is cheap. Storage no longer costs a dollar a meg. or worse, like it was when I was a kid, a few thousand dollars a meg. That's right... MegaByte - Not TB for penny's!
Okay so now I'm waiting to hear back from the OP and see just what the heck they meant when I got triggered. In the meantime....
Enjoy installing and using #Sorcerer_Linux, or the subesquent forks of it's surviving lineage like #SourceMage and #Lunar_Linux - you're now a part of mainstream source-basedLinux History once you do 🤘 💀 🤘
#tallship #Linux #FOSS #distros #Sorcerer
⛵️
.
RE: https://social.sdf.org/users/tallship/statuses/111957857148746923
-
Yes source based distro's have been around since the very beginning - in fact, MCC Interim Linux and #SLS weren't far from that mark, except that they merely tried to make it a bit more convenient by packaging up tarballs to be exploded during installation. And there's always #LFS.
If you think about Slackpkg - and you consider that you can actually re-install the entire system by compiling every single component of the default (full) install with the evocation of a single command, followed by the customization of your entire system by installing every kind of software imaginable through the use of #sbopkg or some other automated, dependency resolving package manager that uses #SlackBuilds (which are downloaded, then exectuted, and subsequently download the latest release of he software package desired, which is in turn compiled, packaged, and exploded) - you actually have a fully source based distro installed on your box.
That's right - Slackware is (can be forced to be) an entirely source based distro installed on your device.
And choosing to convert from a point release to Slackware -current switches you from a point release to a #Rolling_Release distro.
*Debian Testing, aka at this time, Trixie is a rolling release. #Arch_Linux is a rolling release, SourceMage and Lunar Linux are source based distros based on #Sorcerer_Linux, the original fully source based Linux distro released when Linux was only about 8yrs old in 2000, and the #Gentoo or #Funtoo source based Linux distros.
SystemD my ass. That has nothing to do with nothing in that conversation - it's completely non-sequitur and truth be told, most source based distros (Arch, Gentoo) support the type of init system that *YOU CHOOSE. For Debiantards such as myself, well..... There's #Devuan - and that's very refreshing to actually have control over your system again with true init scripts. But I rarely use Devuan, even though I've been associated with the initiative since its inception, after leaving the #Mageia team several years ago.
As I state in almost all of my profiles, I'm a Slacker, since 1993 (Slackware Linux), and I'm also a bit of a #Debiantard. On the BSD side, after leaving #Jolix (386BSD) for Slackware, I've pretty much settled on either #OpenBSD or #Dragonfly_BSD, w/the awesome #HAMMER2 FS. I still have a lot of love for #FreeBSD and of course #NetBSD - where I spend a lot of time in my proper #Korn Shell....
But what the heck does any of this have to do with a comparison of using Gentoo Linux being akin to using SystemD?
I don't like SystemD - but if you're a realist, that doesn't mean you forgo using distros that only have that init tooling. You just roll with the punches and keep following the innovations that support you - NO ONE STILL RUNS WINDOWS XP in production - at least, no one outside of state mental hospitals, that's just insane to do in a forward facing business environment.
But a lot of companies do leverage OpenRC, SysVinit, etc., instead of SystemD - that's not going away, and SystemD itself and Poetering have their own up and coming challengers.
SystemD is (supposed to be, originally) a way to boot your box. Yes, it's indeed encroached upon other landscapes since, but not all of those constructs are even considered by many mainstream distros - it's not a fact of life. Other init systems thrive in the UNIX world to this day and will continue to do so.
Likewise, Source based Linux distros are just one among many distros that exist, and may or may not leverage SystemD as their init systems - to really get a good grasp of this, I recommend doing a few Arch Linux installs - with and without SystemD as the base init system. Heck, even Debian still supports your regular, good old #syslog, and at every turn during your updates, reminds you how to keep it enabled since the whole journalctl crap just isn't as elegant, IMO.
Personally, I think more concurrent options are usually better - space is cheap. Storage no longer costs a dollar a meg. or worse, like it was when I was a kid, a few thousand dollars a meg. That's right... MegaByte - Not TB for penny's!
Okay so now I'm waiting to hear back from the OP and see just what the heck they meant when I got triggered. In the meantime....
Enjoy installing and using #Sorcerer_Linux, or the subesquent forks of it's surviving lineage like #SourceMage and #Lunar_Linux - you're now a part of mainstream source-basedLinux History once you do 🤘 💀 🤘
#tallship #Linux #FOSS #distros #Sorcerer
⛵️
.
RE: https://social.sdf.org/users/tallship/statuses/111957857148746923
-
CW: experience with mobile carriers
We have five cellphones here at HyperTwin Manor -- four people and one spare phone.
Up until last year or so, we were using Republic Wireless because at the time we first signed up (2017) what they offered was pretty progressive. They're also based near us (Raleigh) which, although it doesn't exactly make them a "local business", nonetheless seemed like a plus. (I mean, why ship those wireless megabytes all the way across the country from Silicon Valley if I can get them from closer?*)
Then last year or so, they got bought up by Dish Network, and the enshittification process began. To start with, they dropped support for calls-over-wifi, giving the justification that most modern phones supported it in hardware -- which my main phone doesn't, and it immediately began to be difficult to send and receive texts from inside the office.
So I started looking around, and found Mint Mobile -- which offered (at the time) 4GB/mo instead of RW's 1GB for (effectively) $5 less per month ($15). They sent a spare "try out out" SIM with one of my original orders, and that became the spare phone.
After thinking it over for a bit, I started the process of switching our phones over -- but part of RW's Enshittification Process means that you can no longer get the PIN to transfer your number out by going to Republic's web site; you have to call them. (Can you say "customer lock-in", boys and girls?)
Folks, I have phone-phobia, so this was a BFD. I had the spoons to do it for my phone and (eventually) one of the kids' phones (the one who kept using up his 1GB accidentally), and then I ran out of steam.
...and then just this past month, Republic (and Dish? dunno) got bought up by Boost Mobile. We were sent new SIMs and told that the price would now be $25 (another $5 more, making it $10 more than Mint).
I have no real prior experience with Boost, and a vaguely negative impression of them, so my first thought was "okay, now we really need to move the last 2 phones over) -- but apparently the plan we're on is this new(?) service, Boost Infinite, which has "unlimited bandwidth"... which usually means "we don't cut you off completely after the limit, just throttle you down to liek a bad DSL connection in the rain", but I can find no indication that there's actually any limit.
So... even though it's an extra $20/mo, I'm willing to give it a try and see how the service is.
I figure there's got to be a catch somewhere. It does still allow the phones to be used as hotspots, but it's possible there's some kind of throttling on that ("unlimited" data plans tend to throttle hotspots or disallow them, in my experience). If there isn't, then we could in theory use a phone as a backup internet if Spectrum goes out (...so there's really got to be a catch, somewhere).
*
This is humor. It is permitted to giggle.
#mobileService #BoostMobile RepublicWireless #MintMobilecc: @Harena
-
qalc looks pretty cool, like MATLAB #sym or #WolframAlpha in #Linux (even #termux !)
```termux
$ pkg install qalc/stable
...$ qalc 'now + (500GB / (50MB / second))'
now + ((500 × gigabyte) / ((50 × megabyte) / second)) ≈ "2022-08-30T00:23:47"
```
https://teddit.net/r/commandline/comments/wyhdm0/qalc_is_awesome/ -
The "Astra Monitor" lightweight system resources monitoring #GNOMEShell extension is seriously awesome.
Very useful to keep an eye on my system (without having GNOME System Monitor running all the time) to catch any runaway process eating excessive amounts of CPU or RAM over long periods of uptime, or to remind myself that I really need to free disk space because I only have about 600 megabytes left out of 2 terabytes :blobsweats: -
Pretty happy with #BorgBackup's #Vorta GUI (hat tip to @amin for the recommendation).
4x hourly backup take only ~30 seconds to run and consume as little as half a megabyte.
The backups aren't natively user-browsable like backintime's was, but I'll take that in exchange for not having incremental backups that are no less than 111MiB because everything is a symlink.
-
Wegen 15 Megabyte: Google-Update sorgt für Probleme auf Pixel-Smartphones – so behebt ihr sie | t3n https://t3n.de/news/15-megabyte-google-update-probleme-pixel-smartphones-1724480/ #Google :google: #GooglePixel10
-
I just found a 1 megabyte AMIGA SIMM memory module in a box of various junk at work. What's it worth based on current memory prices and can I buy a yacht?
-
I just found a 1 megabyte AMIGA SIMM memory module in a box of various junk at work. What's it worth based on current memory prices and can I buy a yacht?
-
Getting lots of BIMI images using Python
https://shkspr.mobi/blog/2024/06/getting-lots-of-bimi-images-using-python/
I've written before about the moribund BIMI specification. It's a way for brands to include a trusted logo when they send emails. It isn't much used and, apparently, is riddled with security issues.
I thought it might be fun to grab all the BIMI images from the most popular websites, so I can potentially use them in my SuperTinyIcons project.
BIMI images are SVGs. Links to a site's BIMI are stored in a domain's DNS records. All BIMI records must be on a
default._bimi.subdomain.If you run
dig TXT default._bimi.linkedin.comyou'll receive back:;; ANSWER SECTION:default._bimi.linkedin.com. 3600 IN TXT "v=BIMI1; l=https://media.licdn.com/media/AAYQAQQhAAgAAQAAAAAAABrLiVuNIZ3fRKGlFSn4hGZubg.svg; a=https://media.licdn.com/media/AAYAAQQhAAgAAQAAAAAAALe_JUaW1k4JTw6eZ_Gtj2raUw.pem;"Awesome! We can grab the .svg URl and download the file.
Getting a list of BIMI enabled domains is difficult. Thankfully, Freddie Leeman has done some excellent analysis work and was happy to share a list of over 7,000 domains which have BIMI.
Let's get cracking with a little Python. First up, install DNSPython if you don't already have it.
This gets the TXT record from the domain name:
import socketimport dns.resolverresponse = dns.resolver.query('default._bimi.linkedin.com', 'TXT')result = response.rrset.to_text()print(result)There are various ways of extracting the URl. I decided to be lazy and use a regex. Sue me.
import repattern = r'l=(https[^;"]*[;"])'match = re.search(pattern, result)if match: # Remove the trailing semicolon or quote mark url = match.group(1).rstrip(';\"') print(f'Matched URL: {url}')else: print(f'No match: {result}')Putting it all together, this reads in the list of domains, finds the BIMI TXT record, grabs the URl, and saves the SVG.
import socketimport dns.resolverimport reimport requestsheaders = { 'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101 Firefox/91.0'}pattern = r'l=(https[^;"]*[;"])'domain_file = open('domains.txt', 'r')domains = domain_file.readlines()domains.sort()for domain in domains: bimi_domain = "default._bimi." + domain.strip() try: response = dns.resolver.query(bimi_domain, 'TXT') result = response.rrset.to_text() match = re.search(pattern, result) if match: # Remove the trailing semicolon or quote mark svg_url = match.group(1).rstrip(';\"') print(f'Downloading: {svg_url}') try: svg = requests.get(svg_url, allow_redirects=True, timeout=30, headers=headers) open(domain.strip() +'.svg', 'wb').write(svg.content) except: print(f'Error with {domain}: {result}') else: print(f'No match from {domain}: {result}') except: print(f'DNS error with {bimi_domain}')Obviously, it could be made a lot more efficient and download the files in parallel.
I found a few bugs in various BIMI implementations, including:
- ted.com and homeadvisor.com uses a
httpURl - consumerreports.org and sleepfoundation.org has a misplaced space in their TXT record
- audubon.org had an invalid certificate
- mac.com was blank - as was discogs.com, livechatinc.com, icloud.com, me.com, lung.org, miro.com, protonmail.ch and many others.
- alabama.gov had a timeout - as did nebraska.gov, uclahealth.org and several others.
- politico.com had a 404 for their BIMI - as do lots of others.
- coopersurgical.com is 8MB!
- There are loads of SVGs which bust the 32KB maximum size requirement - some by multiple megabytes.
I might spend some time over the next few weeks optimising the code and looking for any other snafus. I didn't find any with ECMAScript in them. Yet!
- ted.com and homeadvisor.com uses a
-
"In 1966 [...] five megabytes of data—a relatively small amount by today's standards—required an astounding 62,500 punched cards."
https://www.vintag.es/2025/02/5-megabytes-of-computer-data.html
#technology #history #TechHistory #VintageTech #RetroComputing #data #PunchCards
-
New feature.
I've added #fulltextsearch to beyng.com using #PageFind. I'm excited because Google/Bing/Yandex only index 10% of the ~40,000 pages–philosophy texts don't contain the keywords advertisers pay for. Now it's possible to search them all.
Features I'm hoping for in future releases of PageFind are open-results-in-new-tab and include og:image in results.
It takes half-a-day to FTP upload the ~180 megabytes of index files, so I won't be updating indexes often.
-
New NIST SP800-63b on password length (seems solid):
Users should be encouraged to make their passwords as long as they want within reason. Since the size of a hashed password is independent of its length, there is no reason to prohibit the use of lengthy passwords (or passphrases) if the user wishes. However, extremely long passwords (perhaps megabytes long) could require excessive processing time to hash, so it is reasonable to have some limit.
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-63B-4.pdf