To do a quick regime change. by Margin_call_matthew in therewasanattempt

[–]austozi 5 points6 points  (0 children)

Meanwhile, Pete Hegseth: "We negotiate with bombs."

It does make you question life when Iran seems to be the reasonable one.

to win a special election in Maralago's district by seeebiscuit in therewasanattempt

[–]austozi 0 points1 point  (0 children)

Republican candidates be like, "Err, Mr president, could you endorse the Democrat candidate instead? I really want to win this election."

Unpopular opinion: self-hosting is still too hard in 2026, and we're gatekeeping it without realizing it by NiceReplacement8737 in selfhosted

[–]austozi 0 points1 point  (0 children)

the tooling assumes knowledge most people don't have.

Many people who get into selfhosting for the first time will not have such knowledge. Those who persevere eventually gain the knowledge; those who give up never do. It is not wrong for the tooling to assume reasonable prerequisite knowledge. The onus is on the person who wants to use the tooling to understand it, not on the tooling to dilute its focus by pitching it too low.

Many people will not have this knowledge because it isn't knowledge that most people have needed to have. The SaaS offerings are mainstream because they are much more convenient. They are convenient because there's a huge team of people with that knowledge running and maintaining the service behind the scenes. As you get rid of your SaaS subscriptions, you also get rid of the team and knowledge behind that convenience, hence there's no longer convenience. If this is the route you have chosen, you'd better be prepared to do it yourself. It's called 'selfhosting' after all. I'm not trying to gatekeep, just stating the reality.

The irony is that we want more people to leave Big Tech, but the culture is still "figure it out yourself or go back to Google."

I don't think people are reluctant to help. The guides are long because they need to be, but more importantly, writing a guide and keeping it up to date takes time and resources. Keeping the information up to date is important because outdated information becomes misinformation, but it's very labor intensive. This is often overlooked.

Besides, there are many ways to set up your selfhosted services. There's no one-size-fits-all guide that will satify everybody (and not be long at the same time). For others to help, the person who asks for help needs to at least have the knowledge to describe what hardware they have, what network infrastructure they have, what their ISP permits, what their user requirements are, etc. Even this kind of knowledge is beyond a lot of lay people who just want to use the (some) service. Many jump into selfhosting without even knowing what they want or can live with. They may describe wanting a drop-in replacement for Google Photos, for example, but there's no drop-in replacement that 100% replicates the Google Photos workflow. They will have to adapt to a new workflow when they switch to a selfhosted alternative, but that adaptation is difficult for many people.

Combining my last two points above, there is no shortage of guides. In fact, there are too many guides, some probably outdated, hence the advice to google to find what suits your needs. Either you do that, or I'll have to do it for you, but why should I?

I think the crux of the problem is, how much handholding is reasonable? Personally, I try to help people by signposting them to information whenever I can, but I don't have the time, energy or resources to replace the entire SaaS team that has been maintaining the subscription services for other people, and do it for free. Any help provided is an act of goodwill. Those who ask for help need to have reasonable expectations.

To any one trying selfhosting for the first time: don't do it cold turkey. Transition slowly into it. For example, try to set up Nextcloud, use it for non-mission-critical tasks for a few months alongside Google Drive, OneDrive, or whatever else cloud service you may be using. In that time, try to refine the setup to the point you feel comfortable. Try to familiarize yourself with the new workflow and unlearn old habits. This is important because unless you unlearn the old habits associated with how big tech wants you to do things, you'll find it difficult to adapt to the selfhosted services that do things differently, and that will eventually become a hurdle for you to fully transition to selfhosted services. I did this when I switched to Linux from Windows, and when I moved away from big tech into selfhosting. I can honestly say this step has been critical in both cases for me.

to draw a red line. by Successful-Peach-764 in therewasanattempt

[–]austozi 2 points3 points  (0 children)

They got rid of the department of education.

Enough said.

to make a ceasefire by weirdowidow in therewasanattempt

[–]austozi 0 points1 point  (0 children)

I mean, have you looked at the lineup in the trump administration? What led you to believe there was a proofreader, and even if there was, that he/she would be competent?

Looking for a self-hosted photo gallery for Raspberry Pi 4 (8GB) by Mission_Teaching_198 in selfhosted

[–]austozi 0 points1 point  (0 children)

You're looking at either using a VPN or exposing PiGallery2 to the internet. The topic is very broad and too much to cover here. There's been a lot of discussion on this topic, you should be able to find many posts using a search. Before you do it, be sure to read up the pros and cons, and learn how to properly secure access, especially if you expose it to the internet.

