Well the obvious answer there is that port scans shouldn't be considered abuse absent other factors like rising to the level of a DoS.

Exactly this. A single SYN or TCP connection doesn’t constitute abuse.

Unfortunately many people seem to think otherwise and will spaff abuse reports over an errant SYN packet

If you scan a bunch of my ports and you aren’t on my LAN then your IP gets banned (ignored) for a week.

Go for it. But I don't see the relevance to the comment you replied to?

That isn't going to handle possibly conflicting changes from more than one source.

Whatever you may think of what OP's buddies were doing, there is no way to apply any reasonable meaning of the word "stealing" to it.

There is indeed plenty murky here, and it is mostly coming from you in an attempt to incorrectly use an emotionally-loaded word in order to deceive people into supporting your position.

> emotionally-loaded word in order to deceive people into supporting your position

That's an entirely colourful way of phrasing it, considering I merely just said what I thought and have experienced, nor do I think I have the capacity to deceive at such a level. That is your opinion, and I accept it.

> Plus, if you don’t like it, reconfigure it. It’s only the default, after all.

Or -- and I know this is crazy but hear me out here -- if you don't like it, and it brings nothing but problems to the table, just don't use it at all.

What problems?

For me, literally everything it does is a problem, including:

The file format is not text, and I use it under Linux, which is good at processing text files.

The command line arguments are insane.

Bad handling of log lines emitted at system crash.

Broke an entire prod network’s observability stack because ubuntu replaced syslogd with it in the middle of an lts support cycle.

Brings in a systemd dependency, which causes 100x more problems than this.

> For me, literally everything it does is a problem, including:

That makes it sound that your main problem is the fact that it exists.

> Broke an entire prod network’s observability stack because ubuntu replaced syslogd with it in the middle of an lts support cycle.

That's more ubuntu's fault I guess. I don't really remember this happening though.

> Brings in a systemd dependency, which causes 100x more problems than this.

Is it other made up problems or real things?

Xmonad integrates nicely with xfce and MATE, at least. Probably KDE as well.

Here's not only the IC but an entire development board for $0.95: https://www.aliexpress.us/item/3256805283269799.html

cool, I guess we can go make lightsabers instead of badges...

Android supports this but as usual with Android, it's shoddy and broken.

For example, if you log out of a secondary profile and log back in, all your widgets will be gone. I don't have the bug link handy but IIRC, it's been open since 2021.

I am having a hard time understanding how you could even ask for all this personal information with a straight face for an app like this. In fact why would any kind of account at all be required?

Given the apparent simplicity of the app I don't see any other conclusion than this is a pure and shameless gimmick to collect this information from people.

As far as I can tell this can be replaced by a plain text file of suggestions and a random number generator. Of course I'm not sure about this since I am never going to never going to submit to the requirements to find out.

Well you can't expect to hire engineers with half a brain for the pitiful compensation Meta offers, can you?

Beyond unbelievable that going on an hour later, they're still showing "incorrect password" errors. How many hundreds of millions of people have wasted time frantically trying (in vain) to reset their passwords and pointlessly freaking out that their account might be compromised? What a bunch of careless, incompetent excuses for engineers.

Blame the managers and product owners that don't think this is an issue, not the developers that likely raised it a million times already.

Imagine how many hundreds of millions of users waste their time using instagram and facebook on a daily basis. Safe to say they don't mind wasting their customers time

This is your regular reminder that the users are not their customers. Advertisers and media outlets are the paying customers.

What a poor bunch of overworked human beings, with almost no control over the product they work on. Frantically following the whims of managers, reduced to labour units in this late stage capitalist hellscape.

But well paid at least. Working at Meta seems pretty shitty except for the pay from the stories I have heard.

It probably depends what team you're on, but I would not describe it as "pretty shitty." Being oncall for a 24/7 service sucks, yeah, but for my team it is one week a quarter and I haven't had any outside-of-biz-hour alarms the last few shifts. Other than that -- my work is challenging and interesting, my colleagues are friendly and smart, and my manager is decent. Not a lot to complain about.

That's such a beautiful comment I would almost consider printing it and putting it on my wall

Major outages are periods of intense stress and extremely difficult to operate in. The folks troubleshooting may be many things, but careless and incompetent are unlikely to be among them.

I can almost guarantee you're getting mercilessly downvoted because half of the people here are sympathetic Meta worshippers who desperately (1) wish they worked there and (2) know they'd probably contribute similarly to this same horribly engineered system.