xani_

You'd get shit tuner if you do that. Ain't nobody got time to define scales on a fucking tuner

Well, there are also already at least dozen free ones that allow to buy ad-less versions

> I find the idea that $1 is a "hard sell" laughable, but unfortunately for software devs that is the world we find ourselves in when trying to monetize an idea.

and it's hard sell because you can just pick any of them, test to your liking and pay for one after using it.

I love how it just decided in the middle you should just move the kitchen to outside

Don't worry, various encoding format, containers and other crap got you covered on complexity.

Hell, just look at ffmpeg commandline if you miss some complexity in your life

It's 44100

> Having worked with ARM too I have to disagree. I found device trees really flexible and easy to get going.

... as opposed to not having to "get it going at all"?

how faster is rclone compared to s3cmd ? We're using s3cmd to sync some stuff for backup purpose (many many small-ish) files and performance has been generally mediocre

That's ridiculously expensive for that tiny amount of users

It wouldn't need single devops person full time job. But it would make more sense to just pay a company to manage the technical side for you

> I run an instance and I really have none of these problems. Keeping open applications off solves a lot of them, you have to ask me for an invitation and I’m not going to give you one if I think you’re going to be a problem.

You're not building social network then. Just a single isolated place. So obviously problems of running bigger social space won't apply as much

Well, you can probably easily see how this:

https://blog.alexgleason.me/trans/

would trigger some people

Wordpress have same problem of being slow POS that in addition needs to be constantly updated for security issues.

Hell, we even got one of our clients (we just provided hosting for some of their stuff) getting half-hacked while setting it up (they were not exactly the developer type). Half-hacked because we required app-to-internet traffic to be ran by proxy so the final payload didn't get downloaded on the server, hilariously enough.

Yeah, and there will be people that will just throw their porn collection there, hogging space on other people's drives for no good reason.

There is an option of dividing it between "publisher" (source) and "cachers" (caching whatever is recent and popular) but that only helps a little bit.

> Then there is the whole tragedy of commons: average seed ratios and streaming video players for torrent content shows that are not willing to contribute to the greater good.

Over 2 decades of pirating that has only been a problem for obscure and old stuff.

I don't see it being a problem in social network sense; you publish your stuff, if there is nobody wanting to look at it, seeds 1, leeches 0. Moment there is interest it propagates. It is of course problem if you want to see something archival that author is no longer in the network tho.

Well, it was true decade, maybe two ago. Stuff got faster and therefore cheaper too.

Server written in reasonably fast software on $10 (well, probably some extra bux in storage if community is image-heavy) VPS can reasonably serve tens of thousands of users in typical forum/blog/hn-esque format. Mastodon isn't but I don't doubt someone would rewrite it in something faster if there was a need for it.

Uh, no, it was always usability.

Insert any modern chat app and random user can drop a screenshot there trivally, do some basic text formatting, and paste code in nicely colored blob of text, all from comfort of single login in a browser. And now even jump to voice chat or video conference directly from it.

They can also look at what they missed in channel by just scrolling up. Sending files just worked. You just got notifications without extra fuckery. Hell, you get digest with conversations you miss.

That's why modern closed down chat ecosystems won. Coz it's easy for "normies" to use.

Let's take other example, XMPP. It had all that but in network of XEPs that some clients/servers implemented, some not, some just not very well, and some being fucky to config. It wasn't just "login here and get every feature" like it is in modern chat clients.

It had it's one shining moment where both facebook and google offered XMPP way into their garden so you could have connectivity across federation and just have a single contact list but that didn't matter to non-nerds that just used facebook/google talk so once they decided to close their gardens any benefit of xmpp faded away.

> You can either have a federation of commoditized servers or you can ban people you don't like -- you cannot have both.

That's not incompatible. You can go anywhere you want but you can get banned from place if you're an ass there is entirely sensible way for federated network to work.

More than that, it's necessary if you want any resistance to bad actors

Twitter is terrible medium for conversation in the first place so unless musky boi decides to completely reengineer it I doubt that would happen

> For example, you'd find that sysadmins are much more prevalent on Gopher than Twitter.

I'd say ratio of sysadmins to actual users of the service is good indication that something is dead

It's disgusting, really.

We manage this POS for some clients, and it's the worst distribution you can have. Stuff you can "just install" under any other popular distro is often silosed off into special packages you need to buy, despise it being OSS and "just available" on EPEL.

They already stopped building packages for Ubuntu for Ceph...

>to date it feels like all IBM wants to do with Redhat is turn it into IBM so if thtas all these juggernaut dinosaurs can do im quietly waiting to see Microsoft acquire Ubuntu and quietly turn it into a teams plugin the same way they acquired github and turned it into an outage response simulator for developers.

RedHat was eating into their business so they bought it.

Compare the speeds of both modes of transport

No more or less chance that really anything else connected to power to catch on fire. Just make sure RCD works.

Hell, some weeks ago my oven decided the lower heater's line is now connected to ground and blows fuses...

Our 8 racks in DC only had single event of something blowing (power supply) and aside of smell and fuse blowing nothing really happened

Servers are essentially metal boxes with a bit of glass-reinforced epoxy and some plastic inside so there is limited amount of stuff that can burn. UPS is probably bigger problem

For example the OVH datacenter fire was more of "stuff around servers was flammable" (they had wooden ceilings for some reason...) rather than "just" servers.

Homelab-priced sensor is the temp sensor in your server, it's free! Actual servers have a bunch, usually have one at intake, "random old PC" servers can use motherboard temp as rough proxy for environment temp.

Hell, even in DC you can look at temperatures and see in front of which server technican was standing just by those sensors.

Second cheapest would be USB-to-1wire module + some DS18B20 1-sire sensors. Easy hobby job to make. They also come with unique ID which means if you put it in TSDB by that ID it doesn't matter where you plug those sensors.

It always was for load that doesn't allow for autoscaling to save you money; the savings were always from convenience of not having to do ops and pay for ops.

Then again a part of ops cost you save is paid again in dev salary that have to deal with AWS stuff instead of just throwing a blob of binaries and letting ops worry about the rest.

Uh, no, that's even worse thing to give to the for-profit companies as indentifier.

Now they have country-unique ID of a person that will never change so it can be linked to a person regardless of where that person logs in

> This is the sort of performative response that is the problem. Let's say we force Google to switch off 2FA. Now we have exposed millions of people who don't know any better to phishing attempts and financial loss.

Could be just option hidden somewhere in the settings. Don't need to turn it off for all

> And the group we are trying to help isn't really better off.

That's just your assumption

Eh, I greatly prefer ability to move the very reliable thing from one phone to another, just use another phone instead of going into paperwork to move it if my phone gets damaged or something

> The idea that you want, need, should or will tie your identity to a phone number where people can always reach you is long outdated.

Yeah I have no idea why phones still use numbers. It would be so easier if same address for e-mail worked for voice, just add some DNS records that point at my phone provider to domain and done.

Then again, spam calls would probably be so much worse...

Yea till they add 2FA too...

> Gosh, I don't know, how about literally all of the problems that 2FA solves in the first place?

Well, it isn't solving this one. Option to opt out would be nice.

> aren't capable of keeping track of a physical device for more than N weeks?

Bit ignorant of you. They could be just plainly stolen by someone else. A piece of rag working as a tent doesn't exactly have best physical security...

> I'm not unsympathetic to the problems of the homeless ant the burdens 2FA entails, but I'm also not willing to ignore the huge problems the 2FA solves, and realizing there will often be a tradeoff between making it very difficult to hack into accounts and making it easy for people with mental and other problems access their accounts.

It's not either or.