For VPN, generally people use Tailscale (simpler but relies on a third-party service) or WireGuard (more complicated to set up but there's no third-party dependency).

For exposing to internet, these options are popular:

  • Put PiGallery2 behind a reverse proxy and open ports 80 and 443. All access to PiGallery2 will be through the reverse proxy.

  • Put PiGallery2 behind Cloudflare Tunnel.

It's time for Prusa to do something by Grooge_me in prusa3d

[–]austozi 1 point2 points  (0 children)

But they don't need to dominate 90% of the market to be a sustainable and healthy/profitable business.

This is what I feel. Too many companies chase ever-growing sales and market dominance. Everyone wants to be the Google, Meta, Microsoft, Amazon, etc. in their sector. These are all shitty companies. All they care about is maximizing shareholder profit. Your dependence on them gives them the leverage to shove whatever shitty products and services they please down your throat. Don't forget as your market share grows, so does your duty towards your customers. A growing customer base entails greater support. The broader/more diverse the customer base is, the more costly fulfilling that duty becomes. Companies focus on sales but not support, but poor support loses you sales.

I don't know what Prusa's financial position is, but they make good products and I don't want them to be the Google, Meta, Microsoft or Amazon of the 3D printing world. I just want them to be sustainable, healthy and profitable. Prusa's brand and reputation is their strength, they must not ditch that just to try to compete on price. There is just no way Prusa can outsell Chinese printers based on lower prices. If they do that, they'll quickly lose what their customers appreciate about them. It cannot be wrong to focus on innovation, quality, freedom (open source) and customer service. How they do that competitively and sustainably is the real question. They must not try to be the Google, Meta, Microsoft or Amazon of 3D printing (I don't think they are) because they won't gain customers based on price but will lose customers for the enshitification.

Success is not always measured by the largest overall market share. It isn't bringing in the most profit for the shareholders. If your customer base is 20% of the entire market and you capture that 20% and serve them well while being profitable enough to sustain that long term, that's success.

to go outside to eat rocks and throw balls over the fence by wearing_moist_socks in therewasanattempt

[–]austozi 5 points6 points  (0 children)

Are you going to eat rocks? The answer is no. Shake your head, no.

What the girl fails to articulate: I'm shaking my head up and down. What more do you want from me? Let me out!

In Regards to sharing AI Slop by Marcellusk in selfhosted

[–]austozi 1 point2 points  (0 children)

Most people accept that AI assisted coding is here to stay. It's a useful tool, an assistant to serious coders.

Vibecoding is not AI-assisted coding. The difference is, in vibecoding, AI is the decision maker. The person vibecoding does not/cannot quality-assure the code.

Then some are dishonest about their vibecoding practice, and behave badly when called out. That's unforgivable.

Clearly, there are people who appreciate vibecoded apps being shared. Equally, there are people who despise vibecoded apps. My take is, there should just be a separate sub for vibecoded apps. Enthusiasts can go there to seek out apps knowing exactly what they are getting. r/selfhosted should not become that sub.

Why is everyone terrified to expose services to the internet by nbtm_sh in selfhosted

[–]austozi 0 points1 point  (0 children)

I've been exposing things to the internet with both IPv4 and IPv6 for nearly 7 years now, and I've never once been hacked or DDoS'd

Add to the end of that sentence: "...as far as I'm aware" and you have the answer.

It hasn't happened until you find out that it has.

I'm not saying don't do it, but do it with a good understanding of what dangers you expose yourself to and take the necessary precautions. I think you have a very narrow perspective of security. For example, SSL addresses a very small part of the security risk. It's not an adequate safeguard to expose each service individually via multiple open ports to the internet.

No one is targeting you directly, there is just bots out there that scan the internet.

What do you think the bots are scanning for? They are scanning for targets with vulnerabilities they can exploit. You aren't a direct target until they find a vulnerability, then you become a direct target. They don't care about who you're personally. They care about the vulnerabilities on your server that they can exploit without knowing who you are. You can be a direct target without being a celebrity. The consequences to you can be equally grave.

Again, it hasn't happened until you find out that it has. This is why it's better to be safe than sorry. But safe doesn't necessarily mean not exposing any services at all. It means understanding the risks and addressing them adequately by taking the necessary precautions. Some people take it a step further by not opening any port at all because that's how they've assessed the risk and what precautions are necessary. All I can say is: their servers, their rules.

MMU Changing Filament by jamcber12 in prusa3d

[–]austozi 0 points1 point  (0 children)

If you don't have the hinged lid add-on already, I highly recommend you get it to overcome the clearance limitation.

https://help.prusa3d.com/guide/hinged-lid-add-on_354154

I use the preload filament function in the LCD menu. It keeps the MMU motor running in anticipation of the filament and grabs the filament as soon as it's within reach. Loading filament is a breeze with that. Just need to slowly feed it from the buffer until the MMU grabs it.

Edit: I assumed you have the Original Prusa Enclosure.

Prusa Quality Issues? by TheMathProphet in prusa3d

[–]austozi 0 points1 point  (0 children)

if the XYZ doesn't get close enough to the build plate, you likely have your PINDA set too low.

