home.social

#html — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #html, aggregated by home.social.

fetched live
  1. ‹datalist›

    Contains a set of option elements that represent the permissible or recommended options available to choose from within other controls.

    developer.mozilla.org/en-US/do

    #HTML #WebDev #DailyHTML

  2. ‹datalist›

    Contains a set of option elements that represent the permissible or recommended options available to choose from within other controls.

    developer.mozilla.org/en-US/do

    #HTML #WebDev #DailyHTML

  3. hand rolled #HTML is Rock'n'Roll
    #AI generated HTML is...

  4. hand rolled #HTML is Rock'n'Roll
    #AI generated HTML is...

  5. DCRat Campaign Hides Malware Archive Inside SVG Using HTML Smuggling

    Indicators extracted from public reporting. Source: trellix.com/blogs/research/sig

    Pulse ID: 6a7f105c416203282deae39f
    Pulse Link: otx.alienvault.com/pulse/6a7f1
    Pulse Author: CyberHunter_NL
    Created: 2026-08-14 12:55:56

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #CyberSecurity #DCRat #HTML #HTTP #HTTPS #ICS #InfoSec #Malware #OTX #OpenThreatExchange #RAT #RCE #SVG #Trellix #bot #CyberHunter_NL

  6. DCRat Campaign Hides Malware Archive Inside SVG Using HTML Smuggling

    Indicators extracted from public reporting. Source: trellix.com/blogs/research/sig

    Pulse ID: 6a7f105c416203282deae39f
    Pulse Link: otx.alienvault.com/pulse/6a7f1
    Pulse Author: CyberHunter_NL
    Created: 2026-08-14 12:55:56

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #CyberSecurity #DCRat #HTML #HTTP #HTTPS #ICS #InfoSec #Malware #OTX #OpenThreatExchange #RAT #RCE #SVG #Trellix #bot #CyberHunter_NL

  7. Dass der Developer-Konsole in den Browsern nicht zu trauen ist, ist ja bekannt. Aber weiß jemand, warum auch die Quelltextansicht im Chrome den Code falsch darstellt? Im Firefox und wenn ich die Seite mit wget herunterlade und im einfachen Texteditor den puren Quelltext öffne, ist die Syntax richtig. Der Server liefert also korrektes HTML. Oder sind Zeilenumbrüche im srcset-Attribut nicht erlaubt? Der w3c-Validator bemängelt die nicht. :blobcatthink:

    #HTML #fediHelp

  8. Dass der Developer-Konsole in den Browsern nicht zu trauen ist, ist ja bekannt. Aber weiß jemand, warum auch die Quelltextansicht im Chrome den Code falsch darstellt? Im Firefox und wenn ich die Seite mit wget herunterlade und im einfachen Texteditor den puren Quelltext öffne, ist die Syntax richtig. Der Server liefert also korrektes HTML. Oder sind Zeilenumbrüche im srcset-Attribut nicht erlaubt? Der w3c-Validator bemängelt die nicht. :blobcatthink:

    #HTML #fediHelp

  9. My life would be easier if neglected informational WordPress and Joomla sites would be converted to static HTML pages.

    #incidentresponse #wordpress #html #joomla

  10. My life would be easier if neglected informational WordPress and Joomla sites would be converted to static HTML pages.

    #incidentresponse #wordpress #html #joomla

  11. I should at some point get around to writing the specifications for the alternative web document markup language I've had in my head forever.

    HTML isn't bad, but it is definitely constrained by its position as the default markup language for the whole modern web. They need to cater to everyone, from super fancy corporate websites, massive web applications, social media, video sites, encyclopedias, personal homepages, art projects, hobbyists, to professional webdev engineers ...

    I really want something purpose-built for a more semantic, personal hypertext web aimed at enthusiasts.

    Perhaps it wouldn't be as versatile as HTML, but it doesn't need to fit all use cases of every possible target audience or be viable for businesses.

    I am thinking things like …

    • Styling should be handled exclusively by the browser based on semantic elements and application-level user preferences (perhaps minimal style recommendations/hints at best).
    • Differentiating types of hyperlinks; internal navigation links, important main links, optional context/rabbithole links etc.
    • More granular and specific semantic elements, like the uncoupling of times and dates, splitting address/contact elements into specific fields like e-mail and name, quotations with attributions, definitions etc.
    • Integration of other semantic data projects such as MusicBrainz, Wikidata or Wikipedia (holy link rot, but we'll see).
    • More obligatory metadata like authorship, tags, publishing/modification date etc.
    • Integration of non-search engine discoverability features like webrings, directly on a site level
    • Easier cross-document reusable elements, i. e. integrating the same header or footer on each site
    • Extensive entity-oriented data support with URIs, e. g. in-line fetching of things like names, pronouns or contact data from a central 'person' entity URL to automatically propagate things like name changes through the web.

    … and so on.

    I could even experiment with the markup tech itself; it doesn't need to be XML after all. It could even be something like a stand-off annotation document allowing the division of content writing from mark-up. Or something with a similarly simple syntax as Markdown, but with semantic instead of styling information.

    And then comes the arduous task of implementing a parser. :popcorn: I'm so excited.

    #web #webDev #markup #markupLanguages #html #hypertext #www #worldWideWeb #programming #tech

  12. I should at some point get around to writing the specifications for the alternative web document markup language I've had in my head forever.

    HTML isn't bad, but it is definitely constrained by its position as the default markup language for the whole modern web. They need to cater to everyone, from super fancy corporate websites, massive web applications, social media, video sites, encyclopedias, personal homepages, art projects, hobbyists, to professional webdev engineers ...

    I really want something purpose-built for a more semantic, personal hypertext web aimed at enthusiasts.

    Perhaps it wouldn't be as versatile as HTML, but it doesn't need to fit all use cases of every possible target audience or be viable for businesses.

    I am thinking things like …

    • Styling should be handled exclusively by the browser based on semantic elements and application-level user preferences (perhaps minimal style recommendations/hints at best).
    • Differentiating types of hyperlinks; internal navigation links, important main links, optional context/rabbithole links etc.
    • More granular and specific semantic elements, like the uncoupling of times and dates, splitting address/contact elements into specific fields like e-mail and name, quotations with attributions, definitions etc.
    • Integration of other semantic data projects such as MusicBrainz, Wikidata or Wikipedia (holy link rot, but we'll see).
    • More obligatory metadata like authorship, tags, publishing/modification date etc.
    • Integration of non-search engine discoverability features like webrings, directly on a site level
    • Easier cross-document reusable elements, i. e. integrating the same header or footer on each site
    • Extensive entity-oriented data support with URIs, e. g. in-line fetching of things like names, pronouns or contact data from a central 'person' entity URL to automatically propagate things like name changes through the web.

    … and so on.

    I could even experiment with the markup tech itself; it doesn't need to be XML after all. It could even be something like a stand-off annotation document allowing the division of content writing from mark-up. Or something with a similarly simple syntax as Markdown, but with semantic instead of styling information.

    And then comes the arduous task of implementing a parser. :popcorn: I'm so excited.

    #web #webDev #markup #markupLanguages #html #hypertext #www #worldWideWeb #programming #tech

  13. Phantom Stealer Hides Inside PNG Files, Then Steals Your Passwords, Cookies and Crypto

    Indicators extracted from public reporting. Source: splunk.com/en_us/blog/security

    Pulse ID: 6a7d94b079c2c1e42df7974b
    Pulse Link: otx.alienvault.com/pulse/6a7d9
    Pulse Author: CyberHunter_NL
    Created: 2026-08-13 09:56:00

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #Cookies #CyberSecurity #HTML #HTTP #HTTPS #InfoSec #OTX #OpenThreatExchange #Password #Passwords #RCE #ShellCode #Steganography #Word #bot #CyberHunter_NL

  14. Phantom Stealer Hides Inside PNG Files, Then Steals Your Passwords, Cookies and Crypto

    Indicators extracted from public reporting. Source: splunk.com/en_us/blog/security

    Pulse ID: 6a7d94b079c2c1e42df7974b
    Pulse Link: otx.alienvault.com/pulse/6a7d9
    Pulse Author: CyberHunter_NL
    Created: 2026-08-13 09:56:00

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #Cookies #CyberSecurity #HTML #HTTP #HTTPS #InfoSec #OTX #OpenThreatExchange #Password #Passwords #RCE #ShellCode #Steganography #Word #bot #CyberHunter_NL

  15. Inside Multi-Stage Phishing Redirection Chains

    Recent investigations have uncovered sophisticated phishing campaigns employing multi-stage redirection chains that abuse trusted cloud infrastructure and newly registered domains. One campaign exploits Framer, a no-code web platform, combined with Cloudflare Workers to host deceptive landing pages. These pages utilize HTML redirection smuggling via the Blob API, Web Crypto API for decryption, and anti-debugging techniques to evade detection. Another campaign involves device code phishing targeting OneDrive credentials through three-stage redirections using newly registered domains with randomized alphanumeric strings. Both campaigns employ brand impersonation, custom CAPTCHA challenges, and anti-analysis measures including keyboard shortcut blocking. The threat actors leverage a hybrid infrastructure combining legitimate cloud services with short-lived domains to bypass traditional detection methods.

    Pulse ID: 6a7ce26b7815e336e5eee192
    Pulse Link: otx.alienvault.com/pulse/6a7ce
    Pulse Author: AlienVault
    Created: 2026-08-12 21:15:23

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #CAPTCHA #Cloud #CyberSecurity #EDR #HTML #InfoSec #OTX #OpenThreatExchange #Phishing #Rust #bot #AlienVault

  16. Inside Multi-Stage Phishing Redirection Chains

    Recent investigations have uncovered sophisticated phishing campaigns employing multi-stage redirection chains that abuse trusted cloud infrastructure and newly registered domains. One campaign exploits Framer, a no-code web platform, combined with Cloudflare Workers to host deceptive landing pages. These pages utilize HTML redirection smuggling via the Blob API, Web Crypto API for decryption, and anti-debugging techniques to evade detection. Another campaign involves device code phishing targeting OneDrive credentials through three-stage redirections using newly registered domains with randomized alphanumeric strings. Both campaigns employ brand impersonation, custom CAPTCHA challenges, and anti-analysis measures including keyboard shortcut blocking. The threat actors leverage a hybrid infrastructure combining legitimate cloud services with short-lived domains to bypass traditional detection methods.

    Pulse ID: 6a7ce26b7815e336e5eee192
    Pulse Link: otx.alienvault.com/pulse/6a7ce
    Pulse Author: AlienVault
    Created: 2026-08-12 21:15:23

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #CAPTCHA #Cloud #CyberSecurity #EDR #HTML #InfoSec #OTX #OpenThreatExchange #Phishing #Rust #bot #AlienVault

  17. HTML over WebSockets: real-time SPAs with barely any JavaScript

    Building a SPA (Single-page Application) is a complex puzzle: a JavaScript framework that draws the view, an API serving JSON, and 2 independent codebases forced to understand each other through contracts. It is an accepted, professionalized scenario. […]
    — by @andros

    🧑‍💻 en.andros.dev/blog/ef4968f5/ht

    #javascript #websocket #html #webdev #spa #api #json #webdev #frontend #web #barely

  18. HTML over WebSockets: real-time SPAs with barely any JavaScript

    Building a SPA (Single-page Application) is a complex puzzle: a JavaScript framework that draws the view, an API serving JSON, and 2 independent codebases forced to understand each other through contracts. It is an accepted, professionalized scenario. […]
    — by @andros

    🧑‍💻 en.andros.dev/blog/ef4968f5/ht

    #javascript #websocket #html #webdev #spa #api #json #webdev #frontend #web #barely

  19. Andros Fenollosa hilariously suggests we should relive the #1990s by serving #HTML over #WebSockets like it's revolutionary 🤯. Apparently, the cure for complex SPAs is to ditch JavaScript like it’s an overhyped boy band 😆. Who knew the secret to modern web development was to time-travel back to GeoCities-era simplicity? 🚀
    en.andros.dev/blog/ef4968f5/ht #AndrosFenollosa #WebDevelopment #RetroTech #HackerNews #ngated

  20. Andros Fenollosa hilariously suggests we should relive the #1990s by serving #HTML over #WebSockets like it's revolutionary 🤯. Apparently, the cure for complex SPAs is to ditch JavaScript like it’s an overhyped boy band 😆. Who knew the secret to modern web development was to time-travel back to GeoCities-era simplicity? 🚀
    en.andros.dev/blog/ef4968f5/ht #AndrosFenollosa #WebDevelopment #RetroTech #HackerNews #ngated

  21. HTML wirkt auf den ersten Blick simpel. Ein paar Tags, ein bisschen Text, ein paar Links, fertig. Gerade wenn du aus Java kommst, kann HTML schnell wie etwas wirken, das man nebenbei mitnimmt. Keine Klassen, keine Interfaces, keine Exceptions, kein Buildprozess, der erst einmal verstanden ...

    magicmarcy.de/html-meistern-da

    #HTML #Struktur #JavaScript #Coding #Browser #Bedeutung #Formulare #Container #Element #Überschriften #Template #Programming #Webentwicklung

  22. Just released. Judging from its Table of Contents, it promises to be very interesting in mere historical and technical terms. My suspiction is that it runs the danger of being too much enciclopedic.

    From Markup to Markdown: The Evolution of Technical Writing, Typesetting Tools and Frameworks

    Jim Hall (Apress)

    “From Markup to Markdown is a history of how writers have used computers to write, and a look ahead to see what the future looks like for technical writing. This book explores both “technology history” and “how it works” about how we write with computers, with code examples so readers can explore and fully understand how each writing tool and framework works behind the scenes.

    Starting with an overview of the major milestones of writing with digital technologies since the 1960s, you will learn about RUNOFF and how this inspired roff on Unix (and the more familiar versions, nroff and troff). You will also explore word processing milestones like WordStar, and printing technologies like the phototypesetter and the dot matrix printer, before moving onto modern markup and writing systems like HTML, Markdown and DITA and how they play a role in how we write today.

    From Markup to Markdown is ideal for writers, technical communication professionals, history of computing researchers as well as “retro-computing” enthusiasts.

    You Will Learn to:

    - Explore the history of technical writing in the age of the personal computer, from the 1960s to the present day
    - Understand how the technologies and tools have evolved over time
    - Learn how each tool works with simple and clear code samples and exercises, giving you an under-the-hood understanding of how each system works, from RUNOFF markup to modern Markdown

    This Book is For:
    - Technical writers, technology history enthusiasts and researchers.”

    books.google.pt/books?id=2XsAE

    #TechnicalWriting #Markup #HTML #Markdown #DITA #TechnicalCommunication #HistoryOfTechnology

  23. Just released. Judging from its Table of Contents, it promises to be very interesting in mere historical and technical terms. My suspiction is that it runs the danger of being too much enciclopedic.

    From Markup to Markdown: The Evolution of Technical Writing, Typesetting Tools and Frameworks

    Jim Hall (Apress)

    “From Markup to Markdown is a history of how writers have used computers to write, and a look ahead to see what the future looks like for technical writing. This book explores both “technology history” and “how it works” about how we write with computers, with code examples so readers can explore and fully understand how each writing tool and framework works behind the scenes.

    Starting with an overview of the major milestones of writing with digital technologies since the 1960s, you will learn about RUNOFF and how this inspired roff on Unix (and the more familiar versions, nroff and troff). You will also explore word processing milestones like WordStar, and printing technologies like the phototypesetter and the dot matrix printer, before moving onto modern markup and writing systems like HTML, Markdown and DITA and how they play a role in how we write today.

    From Markup to Markdown is ideal for writers, technical communication professionals, history of computing researchers as well as “retro-computing” enthusiasts.

    You Will Learn to:

    - Explore the history of technical writing in the age of the personal computer, from the 1960s to the present day
    - Understand how the technologies and tools have evolved over time
    - Learn how each tool works with simple and clear code samples and exercises, giving you an under-the-hood understanding of how each system works, from RUNOFF markup to modern Markdown

    This Book is For:
    - Technical writers, technology history enthusiasts and researchers.”

    books.google.pt/books?id=2XsAE

    #TechnicalWriting #Markup #HTML #Markdown #DITA #TechnicalCommunication #HistoryOfTechnology

  24. ‹math›

    The top-level element in MathML. It is used to embed mathematical formulas in HTML documents.

    developer.mozilla.org/en-US/do

    #HTML #WebDev #DailyHTML

  25. ‹math›

    The top-level element in MathML. It is used to embed mathematical formulas in HTML documents.

    developer.mozilla.org/en-US/do

    #HTML #WebDev #DailyHTML

  26. RE: social.lol/@db/117075430558062

    I consider the job of a #CMS as outputting content only - not code. When I build in #WordPress I don't allow it to output any #HTML or #CSS - everything is written by my hand.

    It's why I prefer doing a hybrid builder approach - giving the client enough freedom to build their own pages, but controlling the output and locking in the design.

    I have a whole write-up on this process at amberweinberg.com/building-mod if anyone's interested in learning more.

    #frontend #webdev #wp #semantics