buc.ci is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
I am thinking about putting my researched list of 925 release dates for videogames from 1990 to 2004 on my Neocities site.
Which means HTML and nothing else.
What would be a sane method to turn a 1000 row spreadsheet into an HTML table? 🤔
Staring down the barrel of "nobody knows how to do anything without #JavaScript any more". All I want to do is make my #ebook readable in a web-browser. Do I have to make _everything_ myself!?
No fancy UI-styling yet but there's nothing stopping me providing widgets for changing light/dark theme, colours, fonts, line-spacing -- you name it -- no JavaScript needed. Nothing to install, no Python script, no build system; it's just an #HTML + #CSS file. WHY IS THIS A LOST ART!??
Per uno scambio più equo, vorrei portare qualche collezione nel profilo.
Iniziamo da questa sull'IndieWeb, ossia coloro che portano avanti con passione blog e siti personali.
Purtroppo non posso aggiungere tutti quelli che vorrei (alcune istanze non lo permettono), e come al solito mi dimenticherò di qualcuno.
Aggiungo anche, andando a rinnovare un precedente post:
@stefano
@lorenzo
@dado
@denial403
@giacomo
This is a great take from @jimniels on designing in the browser.
I don’t know that I’ve ever once coded up one of my designs exactly as its source. Once that code hits, it’s always gonna influence what you do with it.
He says “with an interface, you have to use it, feel it, interact with it, and poke at it.” 100%. And that’s the reason I believe every designer should code their own work. Once a design is in a browser, everything changes.
You know email has over time with the use of mobile phones and later (yes I’m that old) smartphones become more and more … difficult.
I mean traditionally you read them on your computer, then phone and now smartphones. And often it’s there you first read it, while in your couch, on a trip or just on the go.
You do know that they still have pretty small (compared to a computer) screens?
Certainly all people don’t know this, at least those who create contents and send them out, well that was no problem back in time when it was plain text.
But somehow someone thought of wouldn’t it be nice to send mail in the forms of html instead of text ( the format mail upon time, was created for and ment to be)
The problem is when you create html content on your 32” widescreen with fixed format and then try to read it on a 6” phone the lines don’t wrap.
How fu*** stupid people has become today
Why would that be better than plain text????????
Whyyyy
Today the rat met the bear
#OverUnder 073 with @ratfactor
He shares his thoughts about #HTML #emails, #Letterboxd, #Zettelkasten, #rats, and, #apple #pies.
His #blog is older than #Google
He also replied to @yannick's question.
And, we got a recommendation for two #books.
#bloggers #bookstodon #book #fediverse #mastodon #food #BSD #Linux
So, I'm writing a reporting system for my employer's app. It generates reports in #HTML, which the user can look at, print, and save. They look great—modern #browsers are quite good at #typesetting.
But it occurs to me that some users might want to send these reports as #email attachments to colleagues.
To the #IT people on Fedi: is that going to be a problem? Is it common for email servers to block HTML attachments? If so, what do you suggest I do to work around that?
I was told about this blog site, a couple of weeks ago. There are interesting pages listed here
The subjects vary in the manner as seen in the first page (check the screencaps)
## What I really like about this place, is that it loads blazingly fast
I also love the fact that you can use browsers in your,
* bash
* csh
* ksh
* zsh
* sh
* fish
* without any bloat just like browsing should be, everywhere
https://rldane.space/junited-2026.html
Thank you @rl_dane
#Blog #site #fast #HTML #great #cool #sweet #nice #programming #Python
I really want to post the <header> .. </header> section I need to change in a bunch of #HTML files, but it'd play hell with screen readers.
Definitely a job for #sed. A complicated job for sed. A lot of characters will need to be escaped.
Getting the escapes right will still be faster than changing each file manually.
Over the weekend, I did some document creation with HTML and CSS. I wanted a simple two column layout and some textual styles: colors, size, all-caps text transform for section headings.
At first, I was looking for a template. While there are a lot of templates available, I really didn't like the designs I saw.
So just started with a blank text file, saved as .html, and got to work.
It didn't take too long and I had exactly what I was going for.
Used the browser's "Print to PDF" feature and got the document I wanted.
RE: https://oldbytes.space/@Kroc/116364804890198741
No K8s, no Docker, no Node, no React, no #JavaScript, no AI — just 2KB of #HTML + #CSS and one image. How did we get so far from this when a webpage is 10MB and requires several gigs of dependencies to checkout locally now?
Is there really no better WYSIYG HTML editor in 2026 than the no-longer-maintained Bluegriffon?