apigban

I'm running a PBS instance (plus networking containers) for 4years now, cc on file for the first 2 years, now on file, but my usecase is operating within the free-forever tier.

My instance has not been deleted by them, though I've rebuilt the multiple times since.

The region you are on might be struggling with capacity issues, I use middle east region and never encountered account/vm deletions (yet). For my case, latency isnt an issue so i dont mind having it ona far away region.

The job security.

Fiber. Yum.

Hello! I'm a hobbyist in this space (scripting/coding), does anyone here have a:

• gold standard of what commit messages should look like?
• common practice/etiquette for commit message?

I never had a team or guide or mentor and when I saw this i felt that my commits are like smoke signals describing that there's a fire. which isnt really helpful.

I tried to contribute to a python module that I use daily, my PR was so over engineered (iirc i added just 3 lines, but with tests, screenshots, CI/CD) i think to compensate for my lack of experience that I got called out ("wow this is pretty extreme just for that feature").

Depends on what kind of service the malicious requests are hitting.

Fail2ban can be used for a wide range of services.

I don't have a public facing service (except for a honeypot), but I've used fail2ban before on public ssh/webauth/openvpn endpoint.

For a blog, you might be well served by a WAF, I've used modsec before, not sure if there's anything that's newer.

I'd make my own nas.

I got this step, defederating essentially says to them that I dont consent to them getting my data.

But I'm really missing something here, since any instance that zucc controls that is federated to the large instances just exposes my data to zucc.

Defederating is one step, the instance owners have taken that step now, so far so good, well then zucc will just create a lemmy/kbin instance that they own, they join the fed and not even announce meta's affiliation with it, my data is still zucc'ed.

I should've been more clear about my question, how would I, as a lemmy user, know if an instance has gone rogue (taken over by another entity, meta/fb/ig).

My actual worry is about an instance stealthily created by meat/fb/ig that is not identified as a threads instance/service. Say you have deferedated the fuck out of all known identified Meta created instance so they cant push trash content, then as an example:

an instance owner gets bribed and creates another instance to federate with established instances and gives control of it to FB. At this point fb/ig/meta know they'd just be kicked out again if they even peeped that they now own the inatance.

What is the trust model between instances, where/when does it break?

if the instance that meta now owns doesn't push out threads-content, they still have access to our data and I'll just be unaware of it and next thing we know we getting profiled from what we post in our private instances.

Thanks for this visual. I'd extend the question to:

Will facebook be able to create dummy instances that would federate with the large/established instances and take our information?

I know fuck all about this.

As for me this is what I can't follow too, i understand that fackbook cant be trusted, and the federation is based on trust between instance admins to not do something fuckey.

So our data and rights (my country was victim of CA) are unsafe when federated with threads, these are what people are saying.

what is stopping facebook from creating a dummy instance, not disclose it is theirs, and federate with the instances that rejected the known threads instances?

It seems to be an expensive hobby based on my initial searches in amazon. high barrier to entry but I think I can make it work in 2 years.

I do self hosting/de-googling/homelab but my daughter is too young to be involved in it, I think astrophotography would be a good thing for us.

I fell in love with the thought of seeing things beyond, my daughter loves learning about satellites and space trash (I'm not sure why exactly).

Thank you!

I agree with this, what I suggested is not a best practice, I should preface my post with that.

And I feel your pain! I get calls that are extremes, like people putting too much security where the ticket is "P1 everything is down, fly every engineer here" for an nACL/SG they created.

The other extreme is that deliberate exposure of services to the public internet (other service providers send us an email and ask us to do something about it, but not our monkeys, shared responsibility, etc).