fosstulate

joined 1 year ago
[–] fosstulate@iusearchlinux.fyi 2 points 6 months ago* (last edited 6 months ago)

No one wants to scale enough to compete.

I don't consider scale important from the perspective of making and watching good videos. People get hung up on it when citing barriers to competition with Youtube, and while it's certainly there, it only matters to Google itself (so it can continue to plausibly lie to its customers about ad impression numbers). In fact YT's offering was at its creative peak when scale was lacking.

It makes no difference to me whether a knowledgeable hobbyist has 20,000 subs or 250,000. I don't care about their "content" suitability for advertisers (that creepy term can get nuked). I certainly couldn't care less whether the algorithm promotes their work, deserving as it may be. This sort of creator operates on the assumption their viewers are intelligent, and is typically savvy enough to route around YT with alternate donation/support mechanisms. These people will continue on any platform. For them, quality is an end in itself rather than a feed-in to a metric. I would rather watch a badly filmed insightful critical appraisal of a new piece of hardware than Canadian/Black Technology Man's 8K press release rehash full of slick cuts and pointless b-roll.

Scale is the concern of middlemen.

[–] fosstulate@iusearchlinux.fyi 0 points 6 months ago

The big news/current affairs instances are characterized by autistic screeching that has only a passing relevance to the article posted. See https://iusearchlinux.fyi/post/5429432

You can take the commenter out of R*ddit...

[–] fosstulate@iusearchlinux.fyi 6 points 6 months ago* (last edited 6 months ago)

Assume for a moment the platform providers are in a game of chicken, continually eating costs in the hope of soaking up subscribers from their (at some point) defunct competitors. Every year this competition continues, the victor needs to make increasingly outrageous changes to the service offering in order to bridge the profitability gap. Or perhaps they are betting that a chunk of savings will come from reduced spend on rights, in a market with fewer bidders for programming?

Are investors in the conglomerates even agitated yet?

[–] fosstulate@iusearchlinux.fyi 52 points 6 months ago (1 children)
[–] fosstulate@iusearchlinux.fyi 2 points 6 months ago* (last edited 6 months ago)
[–] fosstulate@iusearchlinux.fyi 2 points 6 months ago* (last edited 6 months ago)

This is an interesting response. It makes me wonder whether the real risk of piracy to game publishers isn't so-called 'lost' sales, but having their control of the initial impressions window undermined by genuine critical reception*. Marketing efforts are seriously compromised unless they operate in an information void. Denuvo provides that void.

[*] Video game reporting outlets not included for reasons that should be obvious in the year 2024

[–] fosstulate@iusearchlinux.fyi 4 points 6 months ago (3 children)

I need conclusive Lemmy anecdata on a key question: is Quebecois French considered antiquated by continental (both European and African) French speakers? Are the differences subtle or not?

[–] fosstulate@iusearchlinux.fyi 2 points 6 months ago* (last edited 6 months ago)

In addition to reducing the volume of waste being created

That will amount to a cynical coercion of the public in some way. I'm being forced to work for free in the form of sorting waste at point of disposal, and worrying about fines, all so that industry's line can continue going up. So that plastics production growth can largely continue on trend. Paper and plastic recycling are like cycling up the hill of environmental conservation in top gear. Loads of pedal revolutions that (ultimately) only slow the rate of decline back down the hill.

If the product has a high energy cost involved in new production, that's when industry actually does the right thing. Aluminum is a great example. Generous deposit schemes are found all over the world. They're voluntary and well managed. But paper and plastic are cheap to manufacture by comparison, and the costs can be passed through to the consumer, so industry and government conspire to do just that (the mechanisms of which are then greenwashed).

6
submitted 8 months ago* (last edited 8 months ago) by fosstulate@iusearchlinux.fyi to c/linuxquestions@lemmy.zip
 

I installed ~300 updates via Discover a couple of nights ago. I sensed something had gone amiss when Firefox both crashed and wouldn't resume after I opened a brand new session (ie. no tab reloads). I got the crash report box, then a subsequent crash.

Full reboot. Up comes the login screen. The password field cursor is unresponsive to keyboard input, and isn't blinking. The virtual keyboard button isn't responsive either, despite my having mouse movement. I then reboot, this time via recovery mode, which loads the crappy fallback graphics driver with only 1024*768 resolution available. This persists after package repair attempts and sudo apt autoremove to clear disk space. My AMDGPU drivers don't seem to be functional at all.

var/log/apt/term.log (below) reveals the latest driver versions are 24.x. Presumably these were upgraded during the update, prior to which I was on an earlier working version? That's all I can think of.

What other logs should I consult for troubleshooting? Would driver reversions work? How do I get back to a normal display? Your input is appreciated!

Preparing to unpack .../libglapi-mesa_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking libglapi-mesa:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Setting up libglapi-mesa:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...
Preparing to unpack .../libgbm-dev_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking libgbm-dev:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Preparing to unpack .../libgbm1_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking libgbm1:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Setting up libgbm1:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...
Preparing to unpack .../libegl-mesa0_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking libegl-mesa0:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Setting up libegl-mesa0:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...
Preparing to unpack .../libgl1-mesa-dri_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking libgl1-mesa-dri:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Setting up libgl1-mesa-dri:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...
Preparing to unpack .../libglx-mesa0_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking libglx-mesa0:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Setting up libglx-mesa0:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...
Preparing to unpack .../025-libegl1-mesa-dev_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking libegl1-mesa-dev:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Preparing to unpack .../048-libosmesa6_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking libosmesa6:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Preparing to unpack .../060-libxatracker2_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking libxatracker2:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Preparing to unpack .../080-mesa-va-drivers_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking mesa-va-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Preparing to unpack .../081-mesa-vdpau-drivers_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking mesa-vdpau-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Preparing to unpack .../082-mesa-vulkan-drivers_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ...
Unpacking mesa-vulkan-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ...
Preparing to unpack .../102-xserver-xorg-video-amdgpu_23.0.0+git2401241940.4d7a9a6~j~mesarc0_amd64.deb ...
Unpacking xserver-xorg-video-amdgpu (23.0.0+git2401241940.4d7a9a6~j~mesarc0) over (23.0.0+git2309251950.31a092a~j~mesarc0) ...
Setting up mesa-vulkan-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...
Setting up mesa-vdpau-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...
Setting up xserver-xorg-video-amdgpu (23.0.0+git2401241940.4d7a9a6~j~mesarc0) ...
Setting up libgbm-dev:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...
Setting up libxatracker2:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...
Setting up mesa-va-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...
Setting up libosmesa6:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...
Setting up libegl1-mesa-dev:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ...

Further info

  • KDE neon 5.27, dual boot
  • Kernel 6.5.0
  • X11
  • GPU R9 390, single monitor setup
view more: next ›