toastal

joined 4 years ago
[–] toastal@lemmy.ml 3 points 17 hours ago (1 children)

One day they will wake up & provide an OLED option with 100% DCI-P3

[–] toastal@lemmy.ml 16 points 18 hours ago

Y’all. Nostalgia is a strong drug, but we all gotta move past Nintendo with its years of behavior like this. Support indies.

[–] toastal@lemmy.ml 3 points 1 day ago

You mean lost features? Remember when headphone jacks, microSD, & dual SIM were normal?

[–] toastal@lemmy.ml 2 points 2 days ago* (last edited 2 days ago)

LibreWolf on desktop—fennec on mobile (tho I should consider Mull, my history is already in Fennec). Back desktop is Brave—with backup mobile being Mulch + Fx Android Beta (to handle DRM). In the terminal, w3m picking up a new possible maintainer means it will stay my favorite.

I want to follow Ladybird, but man is that hype way overblown relative to where the project actually is & you should not trust leadership that locks communications to US-based, proprietary services (Discord + Microsoft GitHub).

[–] toastal@lemmy.ml 1 points 3 days ago

I wish more things used Nickel or Dhall for config. I don’t know why I wouldn’t want editor support for type information or the ability to make functions in my non-Turing-complete config to eliminate boilerplate on my end.

[–] toastal@lemmy.ml 1 points 4 days ago* (last edited 3 days ago)

I mean we have a generation that thinks XML is bloated & JSON is superior but those two formats are about the same on performance & compressed size--which was the point. The non-plaintext-readable formats are superior along a lot of metrics but harder to debug & ultimately less common.

[–] toastal@lemmy.ml 5 points 4 days ago (2 children)

Balisage Paper: Fat Markup: Trimming the Fat Markup Myth one calorie at a time

https://www.balisage.net/Proceedings/vol10/html/Lee01/BalisageVol10-Lee01.html

XML is a fine format in comparison to JSON.

[–] toastal@lemmy.ml 1 points 4 days ago

This project makes it so much less painful to get microG up & running. It all just works. If only they were the default for these unofficial LineageOS builds as it would seem like the tinkering types are more likely to be interested in takinga privacy step with microG than those that want Google Play.

[–] toastal@lemmy.ml 3 points 4 days ago

Missing from the list: ASUS lost a lawsuit in the UK after lying about saying their unlock servers being down would come back up for Zenfones. While they have a headphone jack, offer good price/performance, & used to fall in the ‘small phone’ category, you can no longer unlock bootloaders with final statement being they won’t be allowing it going forward.

(I would contribute to the upstream, but I only use proprietary Microsoft GitHub when absolutely required—keep this in mind Privacy fam when setting up any unmirrored Git repository)

[–] toastal@lemmy.ml 1 points 4 days ago (1 children)

I want to support the Linux phones, but I feel you would still be required to carry a second Android phone one way or another with just enough things in life unfortunately requiring ‘the app’ with no web alternative. This isn’t really something you can overcome without reverse engineering entire apps—which usually violates some stupid ToS that gets your account banned for using an alternative client. That said, the more these exact apps are requiring no root, no flashing, no unlocked bootloader, the closer we are getting to needing a separate device anyhow. Maybe my next phone will be Linux 🤔

[–] toastal@lemmy.ml 3 points 4 days ago (1 children)

5a was the last version with a headphone jack, so they lost my respect

[–] toastal@lemmy.ml 2 points 5 days ago

I would just add a +1 for Sony Xperia phones with LineageOS support (do check). They offer OLED panels, a 3.5mm headphone jack, & microSD card—with the last two once being standard now almost impossible to find despite their usefulness.

As for services, many of them can be accessed thru a browser. There are enough Firefox forks out there that you could stay authenticated with these grimy, untrustworthy apps & another fork with your typical web browsing.


That said some of this could be given up to an extent. If you have a microSD slot or carry a separate DAP, there shouldn’t be much need for Spotify where an offline library is quicker, saves data, & can offer higher bitrates (obv no ads too). Microsoft GitHub is not useful on a phone since no one codes on a phone & you can subscribe to the things you need either their Atom feeds or via email & all of your personal code should be living somewhere off the proprietary platform—especially if you want to help access to contributions since it is blocked for US sactions in some regions & they bow out to capitalist interests (see youtube-dl, or Switch emulators, etc.), while requiring your contributors give up their privacy as there is no way to report bugs or send patches without an account. And the chat options, depending on the situation you should see if you can get folks to consider your privacy too (else why on this sub?) & switch to something decentralized & with E2EE the default for DMs & optional for groups—XMPP is a great default choice, Mumble was built for games, but there are other options. Need is a strong word, & it might take a few years, but eventually, hopefully you can ween yourself & help friends get off these platforms as it is bad for them too, but you are not going to get much privacy if the corporations & governments can still read all your chats.

11
submitted 3 months ago* (last edited 3 months ago) by toastal@lemmy.ml to c/programmerhumor@lemmy.ml
 
1
submitted 5 months ago* (last edited 5 months ago) by toastal@lemmy.ml to c/xmpp@slrpnk.net
 

There is a little bit more than just service.movim.enable = true; but it’s not far off. For those looking to a Docker alternative & reproducible/declarative builds, this could be quite useful.

0
submitted 9 months ago* (last edited 9 months ago) by toastal@lemmy.ml to c/technology@lemmy.ml
 

A quick primer on XMPP & how/why you should host your own server for low-resource-usage, encrypted chat & other pubsub server.

view more: next ›