[-] sj_zero@lotide.fbxl.net 0 points 5 days ago

The increasingly atomized world will not be able to continue for much longer. I fear for what will come next.

[-] sj_zero@lotide.fbxl.net 2 points 6 days ago

I haven't watched through this one yet, but I found the first book in the light novel series relatively self-contained, and I didn't really feel like the later books added much to the series. Assuming it made it through that first book, it might be worthwhile sitting exactly where it is.

[-] sj_zero@lotide.fbxl.net 2 points 6 days ago

The most important risk you face is if somehow mains voltage ends up contacting somewhere you get electrocuted and die.

There are 2 purposes of an earth ground: First it can be used as a reference for certain signals, such as microphones. Second, it can be used to protect against turning yourself into a sparker.

There is a clear separation between mains voltage and system voltages so it's typically not going to be a problem, but if a little wire ends up contacting the power supply case it can become energized and things start to get really bad.

Most of the electrical code where I live focuses on grounding as "Bonding", which is purely safety related for giving dangerous voltages a safe place to go.

1

To an extent. As I mentioned, some redditors are really too interested in having an enemy to fight, so hopefully we can get some cool people over without attracting the nutjobs who see 1945 germans everywhere.

115

Short side hamper handle from the top:

https://social.fbxl.net/media/c06e0e29294d96565b1b189f3bde757486e4af9d79cb92ab3387419f5a802f4b.jpg

Long side hamper handle from the bottom:

https://social.fbxl.net/media/9890d325f4126ae3d58d94435392bff91c44b5f6b557e39a97bf5e16f891b1c7.jpg

