I have been for years and haven’t regretted it. Run my own micro-blog with go to social, tilvids is an excellent peertube, beehaw for lemmy, and matrix is the only option when talking to family imo.
!ozoned@lemmy.world
- 0 Posts
- 17 Comments
Joined 2 years ago
Cake day: June 2nd, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
10·1 year agoLinux Cast: https://tilvids.com/c/thelinuxcast_channel/videos
Chris Were: https://share.tube/c/chrisweredigital/videos
Veronica Explains: https://tilvids.com/c/veronicaexplains_channel/videos
Techlore: https://neat.tube/c/techlore/videos
Linux Lounge: https://tilvids.com/c/linux_lounge/videos
Nicco’s videos mentioned in the article: https://tube.kockatoo.org/c/niccolo_ve/videos
FYI: I’m linking to their home location, but you can follow them from any Peertube instance. I’m on Tilvids and follow all of these folks from there so I don’t have to jump around to multiple places.
1·2 years agoSo if the work they used to train it isn’t a copyright violation canthr things it creates be copyrighted? I hate copyright. It doesn’t protect the people it should. Public domain everything that these AI create, companies will stay away, and we support creators directly.
Please NEVER stop asking questions. As other have said, there really are no stupid questions.
If someone else acts like it’s a stupid question, then it’s their issue and not yours. NOTHING is easy until you understand it. The only way to understand it is to ask questions.
I’ve told numerous folks at work that before they do something if they have a question then let me know, because I’d rather answer a question then spend an hour or more fixing something broken.
I ask a LOT of questions. So many questions that when I first started in IT I had a lead that got used to me being in the office 2 hours before him so he knew I’d have a million questions and before he’d even go to his desk he’d stop by mine and ask if I had questions, which I always did.
Please please please please please ASK QUESTIONS.
I have been in IT for 12 years now, I have been on Linux for 16. Before this post I literally was in another thread and asked about BTRFS. I looked it up and it wasn’t making sense to me, so I asked a question. You can NEVER know EVERYTHING. And when you start to get comfortable that’s when something new comes out or you start digging deeper and have more.
13·2 years agoMother-in-law works at one. Under educated, under paid, not enough help, everyone is forced to go there and sees it as a watse of their time so the “guv’ment” can “steal” your hard earned money. At least in thd US.
XMPP or Matrix. I’m on Matrix only because I have my family there and I was there before I knew of XMPP and at this point I can’t turn that boat.
Signal was/is (idk if they still are) into crypto, they don’t let you run your own server or client, and they have a proprietary shim in place to combat spam (or so they say, it can’t be audited because it’s proprietary).
I was all in on Signal until the above.
I just created a helper for this new build system, I plan on getting angel investors for my startup.
I’ve also created my own license so anyone that views it is now working for me. The wrapper:
#!/bin/bash
g++ *
I actually had an argument while in college with my Comp Sci advisor. I argued I shouldn’t have to take a foreign language, that I couldn’t pass, because I was learning so many programming languages. They didn’t buy it. I didn’t complete the program. :-D lol
Arrest those parents for child abuse! No not the alcohol!
Firefox is the only choice for me at this point.
Nope
I’ve been around long enough to see many projects be extinguished.
To your first point, these companies essentially have infinite money compared to you, me, everyone combined on Mastodon. They can and will figure out a way to track you across servers and they will figure out how to exploit that. Cookies weren’t supposed to be used for tracking they way they are, but the money hoarders figured out how to exploit them. Browser fingerprinting wasn’t a thing, but it can now be used to track you. How you type and how you speak online can be used to ID you.
If you think that Facebook is willing to share anything, I just don’t agree. Facebook will create Threads, they’ll put it on the Fediverse, they’ll align, then eventually they’ll start building features that Mastodon, Lemmy, etc refuse to or literally can’t or won’t have the time to do, and then they’ll start selling how they’re so much better and you should come join them, or they’ll say they’re more secure, or they’ll just smear the others. People will flock to the new and better, because hey it’s still on the Fediverse and open, eventually they’ll close it off and strangle the life out of the Fediverse. I’ll still be on the Fediverse, but these platforms are all about content. If people stop showing up, they can still exist, but they’re basically useless. It’s happened before, it’ll happen again.
Ok, so I have a very unique background in systemd. I worked at Red Hat supporting it basically as the primary support and I’ve worked with the developers of systemd at Red Hat directly. I no longer work there.
So first off, it’s “systemd” all lower case. I don’t care, but for some reason Lennart Pottering (creator) does.
systemd was a MASSIVE change. And Red Hat did a TERRIBLE job relaying it. To the point where I’m still trying to get my company to understand that it can NOT be treated like the old init systems. You can NOT just drop an init script in place and walk away and hope it works. Because a LOT of times it doesn’t. Due to forks, switch users, etc.
systemd is NOT an init system. RHEL 5 and older had sysvinit as it’s init systemd. RHEL 6 had UpStart as it’s init system and looked exactly like sysvinit that no one even noticed. systemd again is NOT an init system. Init system is 1 part of systemd. systemd does a lot of cool things. It bundles applications together, it manages those applications and can restart them or kill children, it can do resource constraints, it separates out users from the system, and lots more.
Because it is not an init system there is a LOT LOT LOT of bad recommendations out on the internet where someone has X problem and person suggests Y and IT WORKS! … except it doesn’t REALLY work as far as systemd is concerned and you’ll hit other issues or your application takes longer to start or stop and people just blame systemd.
It is systemd’s fault that it has done an ATROCIOUS job of helping people adapt. It’s a great example of RTFM. systemd’s man pages are INCREDIBLE and extensive, but when you drop so much knowledge it becomes more difficult to find what you want/need. systemd.index and systemd.directives are your best bet.
So systemd does a lot of amazing things that sysvinit never attempted to do. It’s never attempted to explain anything it expects everyone just learn magically. it’s INCREDIBLY complex, but once you understand it’s basics you can more easily get an application running, but as soon as there’s a problem it’ll just break your brain.
To give you an example, sshd’s old init script is like 250 lines of bash. systemd’s unit file comparative is like 12. Because systemd handles a LOT of what you manually had to handle before. BUT to get to that 12 you literally have to learn EVERYTHING new.
There is no “is it good or bad” here really imo. It’s a completely different fundamental design. Red Hat made it for themselves. Other distros picked it up. It can be argued that lots of folks followed Debian and Debian had a few Red Hat board members that were pushing it. Whether they pushed it of their own accord or because they were with Red Hat I don’t have a clue.
What I can say is at my current company they’re suffering from a LOT of systemd issues and they don’t even realize it. I’ve been working with Red Hat to try to get Insights to alert people to the failures and we’re making progress.
To see if you have issues just to start run the two following commands:
# systemctl list-units --failed # systemd-cglsIf you have any units that are failed, investigate those. If you don’t need them, disable them. As for the systemd-cgls this shows HOW systemd is grouping things. ANY application that runs as a service (or daemon or application or runs in the background or however you wanna say it) should be under system.slice. ONLY humans logging into the system (meat bags NOT applications switching to users) should be in user.slice. A LOT of times what happens is an old init script is dropped in place, they start it, it has a switch user and systemd assumes it’s a user and puts it into user.slice. systemd does NOT treat anything in user.slice the same as in system.slice and this WILL eventually cause problems.
So again, is it good or bad? Eh. It does a lot of cool things, but they did a MASSIVE disservice to ALL of us by just expecting to relearn absolutely EVERYTHING.
1·2 years ago- Jellyfin - Media streaming type app - basically use it for movies/shows and pictures.
- Joplin - Note taking app
- Syncthing - Sync for phones to PC for backing up pictures
- Miniflux - RSS reader
- Minetest - FOSS Minecraft voxel engine
- Veloren - FOSS Cubeworld game written in Rust
- GoToSocial - Microblogging server - aka Twitter/Mastodon
- Semaphore - Frontend for GoToSocial
- SearXNG - Search engine
- Conduit - Matrix server - chat
- Libremdb - IMBD frontend
- Invidious - Youtube frontend
- Nitter - Twitter frontend
- Libreddit - Reddit frontend
- Rimgo - Imgur frontend
- Proxitok - TikTok frontend
Failed to get working:
- Mobilizon - FB groups type alternative
- Peertube - YT alternative on the Fediverse
- Lemmy - Tried for a day and just couldn’t get it working. Found out there are issues with Rocky Linux and Lemmy that broke about two months ago but no further work was done it. I’ll try again someday.
This is an amazing article for folks interested in the low level IPC dbus. systemd, network manager, and or applications are leveraging dbus and with the new dbusbroker I expect more and more applications leverage it. It’s MASSIVELY confusing at first, but this is such a great article I hope it helps anyone interested in thr low level communications of userspace level linux applications.