[solved] slackware media march - july 2013

Links: slackerboy install notes :: slackbuilds.org :: adobe flash 11 :: ibm bash shell tutorial

"It's rarely if ever necessary to update a good Linux installation -- the odd security update being the exception". This should and would be a true statement if it weren't for the parade of media player and media codec changes perpetrated by media providers. Over the long run, media-related updates cost us months of wasted time and effort.

An site sensitive to anything less than perfect Flash configuration is southparkstudios.com, ironically. If it indicates Flash or some other similar Flash error, where do I begin?

checking

Running Firefox 17 ESR inside a Slackware KDE desktop, look into /usr/lib64/mozilla/plugins

$ ls /usr/lib64/mozilla/plugins
libnpjp2.so
skypebuttons.so

Nope, no flashplayer installed. And if I look into "about:plugins" in my browser, I also see no flash player installed.

KDE directory gobbledy-gook

The final version of Adobe is 11.2, due to be entirely retired Jan 2014. Linux users may be forced into Chromium at that time. Lack of information is typical in the media-player realm. Meanwhile, we're supposed to install kcm_adobe_flash_player.so into a bunch of sub-directories and make soft links and so on without KDE documentation. No thanks.

libflashplayer.so [SUCCESS]

Point the browser to adobe flash 11, and download.

$ tar -xzvf install_flash_player_11_linux.x86_64.tar.gz

Download the tarball and unpack it. A file named libflashplayer.so is created. In a separate file named "usr" a lot of KDE bologna (see below) is also created. Ignore the entire "usr" folder and focus upon libflashplayer.so .

# cp libflashplayer.so /usr/lib64/mozilla/plugins/

Verify the Flash Player is active in Firefox via about:plugins. If it's not in there, create a plugins folder: /usr/lib64/firefox[version]/plugins; try that kind of thing. Done in five minutes. Go to YouTube and enjoy your bass fishing videos.

Chromium in Arch

This works, for those running Arch. Follow the instructions for installing "chromium-pepperflash-stable".

kcm_adobe_flash_player.so [FAIL]

Same as with libflashplayer.soabove, head to adobe flash 11, and download.

$ tar -xzvf install_flash_player_11_linux.x86_64.tar.gz

The unpacked folder will be a /usr folder, with subfolders, /bin, /lib, /share, and so on. Sudo-up and waste an hour transfering files into the real versions of these directories in the file system. For example

$ cd [install directory]
$ cd usr/lib64/kde4
# mkdir /usr/lib64/kde4; mkdir /usr/lib/kde4
# cp kcm_adobe_flash_player.so /usr/lib64/kde4/
# cp kcm_adobe_flash_player.so /usr/lib/kde4/
$ cd ..; cd .. ; cd bin
# cp flash-player-properties /usr/bin/
$ cd ..; cd share/applications
# cp flash-player-properties.desktop /usr/share/applications/

And so on through each directory. After these were complete:

# update-desktop-database
# update-desktop-database -q /usr/share/applications >/dev/null 2>&1
# gtk-update-icon-cache
# gtk-update-icon cache /usr/share/icons/hicolor >/dev/null 2>&1

None of this KDE sh*t worked. Suggest the easy way with libflashplayer.so or, if runninig Arch, get the pepperflash prior to Jan 2014.

Browser - Adobe Flash

Links: Slackware Flash update :: Opera plug-in page

---

Like most reasonable people, I dislike Adobe's proprietary obsfucation. It's most oppressive in the Linux environment, where its intrusive modules don't interact well with Linux's more transparent libraries.

A recent Adobe Flash update¹ screwed my Iceweasel installation and, in turn, destabilized a previously 3-years' stable Zenwalk install. That is, immediately following the update of (libflashplayer.so), including complete deletion of all prior versions, etc, the previously rock-solid Iceweasel intermittently crashed at Flash intensive sites. A new installation of FlashBlock did not stop the crashes. Reinstallation of all three applications did no better. I eventually had to move to ArchLinux from Zenwalk, due to these Adobe-related Flash crashes. In other words, I had to change my entire OS structure thanks to Adobe's closed-sourced, DRM intensive elements, which are so-far impossible for average users to ignore for a typical browsing environment.

¹Pop-up windows demanding Adobe Flash Player updates began to appear in sponsored YouTube videos December 2012. Prior to this update ads could be bypassed. Following the update, they could not.

tweet clients, drm

last update: 20200309

---

Gee, why wouldn't the Chinese want to adopt our unintrusive, unlitigious DRM/IP restrictions? Injecting an army of IP attorneys into their economy shouldn't cost much or swamp their legal system (cough).

Adobe used to purchase content creation companies (eg. Macromedia), then sell content creation software, meanwhile adding layers of DRM. This means whatever "free" player is released slows to check DRM and/or nags users for updates. Good for revenue, but a percentage of creativity is lost, at least for all of those who can't buy the Adobe software.

Unsurprisingly, TweetDeck software requires customers to sign a EULA and to install Adobe's proprietary run-time platform Adobe AIR. Adobe AIR appears to have Adobe's customary DRM layers and potential phone-homes (updates, statistics) drawbacks. To me, TweetDeck means "Twitter, now with statistical data-mining, nagware, and under-the-hood file manipulation". Extrapolating a bit, watch for Adobe to someday "partner" with Twitter or otherwise make "reliability" data-sharing agreements with Twitter. One of the simplest explanations for why DRM seems to make financial sense to companies is this article which notes how creation software helps lock non-purchasers out of the creative process. The article is from Techdirt. I emphasize "seems", because they could likely make more money if they GNU licensed, but offered paid support subscriptions.

tag hasher options
TweetDeck :: Linux version available but, as noted, requires the installation of Adobe Air runtime.

TweetGrid :: Linux compatible. Nothing to download. It appears to require that one's referrer header is set to "2" in "about:config". The developer told me this is to prevent hotlinking. I left my referrer header at "0" and installed the RefControl add-on to firefox to manage the header. This helps on other sites which require headers as well (eg. Adobe!). Appears TweetGrid searches both a tweet's text and its title.

Twitter Search :: This is a sort of rudimentary way to go about it, which is why Adobe and TweetGrid can step in, but it can find whatever I want. Apparently limits its search to tags.

video streams

As of 2020, we sometimes can use Widevine to access some DRM accounts, such as Netflix. It's a browser plugin for chromium... $ yay chromium-widevine, then activate it. The streamer can then gather as much personal and impersonal data as possible from the content viewer. The other major Silverlight clone, Pipelight, appears to operate similarly.