I always enjoy prints that just become part of our lives (and especially ones that let us keep using something that's going to the landfill otherwise)

The hamper has handles that break. For most people I think that'd be time to replace it. I didn't want to do that, so I designed a new handle based on the handle on the short end. This ended up being a mistake later, I'll explain then.

I printed 2 handles (the connection between the two is just to make the printing work better since it can print the two pieces as one piece, then I just snap the two apart and clean up the spot they were connected)

I used my rotary tool to remove the remnants of the original handles. I should have used the cutting tool but I had the diamond grinder so I used that. It worked fine, I was able to fully remove the old material. A quick test fit confirmed that the handle design was pretty good (I just used a tape measure for the measurements so this was a real potential problem)

I went to the long side, but realized that the design of the hamper was different lengthwise than widthwise. I removed a couple tabs that were going to block the new handle, and instead of putting it in as designed, I just put it sideways, which fit.

I put the two in and added gorilla glue. Gorilla glue requires water to foam up, so I wet all the parts. Now everything is fitted, the glue is in, and it's just drying now. I'd consider this repair a success, and I expect the strong PLA part to give the whole hamper a lot more stiffness at those parts, and there's significantly more material in these spots that break. If the other two handles break, I'll just print two more, and at that point I can't help but think that the hamper will be bulletproof.

42

Link aggregators have a problem on the fediverse. The approach is server-centric, which has positives, but it also has major negatives.

The server-centric approach is where a community belongs to a certain server and everything in the world revolves around that server.

The problem is that it's a centralized formula that centralizes power in a the hands of a whichever servers attract the most users, and potentially breaks up what might be a broader community, and makes for a central point of failure.

Right now, if user1@a.com and user2@b.com talk on community1@c.com then a lot of things can happen to break that communication. if c.com defederates b.com then the communication will not happen. If c.com breaks then the communication will not happen. If c.com shuts down then the communication will not happen. If c.com's instance gets taken over by management that doesn't want person1 and person2 to talk, then the communication will not happen.

Another problem is that user1@a.com and user2@b.com might never meet, because they might be on community1@a.com and community1@c.com. This means that a community that could reach critical mass to be a common meeting place would not because it's split into a bunch of smaller communities.

Mastodon has servers going up and down all the time, and part of the reason it's able to continue functioning as a decentralized network is that as long as you're following people on a wide variety of servers then one server going down will stop some users from talking but not all of them so the system can continue to operate as a whole. By contrast, I'm posting this to one server, and it may be seen by people on a wide variety of servers, but if the one server I'm posting this to goes down the community is destroyed.

There are a few ways to solve the problem...

one method could work as something like a specific "federated network community". There would be a local community, and the local community would federate (via local mods, I presume) with communities on other instances creating a specific metacommunity of communities on many instances that could federate with other activitypub enabled communities, and if any of the federated communities go down the local community remains. If any servers posed problems they could cease being followed, and in the worst case a community could defederate totally from a server (at a community level rather than a server level) In that case, community1@a.com and community1@b.com could be automatically linked up once both connect to community1@c.com (I'm thinking automatic linking could be a feature mods could turn off and on for highly curated communities), and if c.com shuts down or defederates with one of the two, user1@a.com and user2@b.com would continue to be able to talk through their federated network.

Another method would be something more like hashtags for root stories, but I don't know how server-server links would be accomplished under a platform like lemmy, kbin, or lotide. I don't know how hashtags migrate on mastodon type software and how that migrates. In that case, it might be something like peertube where a network is established by admins (or users, I don't know) connecting to other servers manually.

Finally, I think you could implement the metacommunity without changing the entire fediverse by having the software auto-aggregate metacommunities. You could create a metacommunity community1 on a.com that would then automatically aggregate all posts on communities called community1 on all known servers. The potential downside of this is you could end up with a lot of noise with 100 posts of the same story, I haven't thought much about how you could handle duplicates so you could participate but wouldn't have 100 similar posts. In this case with respect to how to handle new posts, each metacommunity would be a local community and new individual posts would be posted locally and federated to users on other metacommunities. If metacommunities of this sort became the norm, then the duplicates problem may be solved organically because individuals using metacommunities would see the posts on other metacommunities and wouldn't bother reposting the same story, much like how people see a story and don't repost in individual communities.

One big problem is scaling, doing something like this would definitely be a non-trivial in terms of load per community. Right now if one person signs up to one community, they get a lot of posts from one server. Under a metacommunity idea like this, if one person signs up to one community, they get a lot of posts from many, many servers. lemmy.world has 5967 total instances connected to it, and 2155 instances running lemmy, lotide, kbin, mbin, or friendica that could contain similar types of community, that's a lot of communities to follow for the equivalent of one single community, especially if some of the communities in the metacommunity have a lot of traffic in that community. You'd have to look at every known server to first see if it exists and second if it has a community appropriate for the metacommunity, and the metacommunity would have to routinely scan for dead hosts to remove from the metacommunity and live hosts that may start to see an appropriate metacommunity has been created.

I'm sure there are other solutions, but I'm just thinking of how things work within my current understanding.

Of course, for some people, the problem is one they don't want solved because it isn't a problem in their view (and that's a legit view even if it's one I'm not really amenable to). Some people prefer smaller communities, or want tighter control over their communities. For servers or communities that don't want to be brought into a metacommunity, it seems like some sort of flag to opt-out (or opt-in as the case may be) should be designed in -- I'm thinking something in the community description like a textflag NOMC or YESMC that server software would be designed to respect.

With respect to moderation, It seems to me that you could have a variety of strategies -- you could have a sort of default accept all moderation where if one instance moderates a post other instances take on the same action, or whitelist moderation where if one instance or one set of moderators on a whitelist take an action then other instances take the same action, or a sort of republican moderation where if a certain number of instances take an action then other instances take the same action, and probably an option for individual metacommunities to only accept moderation from the local community the original post came from. I suspect you'd want a choice in the matter per metacommunity instance on a server.

41

Anyone who knows me knows that I've been using next cloud forever, and I fully endorse anyone doing any level of self hosting should have their own. It's just a self-hosted Swiss army knife, and I personally find it even easier to use than something like SharePoint.

I had a recurring issue where my logs would show "MYSQL server has gone away". It generally wasn't doing anything, but occasionally would cause large large file uploads to fail or other random failures that would stop quickly after.

The only thing I did is I went in and doubled wait_timeout in my /etc/mysql/mariadb.conf.d/50-server.cnf

After that, my larger file uploads went through properly.

It might not be the best solution but it did work so I figured I'd share.

14
submitted 7 months ago by sj_zero@lotide.fbxl.net to c/science@mander.xyz

https://youtu.be/gNRnrn5DE58?si=VTrpcfDDDukItwCH

It's an older video, but I really enjoyed it and found it really thought provoking. Precision is something we take for granted but as this video shows it's something that was incredibly difficult to get to where we are.

[-] sj_zero@lotide.fbxl.net 82 points 7 months ago

Originally copyright was like 15 years and if the thing was really good for you then you could Apply for a second 15 year term.

30 years is a long time to get a monopoly over something. As a human being, 30 years is a significant part of your entire lifetime. From birth to 30 years you have your entire childhood, many people go to and finish college, get married, have kids, achieve a degree of professional success. Another 30 years from that moment, many people are at the end of their lives. They're retiring, some who smoked or did other things are dying of old people diseases.

I believe strongly enough that 15 years is a reasonable copyright term that my book, the graysonian ethic, which I published in 2021, has a note on the legal page releasing it to the public domain 15 years from the first date of publishing, and in jurisdictions where you can't do that, it's licensed under the creative Commons zero license

If I want to own the rights to another book, I can write another book. If I can't make back the money that I spent writing and publishing it in 15 years, then that's a me problem, not a society problem the police can help enforce.

The famous song Happy Birthday left copyright only a couple years ago, and not because it timed out. The song which was written in the era of my great grandparents only lost protection from the largest state in history because after a hundred years no one could keep track of who owned it anymore.

[-] sj_zero@lotide.fbxl.net 54 points 8 months ago

I found one study that found that 100% of people who breathe oxygen die, but I found another study that found that 100% of people who don't breathe oxygen die!

[-] sj_zero@lotide.fbxl.net 55 points 9 months ago

Always has been.

It's one of the reasons why lemmy never really took off until the great reddit migration despite having a decent software product.

25

Apparently it's been out since June and I just never realized, but there's a new pfsense out.

https://www.netgate.com/blog/pfsense-2.7.0-and-23.05

Not exactly timely, but I bet I'm not the only one who easily forgets about that particular thing. Most of my stuff is set to autoupdate so I tend to forget.

The upgrade downloaded a large number of packages, I think about 160, during which network connectivity continued to function. After downloading, my router PC reset, and that first boot after the upgrade took quite a few minutes. I ended up running the 90 second timer out after which it reset to 20 seconds a number of times. I was just about to start digging for an HDMI cable to see what when I heard the router beep and my internet came back. Perfect upgrade, didn't need to fix anything afterwards.

18

So both lemmy and lotide were having big problems where they'd get totally overwhelmed, especially once I started federating with huge instances. At first I thought it was because my servers aren't very powerful, but eventually I got the idea that maybe it's because it can't keep up with federation data from the big instances.

So I decided to limit the connections per IP address. Long-term testing isn't done yet, but so far both my lemmy and lotide instances aren't getting crushed when they're exposed to the outside world, so I think it's helping.

In /etc/nginx/nginx.conf, under the http section, I added the line "limit_conn_zone $binary_remote_addr zone=conn_limit_per_ip:10m;"

Then, in my sites-available folder for the services, I added "limit_conn conn_limit_per_ip 4;" or something similar. Both lemmy and lotide have different sections for ActivityPub and API, so it appears I can limit the connections just to those parts of the site.

It's only been a few days, but whereas before both instances would die randomly pretty quickly once exposed to the outside world, now it appears that they're both stable. Meanwhile, I'm still getting federated posts and comments.

[-] sj_zero@lotide.fbxl.net 92 points 10 months ago

Plugs can be more secure, but they also can't.

You don't want plugs to be too secure because they're supposed to be temporary. Plug in fast, unplug fast.

There's a benefit to plugs that come off easily: That's the weakest point. If you kick a cord, the cord doesn't snap, it just comes unplugged. If you make your plug stronger, maybe instead the cable breaks and now you've got lethal voltage swinging around, or you have arcing inside a connector or inside a cable that starts a fire.

There are electrical connections that are more secure used in industry or other places. For example DIN plugs or Brad Harrison connectors.

[-] sj_zero@lotide.fbxl.net 97 points 10 months ago

We're not allowed to have nice things.

0
submitted 10 months ago by sj_zero@lotide.fbxl.net to c/history@lemmy.world

I have a feeling that there's a lot of history that will be uncovered in Africa, particularly as many countries on the continent get richer and have the resources for stuff like archaeologists to learn more about the past.

In my recent history kick it was really frustrating the black hole of African history (besides the egyptians, obviously). But we're learning more about stuff like Ethiopian civilization, and obviously Great Zimbabwe, what else is out there buried waiting to be found?

[-] sj_zero@lotide.fbxl.net 67 points 10 months ago

It's a normal situation when you have big migrations like the reddit migration. Same thing happened on mastodon with the various twitter migrations.

A lot of people migrate thinking they're reaching the promised land, realize they aren't getting what the want from the new platform and go back. It's the nature of bandwagon jumping.

It's just fine. The process of growth is dynamic, and the people who remain are the ones who like the platform.

[-] sj_zero@lotide.fbxl.net 49 points 11 months ago

Honestly, I've been considering minetest the real successor to minecraft. It's just really decent, and it doesn't have all the risks of minecraft being controlled by someone else including opening the game being gatekept by their centralized servers.

[-] sj_zero@lotide.fbxl.net 49 points 11 months ago

The worst is when the problem is something that will only manifest at scale, so your bosses are going "You should have tested it before putting it in production!" And I'm like "DO YOU THINK I DIDN'T TEST IT BEFORE PUTTING IT IN BLOODY PRODUCTION!?"

[-] sj_zero@lotide.fbxl.net 52 points 11 months ago

It's the internet. Eventually if you're popular enough, some jerk off will say something dumb.

It's cheap and easy to do it! Watch: I'll kill you!

The internet is not your friend.

-1
1

https://invidious.fbxl.net/watch?v=oK1UgqHz7_U

A relevant passage from The Graysonian Ethic: "In a lot of ways you do not realize, the human race is entirely defined by our biology. Many of your deepest-rooted fears and ambitions are written into your blood, in a library that was passed down by millions of generations of successful creatures going all the way back to the single celled organisms that first spawned within the primordial ooze."

-1

https://invidious.fbxl.net/watch?v=i70wkxmumAw

Good science is humble, and is often wrong, and admits it. This is a really cool story about that.

-1

https://m.jpost.com/science/article-715147/

The Saccorhytus looks somewhat like a spikey jelly bean with pursed lips and is described by the University of Bristol as "resembling an angry Minion."

view more: next ›

sj_zero

joined 1 year ago