home.social

#javascriptfree — Public Fediverse posts

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

fetched live
  1. Ah, the noble quest for JavaScript-free (X)HTML includes—because who needs modern conveniences when you can party like it's 1999? 🎉 Meanwhile, GitHub’s on a mission to make AI do everything except make your coffee ☕. Enjoy navigating their labyrinthine menus while pondering the true meaning of progress. 🚀
    github.com/Evidlo/xsl-website #JavaScriptFree #AIRevolution #GitHubJourney #NostalgiaTech #ProgressParadox #HackerNews #ngated

  2. ✨ Dive into the magical world of "CSS Minecraft" where JavaScript is as unnecessary as a manual for a spoon. 🚀 Just close all other tabs, upgrade your browser to the latest bleeding-edge version, and watch as your computer struggles to render a pixelated masterpiece. 😂 Spoiler alert: it's like watching paint dry, but with more CSS.
    benjaminaster.com/css-minecraf #CSSMinecraft #JavaScriptFree #BrowserUpgrade #PixelArt #Adventure #HackerNews #ngated

  3. CW: New minimal FosseryWeb (post 2/2)

    However, I have another plan, which isn't this hard to implement, and I already planned it independently from the one mentioned above: I'll make an HTML-CSS-only site, with a more minimalistic UI, which can be displayed correctly even in browsers with limited HTML/CSS support, especially targeted to Dillo and NetSurf users (the original site is broken in these browsers), but of course they will work in all other browsers (including Ladybird, Servo, Pale Moon and Otter in which the original site also has some minor issues). The new site will also be hosted on Codeberg, like the original one, so it wouldn't be any worse from a privacy perspective. The only downside will be, that it won't include all features, because some content like the utilities can't be implemented with HTML and CSS only. Quizzes could be done with HTML and CSS, but they would require advanced CSS features which aren't supported by Dillo and NetSurf, so I'll leave those out too. What I'll include are the articles, programming cheatsheets and an about page for now.
    More details, sample design coming in a few days.

    As for the original site, I originally wanted to discontinue it, but since I don't do the Java stuff anymore, and the new minimal version won't include every content, I'll continue to maintain the original one too. It won't receive many updates until I "finish" the new minimal one, but after that, I have quite a few plans for that too (see Issues tab of repo: codeberg.org/fosseryweb/pages/ ).

    #JavaScriptFree #MinimalWebsite #Lightweight #LightweightWebsite #Minimal #WebDev #WebDevelopment #Website #Dillo #NetSurf #FosseryWeb #FosseryTech

  4. CW: JavaScript-free FosseryWeb cancelled (post 1/2)

    After getting overwhelmed by the amount of problems with the new Java+Spring-based, JavaScript-free FosseryWeb project, then taking one week break, I realized that it simply doesn't worth the effort, since I only found one suitable hosting service, Alwaysdata, but it doesn't have the best privacy policy, I thought about addressing this issue, by offering an option to "self host" the site by cloning the repo, and running the Java project with Maven (Java's build system), but seeing how much issues it can potentially have, it probably wouldn't be a good solution (unless I had some really deep knowledge about Java and Maven, which I don't, nor do I have the time and energy to provide support for those who want to "self host" the site but run into issues), and making a JavaScript-free site hosted on a not too privacy respecting platform seems kinda pointless this way. (And yes, there's also Gradle instead of Maven, I tried that too, but there can be just as many issues.)

    However, I have another plan...
    See comment

    #JavaScriptFree #WebDev #WebDevelopment #Website #FosseryWeb #FosseryTech

  5. CW: FosseryWeb going fully JavaScript-free! (Post 1/4)

    Based on some feedback and concerns about the usage of JavaScript on websites, my temporary solution to address the concerns was to be more open about the JavaScript usage on FosseryWeb, label the content for which it's needed, make some parts of the website JavaScript-free (where it was possible without rewriting the whole site). But now I decided to rewrite the site with another tech stack. I considered Python + Django and Java + Spring, but I decided to go with the latter, because Python is a bit controversial, many say it's "slow" and "bloated", so I guess Java will be a better choice. But unfortunately, to make this move, another hosting service is needed, since Codeberg Pages only supports the traditional HTML/CSS/JS stack.

    CRITERIA I CONSIDERED FOR CHOOSING A HOSTING SERVICE

    - it needs to be FOSS (because of my own "rule" to only use FOSS software/services)
    - don't need my own server to host it (I know that would be the best option, but unfortunately I can't afford it currently)
    - has a free plan with at least a few hundred MB of storage
    - doesn't require an external service (GitHub, Google, Microsoft, GitLab, BitBucket, whatever) for signing up
    - doesn't ask for any phone number or home address for signing up (and accepts SimpleLogin alias for email)
    - has a decent privacy policy (doesn't sell data, or share it with anyone without a good reason)

    After a relatively long research, I only found one service which fits all the criteria: Alwaysdata (I know, its name is a bit sus lol). It gives 100MB storage for free by default, but there's a 10GB free plan for FOSS projects, I emailed to apply for than plan, and my application was accepted, so now there will be a lot of room for the site to grow.

    #WebDev #FosseryWeb #Website #OpenSource #FOSS #JSFree #JavaScriptFree #WebDevelopment #FosseryTech

  6. @dsfgs @clacke Mastodon and Pleroma have a #JavascriptFree interface available in the form of #Brutaldon - I use it with Lynx.
  7. @clacke
    Yes, #JavascriptFree rendering for #Pleroma and #Mastodon would be great.

    Before we stopped using #Fakebook, we noticed how they handled #serverSide rendering. Basically a #pagination system. To react in anyway different to simply 'Like', the user would be directed to another page for more options. The buttons were Like, React (for a new page with 'Haha', 'Sad' etc), Comment and Share.

    Is #WebAssembly (wasm) used for anything in masto? If you switch off wasm do things work the same?

  8. @Chamaeleon mi sa che ti sbagli #mastodon di base non è #javascriptfree ma puoi usare una #interfaccia web javascript free, la mia favorita è #brutaldon un’interfaccia brutalista senza javascript e fronzoli tanto che puoi usare Mastodon anche da un browser testuale come #lynx

    brutaldon.online/

    Ce ne sono altre ma questa è quella che ho usato di più e sembra la migliore, funziona perfettamente anche su Lynx, più di così 😄

  9. The 1 reason why I don't make websites with #Angular, #React, or any other front-end data-loading framework, is that they completely and utterly fail at #accessibility and #usability for the #JavascriptFree, and most of the time fail at #security and #privacy for the #JavascriptSufferers.

    #Javascript is a great language and a great tool. Stop abusing it.

  10. And this is why you should browse free from #javascript most of the time, unless you have determined the site's safety and trustworthiness.

    #JavascriptFree #Security #Privacy #Antivirus

  11. Hey, @nextcloud: thank you for increasing the #accessibility on your website by not only making most functionality available to the #JavascriptFree, and for displaying a note that indicates more functionality can be had by activating #Javascript.

    Could you ask your #webdevs to make that note stop blocking up valuable screen space? See screen shot. Android 7.

  12. Unfortunately, the birdsite's #mobile website will also detect that you enforce #pricacy and #security regulations by running #javascriptFree. And it, too, will ask you whether you would like to visit their #legacy web site.

    So you press Yes.

    And nothing seems to happen.

    Why?

    Because #Twitter #webdevs chose to save your preference in a #cookie in your browser. So you have to allow 1st-party cookies.

    #Twitter needs to inform us about that on those redirect pages. #UX #UserExperience