snabelen.no er en av mange uavhengige Mastodon-servere du kan bruke for å delta i det desentraliserte sosiale nettet.
Ein norsk heimstad for den desentraliserte mikroblogge-plattformen.

Administrert av:

Serverstatistikk:

383
aktive brukere

#bloatware

0 innlegg0 deltakere0 innlegg i dag
Replied in thread

@nitot @bortzmeyer

C'est pas le code le plus ancien qui pose le plus de problèmes... il était optimisé pour fonctionner correctement avec des ressources bien moindres qu'aujourd'hui ;)

Le sujet #bloatware ne me semble en effet pas assez étudié. On a favorisé l'écriture rapide de code, toujours plus de code, donc la quantité au détriment de la qualité.

Perte aussi de connaissance du fonctionnement des machines (et couches basses OS) à cause de couches d'abstraction qui s'empilent...

Fortsettelse av samtale

We have @EUCommission [rightfully!] crack down on #cars and their #emissions by demanding ever lower #FleetEmissions and #FuelConsumption numbers but still accept #Bloatware like shitty #WebApps and #Windows11 to demand so much #WastefulComputing that it's painful.

  • Margaret Hammond and Grace Hopper must be rotating in their graves, pointing out how they got people on the moon with less storage than the SPD-ROM on a RAM stick and how their programming language still runs #TradFinance like a clockwork respectably, but somehow sending text messages is too much for a machine that costs €499 yet has more computational power than all the machines they worked on combined.

#WastefulComputing like all those phat & enshittified messengers should be illegal.

  • Espechally since they have 0 reason to be that resource intensive, even if we believe some of their security-focussed marketing lies.
Infosec.SpaceKevin Karhan :verified: (@kkarhan@infosec.space)For those who don't know the [size of the problem]( https://infosec.space/@kkarhan/114862595629371002): In 2006 I bought a new [entry level] Computer with 256 MB of RAM and a single-core P4 Celeron with 2,8 GHz. - This thing ran #WindowsXP and #NeedForSpeedMostWanted just fine. - Nowadays it would crash trying to open #Slack even on a minimalist #Linux distro like @bunsenlabs@linuxrocks.online in @dillo@fosstodon.org, a lightweight browser ... And now imagine that some folks have to use #Slack, #MicrosoftTeams, #Telegram, #Signal, #WhatApp, #WeChat, #QQ and #LineMessenger *at the same time on their machine*, and you can imagine that this will make entry-level desktops already scream harder than if someone were to loop the *Lost Coast benchmark* on them... - The #bloat of modern #WebApps is just the *socially accepted equivalent* to #Cryptojacking desktops and driving some [*phat](https://en.wikipedia.org/wiki/Humvee) #SuperUselessVehicle just to get less than a kg of groceries at a walking distance supermarket. Everywhere else we'd not accept such a #bloatware IRL. - So why should we accept #obscene|ly #WastefulComputing*?
Fortsettelse av samtale

For those who don't know the size of the problem:

In 2006 I bought a new [entry level] Computer with 256 MB of RAM and a single-core P4 Celeron with 2,8 GHz.

And now imagine that some folks have to use #Slack, #MicrosoftTeams, #Telegram, #Signal, #WhatApp, #WeChat, #QQ and #LineMessenger at the same time on their machine, and you can imagine that this will make entry-level desktops already scream harder than if someone were to loop the Lost Coast benchmark on them...

Everywhere else we'd not accept such a #bloatware IRL.

Infosec.SpaceKevin Karhan :verified: (@kkarhan@infosec.space)One thing that really pisses me off personally is the #regression in terms of #Messenger #Apps. My personal distaste and dislike for #proprietary, #SingleVendor & #SingleProvider #services like #Signal [¹](https://infosec.space/@kkarhan/114234551915193036) [²](https://infosec.space/@kkarhan/114935952643402592), #Telegram, #Discord [³](https://infosec.space/@kkarhan/114865723904157014), #WhatsApp [⁴](https://infosec.space/@kkarhan/114873895410403238), #Slack, #MicrosoftTeams, etc. aside: - *WHY* is there no #CrossProvider #Messenger to handle that shite? - *WHY* does everyone of these shitty providers think people want to download their #bloated #WebApp that takes up triple digit Megabytes if not entire Gigabytes and will gobble up all the #RAM and #CPU each of them can?? This problem ain't new and *already got [solved for corporate social media](https://infosec.space/@kkarhan/114862619013462466) ages ago!* (Not to mention actually good messengers!) - And no, [bridges](https://toots.ch/@dalai/114862754556459439) *[don't](https://swecyb.com/@troed/114862774972645542) count*! - I mean `API 0` - [style](https://digipres.club/@foone/112685423773959519) access because obviously [none of the platforms](https://digipres.club/@foone/112685414638522984) will *allow, endorse or support such an endeavour* and [*actively fight the developers and users*](https://digipres.club/@foone/112685441496803574) ! So yeah, consider this a call for a @gajim@fosstodon.org / #Gajim or @pidgin@fosstodon.org / #Pidgin *for garbage platforms!* - Cuz back in the day we had *way worse messengers* yet people actually made #AIM, #ICQ, #MSN, #QQ, #IRC & #XMPP work just fine from one single *"phat" client*! - Can we please get that back? #api0 #Enshittification

