Don't get me wrong, It won't be hard for the big corporations or organisations. They can (probably won't, because "profits") hire artists, musicians, programmers, writers etc.. And have them produce in-house.

But imagine a small content creator or indie game developer. There are only so many hours in a day, and not everybody can do everything. You might have someone that makes documentaries about animals, they need B-roll or background music maybe even art. Its perfectly normal for both established networks and content creators to use stock images and either CC music or licenced music.

I had a look around on a few of these, they don't necessarily tag what is AI and not. For music some are clever enough to edit the meta data not always. I found a whole bunch of music that was clearly AI generated up for licencing on these sites.

Unfortunately same seems to be true for game assets. Also quite normal for indie developers to use bought assets. I mean there is a whole industry around it probably because if the game is being made by a single developer they might not have the talent or time to do, art coding, music, sound effects, animations and story. So what do they do? Probably go looking for assets. -- Are these clearly labeled? Nope, but there can be hints like an account basically spamming huge asset packs on a non human scale. Sure could be a team, could be a very prolific artist.

• Can a small actor reasonable be asked to ensure no AI in the entire chain in such a scenario?

• Would a "no AI" disclaimer ever be trustworthy unless there is proof of work?

• Is there a meaningful difference between music/art licencesed, that turns out to be AI generated and the content creator just generating it them selves?

I don't have any good answers to this. Well the last one is probably either neutral or less bad if they just generate it them selves rather that paying someone for something they would have more agency in if they just generated it them selves.

I actually think that unless we want an armsrace we need to enforce origin tags like certain produce is required to have. How one would go about implementing that I don't know. But as it is right now it will almost certainly only hurt actually artists even more if you can't even really make the choice to buy humanly-produced art or even trust that you did.

They are all over the garden.

I actually made 12 friends, all goats. But this girl was special. She enjoyed cuddles and I'm going to call her Goatrudth.

These goats are actually working they are used to keep the undergrowth from taking over a historical juniper forest. Historically farmers had animals grazing the hills here. Creating a unique landscape. The fence is to keep wolfs out and of course to keep them from wondering off.

Edit: had misspelled juniper as uniper

cross-posted from: https://lemmy.world/post/46782285

So yesterday I pulled out my old "luggable" IBM 5155 because I wanted to know if I could use it as a Terminal for a terminal.

I have previously successfully connected a Psion 5mx over a null modem to a Raspberry Pie. Figured it would be cool to see if I can get it working on this behemoth as well. I have DOS 3.3 on a 5.25" floppy and another with some supplementary software for DOS 3.3. And wow, not a lot of software included. CTTY won't let me set Baud rate, parity och bit size. So it just freezes, and the CONNECT application doesn't throw up errors either but just sort of is there, regardless of settings.

Anyway will in the future get my self a carrier card for a CF -to-IDE so I can throw DOS 6.6 and PROCOMM on it and see if that gets me anywhere. Unless any of you folks have any tips or scathing criticism on my lack of knowledge of DOS.

This is an 80s Olivetti I found in a thrift store and purchased for 10€. Its fully functioning and a pure joy to write on. Just listen to that daisywheel slapping that paper.

By chance I stubmled on this Olivetti ETP 92 in a thrift store, got it for 10€. Now I need some help, as far as I can tell this typewriter is functionally the same as the Olivetti ETP 55, from pictures and descriptions. But I can't really find any information about the ETP 92. Is it some regional naming or is it an oddity or just so not interesting enough to have much information online? Any one here know anything about this novel machine. It works perfectly and I have replacement ribbons on the way already, hopefully they fit.

Found out today when one of my cards was greyed out and I logged out and in again to reload my cards. Good thing I always have one of my physical cards with me, otherwise I would have had to construct some form of sail on my car to get home. As far as I know that was the last European, at least Swedish Wallet app that wasn't one of the tech giants Wallets. It was a good run but I'm back to plastic cards I guess. Really hoping for a European alternative to master card/visa will be revealed soon and with a digital wallet to go with it. If I'm wrong here and there is a EU based Wallet compatible with /e/OS, Android please let me know.

Hur kan man envisas med att göra på samma sätt var enda gång och förvänta sig andra resultat?

Ett uttryck jag en gång hörde från en äldre gubbe gör sig till minnes.

" Det där hade ju till och med en tjackpundare med röven full av krita kunnat räkna ut " - okänd gubbe 2010

At the time of writing this, Fluxer does not yet support streaming a game, application, or your screen with audio on Linux. This is a workaround that can be used in the meanwhile. At first glance this guide might seem lengthy, but it's actually only about 3 steps required for this workaround, the rest is explanations and sub steps to help guide those unfamiliar with audio interfaces and routing audio.

Note: This workaround requires installing a tool through the Linux terminal, although this package is available in Debian, Arch and fedora based repositories, this guide will use the Debian command apt for installation.

What we are aiming to achieve is sharing audio from a game or an application along with our mic input with others in a call. We will do this by using an application called qpwgraph. Which is a Graph manager for Pipewire. It will let us "route" inputs and outputs of different audio sources with a graphical interface. While this requires some manual labor whenever we want to stream audio while in a call, it is by far the simplest method I have found to substitute the "Sharing Audio" feature.

Note: If your system is not using Pipewire, QjackCtl is an alternative but it also requires installing the API Jackd.

First we need to install qpwgraph, so lets open up a terminal. Then type the following command into the terminal:

	sudo apt install qpwgraph

Once installed we can open the application either through our application menu or typing qpwgraph into the terminal.

What, and how many, audio interfaces you see when you first open up qpwgraph depends entirely on your hardware and system setup. Because of this, I will try and explain how you identify what is an input and what is an output source. I recommend that all software capturing or playing audio is closed when first starting qpwgraph, because then only your hardware interfaces and sources should be listed. Once you start an application that either plays or captures audio it will immediately show up in the graph editor as nodes.

Tip: You can move around the nodes to get a better more manageable view if needed.

There are different types of nodes, we have input nodes, output nodes and nodes that have both input and output. Some interfaces have multiple nodes such as most sound card. If the only sound card on your computer is the integrated speakers, headphone jack and internal mic, which is standard for most laptops, it will most likely be represented by three different nodes with differently named Input/outputs. With Capture FL, FR being the input node for your mic and Playback FL, FR being your speakers, FL and FR being your front Left and Right channels.

Note: These Input/output connection points are color coded, with green being the color for standard audio.

If we now start an application that plays audio such as Spotify, we will get an entirely new node in our graph editor called Spotify. This node will have its Output FL, FR connected to the Playback FL, FR of your "output-interface" node.

Let's say we want to stream the music playing from Spotify while talking and sharing our screen in Fluxer, all we have to do is to also route the output from Spotify to the Input FL, FR of Fluxer. Some apps can't handle multiple sources being routed to the same Input channels, and require setting up virtual audio devices that act as a middle man. Fortunately, Fluxer can handle this.

If you open Fluxer, it will show up in qpwgraph as Chromium, this is expected since its a webapp. All we need to do now is to click the output connections on Spotify and connect them to the input connections on the Chromium node.

If you want to break the connection between two nodes simply select it by left clicking the green line connecting the two and then right click and choose disconnect.

Reference image below using an external sound card connected as default input device, and Spotify connected to both standard output and Fluxer input along with external sound card on the same channels

This same operation can be performed for any app that plays sound, and qpwgraph will remember routes even if apps are closed and then opened again.

Note: Two things to remember; You will need to manually cut connections if you want to stop streaming audio along with your voice, and the other parties in your call will not be able to adjust the volume ratio between your mic and what ever audio you have routed to the Fluxer input. This is because it is now the same audio source in Fluxer so you will have to adjust the levels on your end.

cross-posted from: https://lemmy.world/post/44314509

I have been in the process of writing some help guides, and one of my friends graciously lent me his Steam Deck so that I could verify that Fluxer would work on it as well. And I'm happy to say it does. Although I did not plan on just posting a Fluxer Help-Article on Lemmy, I figured while waiting on the Fluxer team to start accepting pull requests and me getting done with my guides, someone might be looking for step-by-step instructions for their Steam Deck. So here it is. Feedback and discussion is of course welcome.

---

In this Help Article we will guide you step-by-step through the process of installing and integrating Fluxer into your application menu on the Steam Deck. Although not required, access to an external physical keyboard is recommended.

The Steam Deck is running a custom version on Linux that is based on Arch, and the CPU architecture is x86-64. This means we could either use the AppImage(x64) option or the tar.gz(x64) option from the download drop-down on https://fluxer.app/downloads

Since integrating the AppImage into the application menu requires additional steps such as manually retrieving the icon .png file this guide will focus on the installation process for the tar.gz.

Before we explain how to install Fluxer from the tar.gz file, let's take a moment and go through what a tar.gz file is. tar.gz are actually two abbreviations put together. "tar" from Tape Archive (sometimes referred to as a tarball) which is an archive file format and the "gz" at the end is short for Gzip(which in of itself is short for Gnu Zip) and it is a compression format. When combined you get an archive that is neatly packed in one file that is now also take up less space.

- Okay, why was that important to start off with?

Well, since it is a compressed archive, that means we can't just double click it and hope it will do much more than perhaps open the preinstalled unarchiver on our system. The fact is, a tar.gz file does not necessarily even have to contain any executable, even if it is an application. In this case with the Fluxer - tar.gz it does contain a executable.

Note: The steps outlined in this help article will primarily be performed using the terminal. The keyboard shortcut to open the terminal is "Ctrl + Alt + T" or you can open it from the application menu under the "system" category and it is referred to as "console".

Installing Fluxer

Let's begin by entering desktop mode on the Steam Deck. Long press the power button on the top of the Steam Deck, this should make a menu appear, from that menu choose "switch to desktop".

Then open the web browser and download the tar.gz(x64) from https://fluxer.app/download.

Once downloaded navigate to your download folder through the terminal by typing the following command:

cd ~/Downloads

Where Downloads is either the default download location, or the folder you chose to save the tar.gz file.

Tip: You can press "tab" on your keyboard to complete the file/directory name. If there are multiple files/directories with the same beginning of the filename it won't auto complete. But if you press tab again, it will show you all possibilities with the same beginning. This is referred to as "Tab Complete".

Now it is time to extract our tar.gz we can do this by using the tar command. Type the following command into the terminal:

tar -xzf fluxer-stable-0.0.8-x64.tar.gz

Tip: The options x, z, f stand for extract, decompress gzip, and specify the file. "Specify the file" might seem a bit cryptic, but remember tar is as old as tape drives. In essence the "f" option just says, what comes next is the filename.

You could run Fluxer here and now, cd into the directory we just extracted and then type the following command in the terminal:

./fluxer

But lets install it properly. Because right now, Fluxer only works if you navigate to its folder and run it manually from the terminal. If we move it to a standard system location and create a desktop entry, we will integrate it with your system. This means Fluxer will appear in your application menu, and you can launch it like any other installed program.

Note: make sure you are located inside the fluxer-stable-0.0.8-x64 folder for the next step. Use the cd command followed by the folder name if needed.

Next we need to create two directories, copy the Fluxer files and make a symbolic link to the executable that can later be used by the application menu to launch Fluxer.

Type the following commands into the terminal:

mkdir -p ~/.local/share/fluxer cp -r * ~/.local/share/fluxer/ mkdir -p ~/.local/bin ln -s ~/.local/share/fluxer/fluxer ~/.local/bin/fluxer

Each line followed by return or enter.

Now that the Fluxer has been installed we want to have it appear in our application menu, to achieve this we need to let the system know where to find it. Lets begin by creating a .desktop file with the Nano editor in the terminal.

Type the following command into the terminal:

nano ~/.local/share/applications/fluxer.desktop

Write the following into the file.

[Desktop Entry]
Name=Fluxer
Exec=/home/USERNAME/.local/share/fluxer/fluxer
Icon=/home/USERNAME/.local/share/fluxer/resources/512x512.png
Type=Application
Categories=Network;Chat;

Note: Change "USERNAME" to your username

Once done; press Ctrl + O to write out (functionally the same as Save), then Ctrl + X to exit Nano.

And now lets validate the .desktop file, by typing the following command into the terminal:

desktop-file-validate ~/.local/share/applications/fluxer.desktop

If this returns no errors we can continue and make our .desktop file executable

Type the following command into the terminal:

chmod +x ~/.local/share/applications/fluxer.desktop

And lastly lets update the desktop database. Type the following command into the terminal:

update-desktop-database ~/.local/share/applications/

You will now be able to access Fluxer through your application menu and it will sit in the correct category.

Note: Fluxer will not run properly if added to your steam library as a non steam game on the Steam Deck and launched from within game mode. - This is no longer true

Edit: After some troubleshooting I realized that there seemed to be an issue with the sandboxing and steam wanting to run the app in 32-bit environment.

Solution: All that should be required to solve the situation is to add env -u LD_PRELOAD %command% to the launch option in properties for Fluxer in steam. I did how ever first try and fix the sandboxing issue so if for you the issue persists after adding the launch options. cd into ~/.local/share/fluxer and run the following two commands in the terminal:

sudo chown root:root chrome-sandbox
sudo chmod 4755 chrome-sandbox

I have been in the process of writing some help guides, and one of my friends graciously lent me his Steam Deck so that I could verify that Fluxer would work on it as well. And I'm happy to say it does. Although I did not plan on just posting a Fluxer Help-Article on Lemmy, I figured while waiting on the Fluxer team to start accepting pull requests and me getting done with my guides, someone might be looking for step-by-step instructions for their Steam Deck. So here it is. Feedback and discussion is of course welcome.

---

In this Help Article we will guide you step-by-step through the process of installing and integrating Fluxer into your application menu on the Steam Deck. Although not required, access to an external physical keyboard is recommended.

The Steam Deck is running a custom version on Linux that is based on Arch, and the CPU architecture is x86-64. This means we could either use the AppImage(x64) option or the tar.gz(x64) option from the download drop-down on https://fluxer.app/downloads

Since integrating the AppImage into the application menu requires additional steps such as manually retrieving the icon .png file this guide will focus on the installation process for the tar.gz.

Before we explain how to install Fluxer from the tar.gz file, let's take a moment and go through what a tar.gz file is. tar.gz are actually two abbreviations put together. "tar" from Tape Archive (sometimes referred to as a tarball) which is an archive file format and the "gz" at the end is short for Gzip(which in of itself is short for Gnu Zip) and it is a compression format. When combined you get an archive that is neatly packed in one file that is now also take up less space.

- Okay, why was that important to start off with?

Well, since it is a compressed archive, that means we can't just double click it and hope it will do much more than perhaps open the preinstalled unarchiver on our system. The fact is, a tar.gz file does not necessarily even have to contain any executable, even if it is an application. In this case with the Fluxer - tar.gz it does contain a executable.

Note: The steps outlined in this help article will primarily be performed using the terminal. The keyboard shortcut to open the terminal is "Ctrl + Alt + T" or you can open it from the application menu under the "system" category and it is referred to as "console".

Installing Fluxer

Let's begin by entering desktop mode on the Steam Deck. Long press the power button on the top of the Steam Deck, this should make a menu appear, from that menu choose "switch to desktop".

Then open the web browser and download the tar.gz(x64) from https://fluxer.app/download.

Once downloaded navigate to your download folder through the terminal by typing the following command:

cd ~/Downloads

Where Downloads is either the default download location, or the folder you chose to save the tar.gz file.

Tip: You can press "tab" on your keyboard to complete the file/directory name. If there are multiple files/directories with the same beginning of the filename it won't auto complete. But if you press tab again, it will show you all possibilities with the same beginning. This is referred to as "Tab Complete".

Now it is time to extract our tar.gz we can do this by using the tar command. Type the following command into the terminal:

tar -xzf fluxer-stable-0.0.8-x64.tar.gz

Tip: The options x, z, f stand for extract, decompress gzip, and specify the file. "Specify the file" might seem a bit cryptic, but remember tar is as old as tape drives. In essence the "f" option just says, what comes next is the filename.

You could run Fluxer here and now, cd into the directory we just extracted and then type the following command in the terminal:

./fluxer

But lets install it properly. Because right now, Fluxer only works if you navigate to its folder and run it manually from the terminal. If we move it to a standard system location and create a desktop entry, we will integrate it with your system. This means Fluxer will appear in your application menu, and you can launch it like any other installed program.

Note: make sure you are located inside the fluxer-stable-0.0.8-x64 folder for the next step. Use the cd command followed by the folder name if needed.

Next we need to create two directories, copy the Fluxer files and make a symbolic link to the executable that can later be used by the application menu to launch Fluxer.

Type the following commands into the terminal:

mkdir -p ~/.local/share/fluxer
cp -r * ~/.local/share/fluxer/
mkdir -p ~/.local/bin
ln -s ~/.local/share/fluxer/fluxer ~/.local/bin/fluxer

Each line followed by return or enter.

Now that the Fluxer has been installed we want to have it appear in our application menu, to achieve this we need to let the system know where to find it. Lets begin by creating a .desktop file with the Nano editor in the terminal.

Type the following command into the terminal:

nano ~/.local/share/applications/fluxer.desktop

Write the following into the file.

[Desktop Entry]
Name=Fluxer
Exec=/home/USERNAME/.local/share/fluxer/fluxer
Icon=/home/USERNAME/.local/share/fluxer/resources/512x512.png
Type=Application
Categories=Network;Chat;

Note: Change "USERNAME" to your username

Once done; press Ctrl + O to write out (functionally the same as Save), then Ctrl + X to exit Nano.

And now lets validate the .desktop file, by typing the following command into the terminal:

desktop-file-validate ~/.local/share/applications/fluxer.desktop

If this returns no errors we can continue and make our .desktop file executable

Type the following command into the terminal:

chmod +x ~/.local/share/applications/fluxer.desktop

And lastly lets update the desktop database. Type the following command into the terminal:

update-desktop-database ~/.local/share/applications/

You will now be able to access Fluxer through your application menu and it will sit in the correct category.

Note: Fluxer will not run properly if added to your steam library as a non steam game on the Steam Deck and launched from within game mode. - This is no longer true

Edit: After some troubleshooting I realized that there seemed to be an issue with the sandboxing and steam wanting to run the app in 32-bit environment.

Solution: All that should be required to solve the situation is to add env -u LD_PRELOAD %command% to the launch option in properties for Fluxer in steam. I did how ever first try and fix the sandboxing issue so if for you the issue persists after adding the launch options. cd into ~/.local/share/fluxer and run the following two commands in the terminal:

sudo chown root:root chrome-sandbox
sudo chmod 4755 chrome-sandbox