toastal

That social media code forge is not the same as its underlying version control system. They are different things & we should support making folk not equate the two.

Supporting conversion with some lossy tendencies is a good idea, but maintaining compatibility will stifle innovation as al bugs & design decisions cannot be fundamentally worked around.

Adjacent, I heard folks praising Forgejo for its Actions & Microsoft GitHub compatibility, but that means you are still left with the same YAML spaghetti and its other limitations. What would have been nice is something better for CI--something that prompts the project to want to switch to get a better experience. As such, while I agree with the moral reasons to switch to non-proprietary software, the reason for switching is philosophical, not philosophical + technical. I feel being a wrapper around Git or Git compatibility will likely fall in this category rather than being more compelling.

You can only submit a site thru a megacorporate proprietary service? Why is Microsoft GitHub involved when talking about “small web”--it is the opposite of small & indie + requires ToS & privacy concerns around accounts with that service (not to mention those blocked by US sanctions).

Great start. Now can I have an account without using the Apple/Google duopoly mobile OSs (especially since Signal doesn’t support UnifiedPush to get some of the leaked metadata for notifications from Firebase, but at least the Molly fork supports this), or a desktop program that isn’t Electron, or allow decentralization? Why should I have to own a phone? Why do I need to run an entire browser for just a chat app when XMPP & Matrix do fine from web to native to TUI? When will I be able to run my own server?

The microSD doubles as a second SIM slot so no, not really. 3.5 mm jack doesn’t get in the way of anything & I use it more than 50% of my time when the screen is on so it more than makes up for the space. I don’t know many devices competing @ 157 × 68 × 8.2 mm (6.18 × 2.68 × 0.32 in) & 168 g (5.93 oz).

Additionally they threw in 2 extra side buttons that can be used for the camera but also mapped to other functions—like for me that is the push-to-talk button for Mumble.

So when the primary purpose of your blogs content is to deliver information accessibly, any user block JavaScript by default for security/privacy, any TUI browsers, & we crawlers get nothing but a blank screen—not even a noscript. You can’t convince me this is a rational usage of a technology—this is essentially static HTML. There’s a lot of justified complaints in here about how terribly limited Markdown is for creating blogs/documentation, but the solution shouldn’t be jumping to React but consider choosing something with better features & extensibility for actually writing something beyond a comment (such as reStructuredText or Asciidoctor).

inherit* from

to leave* the built-in prototypes alone

If you follow the brand fans on social medias on release, there’s always a crowd asking if they plan to bring the jack back. It could be a vocal minority, but it could very well also be your biggest brand advocate & enthusiast. When I have asked ‘tech normies’ for anecdotes, many have said they bought Bluetooth purely in the aftermath of their latest phone upgrade removing the jack & having not invested in otherwise good-quality IEMs, etc. took an opportunity to choose to get some while having complicated & mixed pros/cons for them as often pointed out here. The biggest difference was in the past, that was always a user choice to get one or the other, has now been forced into a non-choice especially in phones where the time-tested 3.5 mm audio jack is still ubiquitous in other apparatuses. …But I’m sure the phone OEMs didn’t mind the uptick in buying wireless earbud bundles for the problem they created.

Be open to #000 black tho <https://toast.al/posts/visuallayout/2023-07-06_be-open-to-bl...>

Great for all my cases where when my <cat> elements cleanly inherits from <animal>!

I could be misreading this, but it looks like this project is overriding the UA’s `querySelector` family of methods, which doesn’t quite sit right. I thought it was a best practice to level the built-in prototypes alone.

In 2024, most built-in DACs on a phone costing more than $200 new (so not picking bottom-barrel parts) is going to be of similar quality from a human-perception perspective. If anything a cheap dongle is more likely to have a PoS DAC. And even still, a lot of DACs will suffice for like an audio cast & provide a lot of convenience, but that wouldn’t prevent you from using a dongle DAC for a difference audio setting--even with the dongle’s downsides.

There are ways to wrap cables so they don’t tangle. Many IEMs & hearbuds come with a carrying case like a Bluetooth pair might (without fire hazard of batteries). Wrapping up cables ‘correctly’ plus keeping them stored tightly in a container is a recipe for no tangles. If I know you are going to moving up & down often, I opt for using my pocket DAP that can support two-way Bluetooth transmission + USB DAC so I can freely move around & unplug--but more often I just replug them into my phone or DAP when doing another task, then the plug IEMs back into my laptop or audio interface when I return.

I had used a pair of wireless earbuds for a year & I can’t tell you the number of calls I had to cancel early due to listening to music earlier & now not having enough charge. I’ve also had botched firmware upgrades & an app with trackers needed to installed just to get those updates, something analog didn’t deal with. The technology is far from the total-upgrade you are pitching--especially when all your digital apparatuses have a jack, the analog convenience of pulling the plug from one to the next without the fiddling of Bluetooth menus.

Sony’s Xperia line is some of the smallest & lightest flagship phones while having a headphone jack and a microSD slot (& can unlock unlike Zenfones) so I don’t think these are good excuses.

Shaving so low was the excuse for removing the beloved 3.5 mm headphone jack ubiquitous most portable electronic devices. I’d rather folks had room for good headphones than a screen-sized speaker.

> <link rel="stylesheet" href="https://unpkg.com/[email protected]/normalize.css">

Thanks Cloudflare