Nobody: "How much bullshit can we shove into our website?"

#deel: YES!

And that's just the crap that #uBlockOrigin and # caught:

deel.com
api.deel.com
app.deel.com
amazonaws.com
a569f72b706584c51b5f33f0e47ccd30-e12968bbf00b014c.elb.eu-west-1.amazonaws.com
wiki.deel.network
braze.com
sdk.iad-06.braze.com
cal.com
app.cal.com
calendly.com
assets.calendly.com
chilipiper.com
js.chilipiper.com
com.cdn.cloudflare.net
api.deel.com.cdn.cloudflare.net
api.deel.com
d20qeu5vw8i5t2.cloudfront.net
cdn.zapier.com
d3kz3mviooatoq.cloudfront.net
avatars.slack-edge.com
deel.network
wiki.deel.network
deel.tools
openreplay-new.deel.tools
google.com
apis.google.com
www.google.com
googletagmanager.com
www.googletagmanager.com
gstatic.com
fonts.gstatic.com
www.gstatic.com
k8s-openrepl-awsalbin-ed4c403a34-602701419.eu-west-1.elb.amazonaws.com
openreplay-new.deel.tools
letsdeel.com
media.letsdeel.com
s3.amazonaws.com
sammylabs.com
api.sammylabs.com
sentry.io
o265775.ingest.sentry.io
slack-edge.com
avatars.slack-edge.com
stripe.com
js.stripe.com
m.stripe.com
q.stripe.com
stripe.network
m.stripe.network
stripecdn.map.fastly.net
m.stripe.network
zapier.com
cdn.zapier.com
 …deel.com
…braze.com
…cal.com
…calendly.com
…chilipiper.com
…deel.network
…deel.tools
…google.com
…googletagmanager.com
…gstatic.com
…s3.amazonaws.com
…sammylabs.com
…stripe.com
…stripe.network
…zapier.com

Seriously, I get that not everyone is able to do #accessible and #performant #forms and #Websites and that #JavaScript is trendy and hip.

  • But this seriously isn't funny, but insulting.

For any #MTCP, #DOS and #Retrocomputing nerds out there who are also running httpserv and want pretty graphs, poke me for a recipe for a hideosly bloated #logstash configuration to ingest the UDP logs.

I feed it to #Graylog which stores the data in #Opensearch - a pipeline that combined (and this is accurate) needs, conservatively, 4096 times as much RAM as the floppy museum itself (8MB).

And while looking at this when making this screenshot: I wonder why someone would hit http//floppy.museum with a Referer-header indicating they come from a salesforce-dot-com address? http-colon-slashslash-136.146.46.127 (about halfway down the list).

#Rooting a new #Xiaomi device is getting totally ridiculous these days.

I already jumped through the hoop to "request bootloader unlock permission" in one of Xiaomi's #bloatware apps at **EXACTLY** midnight beijing time, at least this worked. Now the second step would be to actually unlock the boot loader. On #FreeBSD, I can't use Xiaomi's unlocker tool (but I guess that's actually a good thing), so I found some python script that also works (after a bit of fiddling with it, patching shebang and removing some nonsense), and see what it tells me now.

Xiaomi, you used to be cool, a long time ago... 🙄

Factors:
1. Accessibility. Not everyone has really fast (or stable) internet.
2. Environmental. There's no reason to use more computing power than necessary for the task at hand. It's wasteful. Very few people
need the fancy features advanced text editors introduce.
3. Interoperability. Text files I write and send are readable *everywhere.* Try loading up Google Docs on a 1024x768 screen with a 256MB RAM Pentium 3. You'll be lucky if Google Docs even loads.
4. Privacy. A text file is easy to protect. GPG is the most straightforward. It remains small, and there's no way middle-men can read it. Google Docs? Google has root and they're not encrypted from them. So, good luck.
5. Account requirements. Text files require no accounts anywhere. All you need it an Internet connection and a DNS server that'll point your computer the right way. SaaS requires that you also have up-to-date software, a powerful computer, and that you register an account with them to access files shared with you.
6. Storage space. A text file takes kilobytes. A .docx file takes megabytes. My daily journal, which granted has some meta-data but
is still plain text, is nearing on 580kb after three years of diligent, detailed journaling. I can't help but doubt that Word would even open a .docx file that large if formatted natively. (Thousands of headings, links, timestamps, etc.)
6. Feature-set. Plain text lets you do enough for 99% of all tasks. Yes, it's not as pretty, but within the bounds of putting characters into a file, you have complete freedom. Proprietary services, on the other hand, have a very very rich feature-set, most of which is irrelevant for 99% of users. The drawback of this is that every user is forced to load these rarely-used functions onto their own computer when the applications load up. That's wasteful, and likely cost the world hundreds of millions in unnecessary energy expenditure already.

TL;DR: Use plain text unless you absolutely positively can't help it. It's seriously better in every way.

#plaintext #emacs #txt #notepad #bloat #bloatware #saas #googledocs #msword #microsoftword #rant

RE:
https://fed.bajsicki.com/notes/a6uy06mot0

IpseityIpseityA family instance.