MoogleMaestro

joined 1 month ago
[–] [email protected] 2 points 1 day ago

You can be masculine and also be an egg. (Am I doing that term right?)

[–] [email protected] 16 points 3 days ago* (last edited 3 days ago) (1 children)

Yes, brave Sir Donald turned about and gallantly, he chickened out.

[–] [email protected] 12 points 3 days ago (1 children)

Right?

Lemmy ml and a history of Putin defense?

Alright fam.

[–] [email protected] 5 points 4 days ago

I noticed this as well. It's a shame as I still use it as my daily search driver.

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

Taylor Swift should just make her own social media company. Put mastodon on a server and call it a day for X dot com lmao

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

Regarding VPNs, I wish this was an easier way of doing it. Unfortunately it requires all friends to be tech savvy enough to understand why a vpn is necessary.

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

Yeah, thanks for sharing this. I'm going to have to give this a try sometime.

I had previously been building it manually, but I think I'm starting to realize that gitlab/github CI is basically essential to running a proper repository anyway.

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

I definitely agree with this.

[–] [email protected] 1 points 6 days ago (1 children)

My experience with earbuds (not headphones) that were "noise cancelling" before active noise cancelling was a thing was never all that great. The seal is too difficult to design in the same way over the ear headphones can be for passive noise cancelling. This is probably due to ear size differences and all that, so ymmv on whether or not passives work. Obviously, passive noise cancelling over-the-ears are going to be better, but that's basically always going to be true for any debate of Headphones vs Earbuds IMO.

I think there's a confusion caused by mixing up headphones and earbuds, which I think are for two very different markets. Earbuds have always been for the more casual audience.

My experience with battery life has been pretty much non-perceptual, but I did make note that I'm not sure how long the batteries in these devices can even really last. I agree that the disposable nature of battery-based headphones are a bit disconcerting.

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

As someone who uses FLAC for all of my audio needs, yeah I agree that Bluetooth bitrate is pretty bad (and often uses the lower quality.)

But this image is basically claiming that "cheap passive" plug-ins are superior to the more expensive bluetooth ones. That's simply not true. My experience with those have basically always been bad, so I'm not a big fan of ear buds to begin with over headphones. I don't take the person in the image that OP posted is all that worried about lossless (or even high quality lossy) and is more concerned with money to value. So while the analogue audio out can be high quality, you're simply not benefitting from it if you buy any sub $100 earbuds where the EQ profiles are all trash. And if you're going to spend over $100, at that point you may as well go for the bluetooth connected for all of the other pros mentioned.

I am a firm believer that super-high-quality seekers already know what they want: Over the ear cans that deliver awesome sound and have noise cancelling by their sealed design. They were never the people buying throw away headphones anyway. That's basically why I said that they're great but certainly not for anyone who wants to do professional audio (unless for sound testing what normal humans are likely to hear, ofc.)

edit: Oh and, just to be clear, I think every phone should have a headphone jack as well because the option for analogue is important! I wouldn't say I'm 100% thrilled with less options, mind you.

[–] [email protected] 13 points 1 week ago* (last edited 1 week ago)

Even better: do a git history of certain files to get a broad sense of history and understand it's evolution.

I highly advise this practice for familiarizing yourself with parts of a codebase you may otherwise not know anything about. Interesting commits you should git show.

Though combining this with scripting would also be interesting. 🤔

[–] [email protected] 6 points 1 week ago

I hate writing a serialized format

I mean, that's why it's serialized. It's not supposed to be written by hand, that's why you have a deserializer. 🤦

 

Hi there self-hosted community.

I hope it's not out of line to cross post this type of question, but I thought that people here might also have some unique advice on this topic. I'm not sure if cross posting immediately after the first post is against lemmy-ediquet or not.

cross-posted from: https://lemmy.zip/post/22291879

I was curious if anyone has any advice on the following:

I have a home server that is always accessed by my main computer for various reasons. I would love to make it so that my locally hosted Gitea could run actions to build local forks of certain applications, and then, on success, trigger Flatpak to build my local fork(s) of certain programs once a month and host those applications (for local use only) on my home server for other computers on my home network to install. I'm thinking mostly like development branches of certain applications, experimental applications, and miscellaneous GUI applications that I've made but infrequently update and want a runnable instance available in case I redo it.

Anybody have any advice or ideas on how to achieve this? Is there a way to make a flatpak repository via a docker image that tries to build certain flatpak repositories on request via a local network? Additionally, if that isn't a known thing, does anyone have any experience hosting flatpak repositories on a local-network server? Or is there a good reason to not do this?

 

I was curious if anyone has any advice on the following:

I have a home server that is always accessed by my main computer for various reasons. I would love to make it so that my locally hosted Gitea could run actions to build local forks of certain applications, and then, on success, trigger Flatpak to build my local fork(s) of certain programs once a month and host those applications (for local use only) on my home server for other computers on my home network to install. I'm thinking mostly like development branches of certain applications, experimental applications, and miscellaneous GUI applications that I've made but infrequently update and want a runnable instance available in case I redo it.

Anybody have any advice or ideas on how to achieve this? Is there a way to make a flatpak repository via a docker image that tries to build certain flatpak repositories on request via a local network? Additionally, if that isn't a known thing, does anyone have any experience hosting flatpak repositories on a local-network server? Or is there a good reason to not do this?

 

It's an interesting story as the English subtitles were added directly in the Japanese release, avoiding the Harmony-Gold licensing problem probably. It's a good work around.

 

I may have missed it, but is there a way to see all of my subscriptions at once?

view more: next ›