RootBeerGuy

joined 1 year ago
[–] [email protected] 19 points 2 hours ago (1 children)

"After it became known that the company was involved in forced prison labor, IKEA accepted our invitation to talk."

So from the sound of it IKEA didn't give two shits as long as no one knew, just like any other big company. You cannot tell me that people at IKEA simply didn't know, someone knew.

[–] [email protected] 2 points 7 hours ago

Morbed all over the bottom of the ocean

[–] [email protected] 2 points 7 hours ago (1 children)

Good to hear but it hasn't been updated yet as far as I can see.

[–] [email protected] 1 points 18 hours ago (3 children)

Innertune stopped working for me a few days ago. I know they are working on a bugfix but so far alternatives like the fork of it from a user called Mal...something did not work for me either.

[–] [email protected] 7 points 18 hours ago (10 children)

Yeah, not sure why OP is so damn condescending here. I just tried this app today because Innertune is currently having issues playing songs and this one works.

The interface is super confusing, tapping some buttons changes other buttons next to them without any apparent reason. No explanations what symbols mean. It took me a while to find where the "liked" songs end up. Then I later tried to find it again and just couldn't find it anymore.

[–] [email protected] 14 points 21 hours ago (2 children)

This makes Section 31 sound like Oceans 11. Which would be fine if this were the first mention of Section 31 and what they are about. This is nothing like the Section 31 from DS9, maybe there is some kind of explanation for that, we'll see.

[–] [email protected] 7 points 1 day ago

Can confirm.

Source: am grounding electron.

[–] [email protected] 1 points 1 day ago

It is amazing how good Microsoft is at milking every product for maximum profit, just because people don't like the next Windows version. But most will anyway switch at some point.

[–] [email protected] 52 points 2 days ago

Nice bait in the post title.

[–] [email protected] 2 points 2 days ago* (last edited 2 days ago)

I use this daily and just wanted to highlight two downsides:

  • 1 some instances are quite slow in response

  • 2 some instances are non English, so everything except search results might be unreadable unless you know that language

The second one has been happening less frequently recently though, not sure if there are just more English instances or some other reason behind it.

[–] [email protected] 6 points 2 days ago

How about... Hear me out...

[–] [email protected] 8 points 2 days ago (2 children)

Not just microplastics but also microbes.

 

I just crossposted something using Thunder and another user let me know that my crosspost did not show that the other post was the original.

See here: https://lemmy.ca/comment/11901004

Not sure how that can happen but seems like a bug in Thunder then?

 
 

I am just impressed by the idea and execution. Just wow. Too bad he took it too far.

 

I am using hd-idle (see link) to spin down my one external hard drive on my RPI server. It is not used for large parts of the day and night so it has been quite useful to set up hd-idle, which spins down the drive after an hour or so of no activity.

Now hd-idle can generate a log file where it notes down some data, e.g. when the drive was spun down, how long it was running, what time it spun down.

You can read the file to get an impression how well it works, but I'd like to see the data visualised or analysed in some way. Seeing the past month of how often per day the drive was spun down, or average length of long it was running and so on.

Searching online I couldn't really find anything. Maybe anybody here knows more? Or what ways of recording and looking at this type of data are you using?

 

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

Updated! Updates are shown in quote text like this.

An Apps Experiment

Introduction

This is an experiment I performed out of curiosity, and I have a few big disclaimers at the bottom. Basically, I've seen a lot of comments recently about one app or another not displaying something right. Lemmy has been around for a while now and can no longer be considered an experimental platform.

Lemmy and the apps that people use to access the platform have become an important part of people’s lives. Whether you are checking the app weekly or daily, and whether you use it to stay up on the news or to stay connected to your hobby, it’s important that it works. I hope that this helps people to see the extent of the challenge, and encourages developers to improve their apps, too.

How I did it

I wanted to investigate objectively how accurately each app displays text of posts and comments using the standard Lemmy markdown. Markdown is a standard part of the Lemmy platform, but not all apps handle it the same. It is basically what gives text useful formatting.

I used the latest release of each app, but did not include pre-releases. I only included apps that have released an update in the last 6 months, which should include most apps in active development. ~~I was unable to test iOS-exclusive apps, so they are not included either. In all, 16 apps met the inclusion criteria.~~

I also added Eternity, which is in active development, although it has not had a recent update. I was able to include several iOS apps thanks to testing from @[email protected] – Thanks, Jordan! This made for 21 apps that were tested.

Each app was rated in 5 categories: Text, Format, Spoilers, Links, and Images. I chose these mostly based on the wonderful Markdown Guide from @[email protected], which was posted about a year ago in [email protected] (here).

I checked whether each app correctly displayed each category, then took the overall average. Each category was weighted equally. Text includes italic, bold, strong, strikethrough, superscript, and subscript. Format includes block quotes, lists, code (block and inline), tables, and dividers. Spoilers includes display of hidden, expandable spoilers. Links includes external links, username links, and community links. Images included embedded images, image references, and inline images.

