Technology

37724 readers

559 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

coldredlight@beehaw.org

Los@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

Why is it so annoyingly hard to set up a Fediverse node? (feddit.de)

submitted 1 year ago by tux0r@feddit.de to c/technology@beehaw.org

33 comments fedilink hide all child comments

Everyone (and their mother) have been trying to convince me that I should use one of my less loaded servers to be a Fediverse node. However, all Fediverse software packages I checked only support being installed on complicated systemd + Docker machines. My servers don't have either of those, because neither systemd nor Docker even exist on OpenBSD and illumos.

I know that it would be possible to manually install (e.g.) Lemmy, assuming that I won't ever need official support, but I wonder why the world outside a limited subset of the Linux ecosystem is - at most - an afterthought for Fediverse developers.

How can I help to change that?

you are viewing a single comment's thread
view the rest of the comments

[–] ubergeek77@lemmy.ubergeek77.chat 6 points 1 year ago* (last edited 1 year ago) (1 children)

I wonder why the world outside a limited subset of the Linux ecosystem is - at most - an afterthought for Fediverse developers.

I hate to break this to you, but OpenBSD is an antiquated OS masquerading as a modern one, and OpenBSD's lack of willingness to support modern standards results in the difficulty you're having.

OpenBSD feels like it's been duct taped together for decades. Anything "new" seems to just be, "sorry, not possible." The OpenBSD kernel doesn't support WiFi 5GHz. The OpenBSD kernel doesn't support even the minimum subset of isolation features in order for Docker to function properly. Why? Because OpenBSD refuses to add these features to their kernel. There are very likely other syscalls and basic features any given open source project needs, even if it's not being run in Docker, that simply do not exist under OpenBSD due to the very limited kernel it provides.

You're upset because open source projects don't support a platform that is old and developer-hostile. Turn your frustrations on OpenBSD - these projects would gladly support OpenBSD if they could.

[–] tux0r@feddit.de 0 points 1 year ago (1 children)

I hate to break this to you, but OpenBSD is an antiquated OS masquerading as a modern one, and OpenBSD’s lack of willingness to support modern standards results in the difficulty you’re having.

Ok, let us assume for a moment that “modern” is the same thing as “great”: why do people still use Linux’s terminal, which emulates an actual 70s line printer, although there have been superior input capabilities since the 80s?

[–] ubergeek77@lemmy.ubergeek77.chat 3 points 1 year ago* (last edited 1 year ago)

That's irrelevant to this discussion. I was talking about OpenBSD's lack of kernel features and driver support.

As for the Linux vs OpenBSD terminal comment, I feel like you're grasping. What does OpenBSD's terminal to better? We have had augmentations on top of the Linux terminal for years, adding things like auto complete and syntax suggestions that the 80's could never have dreamed of.