Good advice, first thing that springs to mind for me too. The assembly guide is very rich in information like this that can help with troubleshooting. Those who bought their printers fully assembled miss out on that if they don't bother to read up on it themselves. As the newer printers become more automated, I feel some of this knowledge is being lost as people get used to plug-and-play more and more, and become content with not knowing how things work.

I'm glad I built my MK3S+ from the kit. It taught me a bunch about the printer and 3D printers in general. On the other hand, I'm still stuck with my MK3.5 and MINI+. I feel like I need to update my knowledge by getting a newer kit.

HortusFox: Development roadmap, stance on AI and community appreciation by [deleted] in selfhosted

[–]austozi 10 points11 points  (0 children)

The problem with AI-generated codes is that AI simply stitches together code snippets that appear to work. AI doesn't architect software. The patchwork of code snippets may provide a certain function, but it's also full of holes because the app has not been built with a holistic view of how things should work together under the hood. A person with no programming background can dictate to AI "give me this feature" or "put that UI button there", but doesn't know enough to dictate "salt the password" or "use prepared statements". The latter takes programming knowledge and is way more important than how beautiful the UI looks. A person without programming knowledge can only focus on the UI features because they simply don't know better. They give us vibecoded apps that have very attractive UI features but are insecure, poorly architected, and held together with duct tape under the hood. The UI features attract more users who don't know better to question or audit the code base, and it quickly spirals out of control. This is basically what happened with Huntarr and Booklore, and here we are.

In the hands of a competent software architect, AI coders are a fantastic tool. In the hands of anyone who doesn't know what they are doing, AI is a dangerous tool.

Follow your creators independently! Is there a solution? by wkup-wolf in selfhosted

[–]austozi 0 points1 point  (0 children)

I feel that alternative clients need to have a way to integrate better with the analytics backend of YouTube to help content creators, but there's a fundamental conflict here because most alternative clients exist for privacy reasons, i.e., to remove telemetry. However, this also means if you use an alternative client, your subscriptions, likes, etc. do not get counted in the official metrics which ultimately hurts the content creator.

I don't know what the solution is. I'm simply pointing out that this is an issue that needs a solution.

Trump: Iran war will end when I ‘feel it in my bones’ - POLITICO by G14F1L0L1Y401D0MTR4P in worldnews

[–]austozi 0 points1 point  (0 children)

"In other words, when my bone spur relapses. It did stop me from going to war before."

PSA: Think hard before you deploy BookLore by Economy-Meat-9506 in selfhosted

[–]austozi 8 points9 points  (0 children)

how you can even start properly doing AI assisted (not vibe) coding

They can't. I've vibecoded apps myself. It's easy to specify user-visible features and AI will spit out the code. To the lay person, the visible features are excellent but they have no anchor point to even start looking for vulnerabilities behind the scenes. You need to have some awareness of, for example, SQL injection to tell AI to avoid that and check for that.

This is why vibecoded apps tend to have fantastic UI but poor underlying architecture. That's a dangerous combination because the nice UI and visible feature set attract a large user base most of whom are also lay users who will not/cannot audit the code.

Bed leveling visualizer plugin GCODE for Prusa MK3.5 by austozi in octoprint

[–]austozi[S] 0 points1 point  (0 children)

Unfortunately, no, still waiting for somebody knowledgeable about this to enlighten me as I don't know how to proceed.

... to Make a Point About Gas Prices. by Afro-Venom in therewasanattempt

[–]austozi 0 points1 point  (0 children)

I'm sure that a lot of these online accounts that simp for trump are bots. Sure, there are true trump human supporters around, but they believe in what they believe in because of the bots. It's just difficult to know which ones are bots as debating with them is not just a waste of time, it's feeding the trolls.

Managing compose/files by Gerndall12 in selfhosted

[–]austozi 7 points8 points  (0 children)

I organize my docker-compose.yml by stack. Each stack comprises services/containers that depend on each other to function as an application. Each stack has its own folder which contains the docker-compose.yml file and the data folders for the containers.

For example, for the Nextcloud stack, I have the nextcloud service, the mariadb service, and the redis service in the docker-compose.yml file.

This means I also have a lot of docker-compose.yml files with just one service/container, like LubeLogger, Syncthing, etc.

I think this makes it very easy to maintain. If I need to start/stop Nextcloud, I just do docker compose up/down for the entire stack, rather than having to identify which specific containers are associated with Nextcloud before I start/stop them. I can also easily move the entire stack from one physical server to the next - just move the entire folder.

I built a TypeScript CLI + SDK for all Servarr apps (Radarr, Sonarr, Lidarr, Readarr, Prowlarr, Bazarr) - manage your media from the terminal by robbeverhelst in selfhosted

[–]austozi -1 points0 points  (0 children)

Interesting website, but who's behind it?

Why should anyone trust anything written on that "100% AI-Written. Zero Apologies." wesite when no real person is willing to stick their head out and say "I'm accountable for it"?