TeddE

Fair. Thanks for indulging my FLOSS plug then. Beatbump sounds nice though.

There's a workaround for this issue.

1. Go to https://open.audio/ or https://funkwhale.audio/#get-started
2. Register for an account.
3. Enjoy over 30k hours of creative commons music, freely shared.

FunkWhale is another decentralized service like Lemmy or Mastodon. (It also runs on ActivityPub under the hood.) Most of the publicly available pods only share creative commons material, simply because it's the easiest to share, but artists can share under whatever license works for them.

If you're technically inclined, you can run your own pod and load whatever music you own onto it, and share it with others (I presume you'll take care not to share beyond whatever license you have permits). Pods sharing pirated music exist, and they obviously should be avoided. Even if you're not technically inclined, many pods allow you to upload some amount of music, you'll want to double check the server's rules to determine if that can be used for your personal library.

You can power the device off by holding power for 12. (I always do 30s when hard booting any device, just to be sure)

You can get into recovery mode by powering on holding volume up while pressing the power button. You're welcome to look around, but I don't think you'll be able to fix it from here alone, but at least this way you'll know the hardware is functioning fine.

Others might have a few things to try next, but if all else fails, these instructions could help install a fresh copy of SteamOS: https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3

I was thinking about some kind of grouping system or hierarchy, but to be blunt the post was running long as-is.

I figured it would be cool for some communities if posts could be tagged with copyright details, particularly if the community focuses on copyleft. For exampe, a community for sharing background images, could have a post from a poser who has an an anticorporate "Share and Share alike" type vibe:

• Resolution/800x600 - tags for common resolutions
• License/CC BY-NC-SA 4.0 - would imply that the linked content was licensed Creative Commons "Attribution-NonCommercial-ShareAlike 4.0 International"
• CW/Boobs - Implies that this might be NSFW if your workplace doesn't approve of boobs.
• Animal/Mouse - The post contains an image of a mouse

The post could be linked to a Pixelfed, Imjur, Flicr, or other reasonable picture hosting site. The community's AutoMod could load the link in the post and scrape for licensing indicators (based on the hosting site) and either block the post, flag it for manual, or whatever if it suspects there's a mismatch. ditto for verifying that the image is the correct resolution. Maybe posts that don't please the AutoMod are delayed by some amount of time (where the mods can review them if they wish, but after an hour or so would get posted.

The mods would never have to worry about the resolution tags, the AutoMod bot would take care of that automagically (if mods can modify tags, maybe AutoMod could correct the resolution tag based on the scraped image and even if it were done wrong, it probably wouldn't be a huge issue unless it were egregiously wrong). If foul play were suspected regarding licensing (i.e. maybe that risque cartoon mouse from Steamboat Willie isn't the author's original work to republish as creative commons) it would have to be handled by regular moderation techniques, & that's no worse than what we had to begin with.

The CW/Boobs and `Animal/Mouse tags don't do anything at all with the Mods or AutoMod, but the Animal tag would show up after the post title, and based on the user's preferences, the user's app (or the main website) would blur the image by default due to the boobs.

In other words, a post to the community 'Indie Anime Wallpapers' by a patreon-funded artist could post their latest work "Sticking it to the Mouse" would look better titled as: "Sticking it to the Mouse" Mouse, 800x600, Boobs, than if it had the old school title "[F][Mouse]Sticking it to the Mouse[800x600][CC]"

Both contribute to community discussion

How would you tag your Dickcissel and your Great Tit going after an Antarctic Shag and an Invisible Rail? Do we want our Flying Steamer Duck having fun with a Fluffy-backed Tit-Babbler?

Honestly, I say we ditch NSFW as a on/off switch and go with a mandatory tagging system. We can clarify NSFW into content warning tags, e.g. CW - Gore, CW - Death, CW - Breast, CW - Genitalia.

Users could then set their own preferences on which tags would cause a post to be masked or simply hidden.

But why stop there? Tags could be very useful in our federated environment to help communities mesh better with each other.

Communities could be able to specify a list of mandatory tags, i.e. the Swallow community could require posts specify African Swallow or European Swallow (or both or neither). Communities could also make some tags implied, so the AfricanSwallow community might just imply that posts are Africian Swallow unless user changes it.

Underneath the hood, all tags are just treated as part of the post text, so the backend performance impact will be minimal. However moderation tools would be able to consider tags when deciding how to handle a post.

Of course, the server/instance owner can then simply make a policy of what kinds of content warnings they require, and communities can then build other tags on that to meet their community needs.

I recommend free and open source software for everyone. Everything on this list is curated to feature the best alternatives to common proprietary software (according to Linux Cafe):

https://gitlab.com/linuxcafefederation/awesome-alternatives/-/blob/master/README.md

This list is good free, open source (FOSS) Android keyboards:

https://github.com/offa/android-foss#-keyboard

I think the best two are Simple Keyboard and AnySoftKeyboard. Simple Keyboard is pleasant to use, but is missing a several advanced features. ASK would be perfect if the swipe typing worked (it's currently listed as beta, and is mostly actuate, but unfortunately when it does make a mistake fixing it is almost painful).

Finally, try to get comfortable going to alternativeto.net when you get frustrated with software. Worst case scenario you get frustrated with different software for a bit and switch back. Of course it notes the price and license model for each alternative.

https://opencollective.com/

Instructions unclear. How many teen boys are we supposed to start violence with?

That seems to be the message everyone is drawing from this.

I think it'll be more insidious than that, there will be Linux, but only "signed, verified" Linux will be allowed, and the only Linux distributions that will make that list are the ones with corporate or government versions. Specifically distributions like Google's Android, IBM's Red Hat, Canonical's Ubuntu, and China's Kylin.

This is still as horrible. Imagine Ubuntu winning the snap vs flatpack exchange, because their OS is 'legit', whereas every other distro is pushed out, because it's too much work to install an unsigned OS.

Basically by allowing websites to refuse to load unless the browser the operating system running the browser promises that the user isn't allowed to know what the computer is doing. And Google super duper promises this won't be used for evil.

https://arstechnica.com/gadgets/2023/07/googles-web-integrity-api-sounds-like-drm-for-the-web/