chockchocschoir

No, you're misunderstanding the feature (or they don't explain it well). GitHub solves the problem on their platform yes, but not in the protocol (git) itself.

Fossil embeds that data in the repository, all the data is local. Fossil works perfectly with the "local first" doctrine, something Git also does, but not for everything around Git, that Fossil embeds into the repository.

Basically, Fossil is Git + GitHub but self-hosted and offline first. You pull down a Fossil repository is like pulling down the Git repository + all related GitHub data.

> Why would VCS experts be good at designing a compelling forum or ticketing system?

They don't have to be experts about something to make it good enough. For a lot of us with poor internet connectivity, the offline first doctrine is essential in a lot of the work we do, as internet can disappear at any notice. Fossil works much better for this, as I can still read the wiki and tickets when my internet drops, while if I were using GitHub, I'd have to results to writing my own code/use 3rd party software to get the same experience.

Also, chose a registrar that won't just terminate your account over nothing (like Google is famous to do). I've had good luck with DNSimple over the years. Sign up for their enterprise plan and make sure to stay up-to-date on their policies. If you see that they start acting "googley", start thinking about moving to another one.

Are you trying to secure it against someone transferring the domains out of your account? Make sure you have all the account security up to date and correct (2FA on the account + the email account that has the ownership), and that all the "transfer locks" are setup (EPP codes and so on)

Are you trying to secure your DNS setup against various DNS attacks? Read up on DNS and various security patterns you can implement like DNSSEC and so on.

You're trying to prevent issues regarding DNS uptime (in case the main domain stops resolving, or other system problems)? In that case, setup DNS over multiple TLDs (and registrars) and have a process for failing over.

In short, it depends on what you're trying to protect against, and who you are trying to protect it against.

PlayStation and Xbox do aim for best graphics with the best hardware though, so they are more likely to go with this than anyone else.

There is an easy way to solve this problem. Default to auto updates, allow people to turn it off, by acknowledging what that means. Most users use whatever is the default anyways. Vendors gets to push their updates, users who don't want those, can reject them. If someone gets hacked because they turned off auto update, the vendor won't be on the hook for it, because the user said they were aware of it when they turned it off.

I think the core problem here is not that people are asking for auto updates to be off by default, they simply want to have the option. And frankly, for professional use cases, you have to be able to turn off auto updates, as otherwise it'll harm the workflow as you can't control when the update happens.

It's not dumbing down to link directly to a trusted source of the data itself. Feel free to use both sources, like I did. But if you want to avoid Twitter and the videos anonymous usually bundles with their announcements, DDoS is a good distraction free source.

Made a submission about it (the data) here (before I found this submission): https://news.ycombinator.com/item?id=30810275

???

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

Also, hardly surprising that Russian state entities are getting hacked and having their data leaked, since the day of the start of the invasion, everyone and their mother is trying to hack Russian government organizations.

Yeah, of course, everyone knows this, no one thinks it's some magic storage. That's not what I'm talking about.

The difference is in the interface on how you get your files to some place. With S3 you simply upload the file, and Amazon stores it for you. With Filecoin, it's simply a protocol that allows you to browse everyone who is compatible with the Filecoin protocol, then you make a deal, then you use that deal to upload files. It's like there are many operators like Amazon providing a S3 interface, but first you need to find one you like, then strike a deal.

The workflow is vastly different.

But I never said it was "free hard drive space", I explicitly mentioned "deals with people who offer space".

No matter where the data is ultimately stored (in a data center or not), the method for you getting your files to X is not the same in Filecoin as in S3. With S3 you simply upload your file to S3 and you're done. With Filecoin you need to first make a deal with a miner, then you use that deal to store files within the deal you've made, which is vastly different.

Not sure why you would compare it to cloud storage, because it's not. Storing files in Filecoin is more like making deals with people who offer space on their hard drives (which as far as I know, doesn't exists besides Filecoin). It also doesn't make sense to compare it to something like S3 as again, it is not cloud storage.

Nice!

> Of course, some platforms ban you for using alternate clients.

Less nice... Doesn't seem like that list outlines which platforms will/could ban you either, which makes the entire list a no-go for me, and I'm sure others.

A more successful example of open standards would be the various standards that browsers use. Would you say that browser innovation has slowed down? The model adopted there is less "Wait for everyone to adopt this new standard we wrote" and more "If you have a feature you found many people are using, suggest it as a standard and we'll get all browsers to implement it".

This model could be replicated to messaging solutions as well, without slowing down any innovation as companies can add new features, as long as they get standardized over time.

    fn classify-toxicity(text: string) {
      do_work(text)
      while true {}
      // this should never happen
    }

Just because one uses one of the ways doesn't mean they are not aware of the other way too.

The benefits of distributes systems becomes bigger the larger the network. Replicate the same results with 100 nodes and we'll see.

I still think torrents would be even more efficient though, than both FTP and IPFS.

Specifically:

> What to Submit: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity.

Is what you're submitting something "good hackers would find interesting"?

I submit links in the hope of sharing some novel/interesting information with others, and to spawn discussions around a subject I find interesting.

> but beyond that does it really translate into commerce and connections for people ?

Sometimes, for some people, it does. But still, rule #1 is that it should be interesting, then the commerce and connections (from HN and other sources) will follow automatically.

Besides, it's not like the NSA doesn't have the capability to scoop all packets from people they've seen visited torproject.org.

> I think the issue is not with it being social in general, but rather with it becoming a similar flavour of social to the likes of Facebook, Twitter, etc.

I'm sorry I didn't understand you were using "flavour" to indicate AI, I just thought you were referencing social features in general, it wasn't that clear to me, sorry for that.