Build your own setup with Soupault! It has the Unix philosophy of piping output to CLI tools that do one thing well rather than locking you into a specific system. It helps glue together many other tools like a lightweight syntax renderer, modified date adding, aggregating the posts to create feeds, make some markup modifications, etc.

Additional suggestions outside a specific tool:

* Inevitably you will need more than base Markdown supports features, so you’ll either need to buy into a specific Markdown fork (some of which aren’t open) that won’t port to other platforms if you need to migrate, script the hell out Pandoc or some other tool creating your own fork, or you could start with a lightweight syntax like reStructuredText or AsciiDoc that have a more comprehensive base supporting 98% of your needs including proper metadata in the file, image sizes, figures, callouts/admonitions, spans with class names, definition lists, details/summary, footnotes, citing blockquotes; building these ad-hoc will suck to maintain & could output bad semantic markup making it difficult for screen readers, TUI browsers, web crawlers to parse & understand

* Don’t do syntax highlighting on the client side for a static site (e.g. no highlight.js or similar)

* Don’t touch the base user font size for a blog as users should be able to override font size for their accessibility (e.g. no body { font-size: 14px })

* Add an Atom and/or RSS feed

There’s been a Python issue tho where 2.x has been where a lot of apps are but is based on a 2016 version of Fx. A lot of services probably forgot that they supported KaiOS & when they heard 3.x, despite the upgrade process not being too bad, a lot of apps dropped out support for the platform. The 3.x devices are also much more difficult to root/mod which removes the cool hacker scene of 2.x or Linux/Android.

An alternative on Android is to hide the app from the drawer. If you have to dig thru Settings > Apps > ProprietaryTimeWaster, you will find you only use it when you really need to. That’s how I basically stopped using Facebook a few years back.

SMS is insecure so it’s smart to not use it. The dumbphone OSs aren’t as open as I would like to see otherwise an XMPP and/or Matrix client should have anyone covered while giving them a secure & federated/self-hostable communication option without the corporate lock-in/spying/giving data to the feds.

I used to test out sites on Dillo a lot to see if the experience was absolutely broken, but Dillo got too rusty so I went to checking Netsurf, w3m & elinks--so a revival is encouraging, especially for underpowered systems. Shame to see a project moving from a self-hosted Mercurial repository to a US-megacorparate-owned Git repository in Microsoft GitHub. …But at least the maintainer is committed to accepting email patches so folks aren’t required to create accounts / accept ToS with them.

Thanks. I can think about some of these topics but I can’t use hyprland because there is no color management in Wayland :\

Hyperlinks to scripts? I’ve been wanting to do something similar for ages for those few occasions where ambient sunlight really wanted me moving to something that wasn’t a dark. It seemed like quite a bit of work since, like you, more often than not, I’m not in that sort of environment.

You can also turn way down the brightness & save even more power if #000 & #fff are used to get a low contrast. Seems folks forget about this adjustment as anyone using a low-contrast theme for their site makes me crank up my brightness just to read it. Books being high contrast black & white wasn’t an issue since it’s in ambient light, but if your screen is brighter than ambient, then of course you’ll want a low-contrast theme, but you could have just lowered your brightness.

I’m happy with my OLED phone, laptop, & monitor while not having daily driven a IPS device in 5 years.

> PS: If you don't have an OLED screen, don't comment out autocmd ColorScheme * call OLED_Black() around line 1162. Instead, go buy an OLED screen! It's really worth it!!

Interesting truth. Vivid colors, best response time, saves power in dark mode, #000 looks amazing (and off-black looks muddied). Honestly I wish we normalized true black themes for this reason.

Which if true is still a burden that prevents simple self-hosting. You can (& I did briefly) install an XMPP server on a 10-year-old smart phone with postmarketOS on your network & have a reasonable experience.

It’s not decentralized so somebody’s server has to take the hit even if the protocol is about as barebones as it gets. You’re also missing some basic features like usernames & rooms having collisions—heck usernames & rooms can’t even contain Unicode which hurts accessibility.

This is why we should be using decentralized XMPP servers to chat since they actually run on potato hardware unlike other chat options.

Could be useful in the future for sure if I ever get to a point beyond pushing “trunk” :)

…It would be great if darcs had Pijul’s channels …or Pijul’s CLI UX had parity with darcs

I’ve been moving into a self-hosted direction for a lot of my stuff as a lot of it really wasn’t being used by anyone but myself anyhow. My latest two projects are darcs on my home server using just SSH+Nginx for HTTP with an apply hook that run `nix flake check` & on the server end, a hook that runs `nix build` which not only checks the build, but also has the derivation in Nix store for me to pick up later as that server doubles as a substitutor. Collaboration can still be done via email of patches or DMing a pull request from someone else’s remote repo. It’s crazy how much we’ve been defaulting to tools that are so complicated--especially ones that require accounts to participate & have a social media features tacked on everywhere to cause the sorts of social media anxiety it does everywhere else. When the amount of collaborators is low, self-hosting is hardly a barrier that needs extra scaling.

Weird the author said email was a pain, but last patch I received it was as easy as `himalaya read --raw X | git am` to apply & pointing out that modern email clients do a bad job supporting this seems more damning of those clients than the workflow.

The day this is used widely across browsers is the day devices you own can no longer be flashed with anything other than what the OEM puts on it--even if that is outdated or buggy.