Thanks to input from others, I also added a test to see if lemmy hyperlinks opened in-app. There was a problem with using the SFFA Community Guide that caused some apps to be essentially penalized twice because there was formatting inside formatting, so I created this TEST POST to more clearly and fairly measure each app.

In each case, I checked whether the display was correct based on the rules for Lemmy Markdown, and consistent with the author’s intent. In cases where the app recognized the tag correctly but did not display it accurately, that was treated as a fail.

Results

Out of a possible perfect 10, only 3 apps displayed all markdown correctly:

Jerboa (Official Android client) - 10.0

Alexandrite - 10.0

Voyager - 10.0

Summit - 9.7

Photon - 9.3

Arctic - 9.3 (pending)

Interstellar - 9.1

Lemmy-UI - 9.0

Thunder - 8.9

Tesseract - 8.6

Quiblr - 8.1

mlmym - 8.0

Lemmios - 8.0 (pending)

Mlem - 7.5 (pending)

Boost - 7.3

Eternity - 7.0

Sync - 6.9

Connect - 6.7

Lemmynade - 6.1

Avelon - 5.7 (pending)

More details of testing here

Disclaimers

Disclaimers

I Love Lemmy Apps (and their devs)

Lemmy apps devs work very hard, and invest a lot in the platform. Lemmy is better because they are doing the work that they do. Like, a LOT better. Everyone who uses the platform has to access it through one app or another. Apps are the face of the entire platform. Whether an app is a FOSS passion project, underwritten by a grant, or generating income through sales or ads, no one is getting rich by making their app. It is for the benefit of the community.

This is not meant to be a rating of the quality or functionality of any app. An app may have a high rating here but be missing other features that users want, or users may love an app that has a lower rating. This is just about how well apps handle markdown.

This is pretty unscientific

You’ll see my methodology above. I’m not a scientist. There is probably a much better way to do this, and I probably have biases in terms of how I went about it. I think it’s interesting and probably has some valuable information. If you think it’s interesting, let me know. If you think of a better way, PM me and I’d be happy to share what I have so you don’t have to start from scratch.

My only goal is to help the community

I do think that accurately displaying markdown should be a standard expectation of a finished app. I hope that devs use this as an opportunity to shore up the areas that are lagging, and that they have a set of standards to aim for.

~~I don’t have any Apple things~~

~~Sorry. This is just Android and Web review. If someone would like to see how iOS apps are doing, please reach out and I’ll share how we can work together to include them.~~

See the test comment in the comment section of the original post (this is just a cross-post). Thunder is doing pretty well but has a few things not showing entirely correct.

 
 

Just installed Bazzite and it seems to work well so far.

Then I added a second standard user to the system and thought they'd have access to all software I just installed for the main user. But that doesn't seem the case, Bazzite prompted me to install all those again for the second user.

Is that just a thing with immutable distros or did I do this in a wrong way? I tried looking this question up, but I couldn't find any info on multi user setups with immutable distros.

 

I am a bit late to the party in that I only today updated to the latest version. I now see that the intro skipper plugin from confused polar bear (or whathisname...) isn't working anymore. I guess that was bound to happen after the archiving of the repo.

Is there a working fork out there? I found a few threads here and there but the only forks I saw people mention seemed to also stop working after 10.9.3? Or did that get fixed?

36
Alternative to RaspiCheck (raw.githubusercontent.com)
 

I have a small self hosted setup at home with a RaspberryPi and an external HDD, just enough for what I need.

Some time ago I found a pretty sweet app which from the name implies its mostly working when you use a RPI OS, to monitor the RPI from your android phone: https://github.com/eidottermihi/rpicheck

Its called RaspiCheck (picture in the post is the one from github), and unfortunately it is seriously outdated and development ceased. It is still working on my current phone but I am well aware that's not going to last.

So I am wondering what else is out there that could fill the gap it would leave.

I am using it for 2 things mostly:

  1. monitor system stats, like simply seeing the system is running (I know, like ping), but at the same time also showing memory, average load, temperature and so on.
  2. sending SSH commands, and this is where the app really shines. Using a terminal on the phone is not impossible, but boy is it annoying. In RaspiCheck you can define commands, with placeholders, which allows you to send those to the RPI just by tapping them. So for example I got my backup set up that I can mount the backup drive with one tap, a second tap runs the right backup script (I have several I can choose from by filling the placeholder I leave in that command) and then unmount with a third tap.

I got other commands I like to reuse a lot set up in it and its really useful to me, let's me manage the RPI from my phone in an easy way.

So back to the question at hand, is there anything else like this out there for Android? If possible one app, FOSS preferred. I am pretty sure there are browser-based solutions, if there is no dedicated app other than this, then I guess that's the next best thing. What are you using in your setup that you can recommend?

 

I have been planning to install Kinoite on my laptop, dual booting with Windows.

However depending on what I read online, it is either not possible, not recommended, tricky to setup or it is just a matter of setting partitions up before installing Kinoite. Broad range of opinions and no good "tutorial" how to do it.

Anyone having direct experience with that?

view more: next ›