krash

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

Awesome <3

If you need feedback, testing etc. on this feature, I'm happy to help. Just pm me and I'll give you my github account.

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

This is really cool. Happy that you included the comments, as I find them often quite insightful. Look forward to spin this up and try it.

Edit: I know this is really hard to design and implement, but is it possible to bring in certain amount of child comments as-well? E.g., past a certain vote threshold or only X child comments deep. This might be a requirement that want to "move" the social media platform into the RSS feeder, but I want to entertain the idea.

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

There are so many monitoring tools with various degrees of complicated setup / configuration or the amount of information you get. And honestly, I've looked into various tools: checkmk, monit, Prometheus... And realised that I rarely look into that information anyway. Of all "fancy" tools, I liked the ease of Netdata to set up and the amount of information that you get. However, beware that their in the process to make their free / homelad offering worse. I've been eyeing beszel and don't forget CLI based tools that are avaible such as atop, btop, htop or glances.

If you want to delve deeper into the rabbit hole of monitoring, I can recommend you to read this article below: https://matduggan.com/were-all-doing-metrics-wrong/

[–] [email protected] 8 points 1 week ago (2 children)

I've tried different approaches with fail2ban, crowdsec, VPNs, etc. What I settled on is to divide the data of my services in two categories: confidential and "I can live with it leaking".

The ones that host confidential data is behind a VPN and has some basic monitoring on them.

The ones that are out in the public are behind a WAF from cloudflare with pretty restrictive rules.

Yes, cloudflare suck etc., but the value of stopping potential attacks before they reach your services is hard to match.

Just keep in mind: you need layers of different security measures to protect your services (such as backups, control of network traffic, monitoring and detection, and so on).

[–] [email protected] 2 points 1 week ago (1 children)

I really like this. Is it possible to have it search several sources in the future?

[–] [email protected] 3 points 2 weeks ago

I like this thread :-)

I have just checked off a long standing item in my backlog: implementing OIDC on at least two apps. I've used a remote keycloak instance for authention for my household and so far so good. Now I'll try to understand the configurations a little better before take on other items on my backlog.

[–] [email protected] 3 points 3 weeks ago

I found the UI to be horrendous, and managing tags was very painful. During the time I was paying for the cloud-service, there wasn't any noticable development of the web-app, so I stopped using it. Mind you, this was pre-pandemic and things might have changed since then.

[–] [email protected] 17 points 3 weeks ago (4 children)

I'm really fond of readeck. After being dissapointed with Pocket and Wallabag, I went with omnivore until they pulled a skiff. Out of all the FOSS read-it-later solutions - it was a very even tie between Shiori and readeck, and I went with the latter since it supports highlights.

[–] [email protected] 4 points 1 month ago

I was also eyeing this, but wanted to use another provider than openAI or ollama. So I'll wait until that's implemented.

[–] [email protected] 8 points 1 month ago

One of the main points of the article is not how it affects one as a individual, but how impacts the very social fabric of our societies. Even if you're spared from the effects of the rot economy, you're surrounded by people who are, and it impact them psychologically which in turn affects their mood, well being and their behavior towards their peers.

While I don't agree with everything in this article, it has some very important points. The digital services that we use can have an impact on our digital daily lives on par to a governments.

This isn't a call for every person to save themselves. This is a call to save our peers and our well being on a macro level.

52
Never Forgive Them (www.wheresyoured.at)
 

cross-posted from: https://beehaw.org/post/17602033

You are the victim of a con — one so pernicious that you’ve likely tuned it out despite the fact it’s part of almost every part of your life. It hurts everybody you know in different ways, and it hurts people more based on their socioeconomic status. It pokes and prods and twists millions of little parts of your life, and it’s everywhere, so you have to ignore it, because complaining about it feels futile, like complaining about the weather.

It isn’t. You’re battered by the Rot Economy, and a tech industry that has become so obsessed with growth that you, the paying customer, are a nuisance to be mitigated far more than a participant in an exchange of value. A death cult has taken over the markets, using software as a mechanism to extract value at scale in the pursuit of growth at the cost of user happiness.

These people want everything from you — to control every moment you spend working with them so that you may provide them with more ways to make money, even if doing so doesn’t involve you getting anything else in return. Meta, Amazon, Apple, Microsoft and a majority of tech platforms are at war with the user, and, in the absence of any kind of consistent standards or effective regulations, the entire tech ecosystem has followed suit. A kind of Coalition of the Willing of the worst players in hyper-growth tech capitalism.

Things are being made linearly worse in the pursuit of growth in every aspect of our digital lives, and it’s because everything must grow, at all costs, at all times, unrelentingly, even if it makes the technology we use every day consistently harmful.

This year has, on some level, radicalized me, and today I’m going to explain why. It’s going to be a long one, because I need you to fully grasp the seriousness and widespread nature of the problem.

[–] [email protected] 4 points 1 month ago

Never heard of go-proxy, seems like it will fit my needs well as I only use Caddy for rev-proxying.

Thanks for the awesome blog!

[–] [email protected] 1 points 3 months ago

I used freshrss for quite some time, but the themes always looked a bit "off" for me. Went to miniflux and its awesome in its minimalism.

 

I've seen a lot of posts for a lot of different homepage for selfhosters: homepage, homer, homarr (which has an 700 MB image!).

I was after something lightweight, simple and easy to configure and get up and running without all the frills and flashy features. And I found a hidden geml in envlinks - a really simple dashboard that is supersimple to configure (just env-variables in the compose file) and still customisable enough for my needs.

Hope it will satisfy the need of other minimalists out there :-)

 

Hello selfhosters.

We all have bare-metal servres, VPS:es, containers and other things running. Some of them may be exposed openly to the internet, which is populated by autonomous malicious actors, and some may reside on a closed-off network since they contain sensitive data.

And there is a lot of solutions to monitor your servers, since none of us want our resources to be part of a botnet, or mine bitcoins for APTs, or simply have confidential data fall into the wrong hands.

Some of the tools I've looked at for this task are check_mk, netmonitor, monit: all of there monitor metrics such as CPU, RAM and network activity. Other tools such as Snort or Falco are designed to particularly detect suspicious activity. And there also are solutions that are hobbled together, like fail2ban actions together with pushover to get notified of intrusion attempts.

So my question to you is - how do you monitor your servers and with what tools? I need some inspiration to know what tooling to settle on to be able that detect unwanted external activity on my resources.

view more: next ›