skysight-inc/HackerNews huggingface dataset:
Does IPFS really work? As I understand it, it's sort of like a pay version of BitTorrent. In theory, you're supposedly renting space on hard disks of random users. In practice, you're probably renting space from AWS at a markup.

I was interested in IPFS as a possible asset storage system for assets for virtual worlds. Not for piracy, but as a way to sell virtual world assets with no ongoing obligation to host the content. You store the ownership on some blockchain and the content in some storage system with pre-paid "perpetual care".
I'd seen one offer at $5/gigabyte/forever.

The idea is supposed to be that Filecoin is a derivative of future declines in storage pricing, and profits on that derivative pay for the storage. Unclear if this works. There's one seller offering "perpetual storage" for a one-time fee. But their terms of service say "Data will be stored at no cost to the user on IPFS for as long as Protocol Labs, Inc. continues to offer free storage for NFT’s." No good.

(Just once, I'd like to see an application for NFTs that actually did something besides power a make-money-fast scheme.)
I wish I remembered what it was I was searching for, but I found a github issue where a repo admin directed folks to some chat website about a year ago; naturally, in the year 2021, the whole thing was completely defunct, and more recent threads pointed people to Discord.

I wonder what'll happen next year, if/when the Discord community fractures, or starts making certain channels private, or it's just abandoned and closed down.
The poll results show the real sentiment, that close to 30% of people actually like synchronous chat. That is a significant chunk.

Perhaps there's an unmet market need for a product that both excels at synchronous and asynchronous communication.

I could see potential for a feature in a chat program where a message or series of messages could be selected and enshrined in a search engine-indexed synchronous knowledge base page, working something like a more powerful version of a pin in Slack or Discord.

Overall, though, I felt like the article was kind of bossy.
"People will behave well if they think Big Brother is always watching so let's make them think that"

Remember when you could leave your house and not get recorded? I miss that.
A deep stain? No, I wish everything remained flat, it is exactly what design of software should be. (I can also state my opinion as fact)

But seriously, I do really love flat design. Though I do agree with some of the arguments against it.

A more varied design landscape is always better though.
I once saw a world map annotating the dominant dev stack in different regions, and yes, it's absolutely a thing.
I much prefer the Haskell / F# approach of using do-notation to allow the user to build their own syntax.

I don’t think I can build an Async<Either<E, T>> expression with Loom, for example.
This feature can be turned off.
The blog post says surprise bills rarely happen but nearly every company I've worked at that used AWS had surprise bills and had reasonably large projects to reign those bills in once they noticed the bills.

This is such a large problem for AWS users that there are multiple SaaS systems that help people manage their AWS bills.
"the first thing I looked for in the docs was authorisation controls/checkpoints."

We've got a component called the Assign Task that was pretty much built for this - its pretty flexible, but it is mainly used to create authorisation/control/approval/decision points in a workflow.

Here's an example for a process to handle timesheets: https://app.workflow86.com/template/812aaa61-8e00-414d-9898-...

The Assign Task component acts as a step where you can accept or reject the timesheet that has been submitted.

The Assign Task component is probably our most popular component and I'd be happy to show how you can use it for controls/checkpoints in your use case.

"Business processes are not static. I would like to understand how changes in process are managed."

All workflows are version controlled. This means that when a workflow starts, it is attached to a particular version e.g. version 5. This means if you make changes to the workflow i.e. update to version 6, the workflow currently in progress remains at version 5 so nothing breaks. We are looking into the possibility of migrating in progress sessions from one version to another.
“At this time, we understand that the unauthorized party obtained a list of email addresses for approximately five million people, and full names for a different group of approximately two million people. We also believe that for a more limited number of people—approximately 310 in total—additional personal information, including name, date of birth, and zip code, was exposed, with a subset of approximately 10 customers having more extensive account details revealed. We are in the process of making appropriate disclosures to affected people.”
Seems like a reddit joke

Previous discussion https://news.ycombinator.com/item?id=15596253
I agree with the fact that Slack/Discord are terrible for keeping track of things long-term, but I will say that once you've set Discord/Slack up and running, operating it is typically pretty smooth - you've already likely got Slack and Discord running, and you can check it every so often.

Granted, things can completely explode, and moderation is still a requirement, but that's true of forums as well.

(Although due to their async nature, things boil over much more slowly, and it's typically easier to just put the entire forum or a user into a timeout.)
Assuming one has an appropriate PhD in math/physics, what other kind of general knowledge questions would you be asking people in an interview? For example, I've read that one should learn modern portfolio theory before going for an interview. Is this sort of thing true, or would that be a waste of time?
They updated the page now:

> If you see agge, he leaked my password. He is enemy numba wan
For anybody else who didn't know that was trivial

> “As to what are the medical and biological effects of that, with such low doses of radiation, it’s very difficult,” Litster said. A child exposed to that kind of dose, he said, would have a one in 2,000 chance of contracting cancer, which was barely higher than the average rate. A 1994 Massachusetts state panel concluded none of the students suffered significant health impacts, and radioactive tracers continue to be used in medicine.
I'm absolutely in love with the new completely psychotic web3.0 design trend. Reminds me of when the internet was properly weird.

I guess we millennials are coming of age.
I'm very aware of the proliferation issue. To be clear, I have worked in the nuclear space.

But that still doesn't mean that fears of proliferation would have disappeared if we had a larger reliance on nuclear power.

Those countries weren't said as examples of countries without nuclear power. They are examples of countries that have it but still likely wouldn't have had any exports from the US. I thought the Pakistan example made this abundantly clear. Maybe I confused people by including Brazil, but there was pressure on them during the cold war.
I think it's a reasonable assumption that US fusion companies would have the same patent policy as SpaceX.

Elon is quoted in HBR, “We have essentially no patents. Our primary long-term competition is China. If we published patents, it would be farcical, because the Chinese would just use them as a recipe book."
On a not unrelated note, Kate Brown has been under fire for Oregon's awful HS graduation rates. While all of the changes are being made as "a response to the pandemic and a reassessment of our current graduation requirements"...it all stinks of gaming the numbers so that it looks like graduation rates are better than they should be.

https://www.oregonlive.com/education/2021/01/oregon-graduati...
Where did you find an astrophotography community full of assholes? I'm fairly new and haven't seen much problems. Feel like online it's been fairly easy to find info and ask questions
Market makers also typically make money on their spread, paying slightly under market rate for an asset and selling for slightly over. They can do this in, say, stock trading because people want to make trades right now to capitalize on moment-to-moment conditions, so that's the price of convenience and liquidity.

Zillow SAID they wanted to be a market-maker, but they ACTED more like a flipper or investor, expecting to make a profit on the houses themselves, not just on the spread. When they started making above-market offers on homes they pretty much left any pretense of market-making behind: at that point, you need to either sell at a loss or hold inventory and go (a little) long on your investment. Zillow realized they didn't want to hold inventory.

It doesn't help that houses aren't nearly as liquid or fungible as stocks: buying a house, prepping it for sale, accepting and offer, and closing takes months, and all that time can eat into your spread. Zillow would probably always have ended up in a situation where they were more concerned with the sale price 2-4 months down the line rather than their spread.
I did it the other way around putting Esc on CapsLock for the whole system. But yes, Esc is a pretty horrible key to reach for, especially considering how often it is used when interacting with vim.
The poll is not exactly lined up with the point, though: it says that people want synchronous chat, while the article says synchronous chat is not beneficial to the community. Both can be true.
Thank you! If it takes off, I'll consider adding Linux support. Until then I want to ship high quality experience for Mac, rather than subpar experience for everyone. ;)
"success" of the drone "industry"
The difference between this and openapi code generator (I think) is that I made a few specific decisions in the builtin templates that help get internal business apps off the ground faster. But since it's designed around a template system you could do whatever you want with it. And of course openapi is much more mature just generally speaking.

It's different from PostgREST in that it doesn't dynamically read schemas from the DB during the application server runtime. You generate an application from the DB up front and then you can do whatever you want with that generated application afterward.
Not OP. I think the brain is more a receiver of consciousness than a generator, and there are many types of receivers, beyond neural cells.

Trees will form a network with the cooperation of fungi, to exchange information and nutrients among each other. Plants will grow better when they are planted with companion plant, or cultivated in guilds (https://en.m.wikipedia.org/wiki/Guild_(ecology)
Regulatory capture kills people, but unfortunately the legislative equivalent means there's not much will to fix it. In this case though not only was there regulatory capture, but J&J and their talc supplier conspired to deceive the FDA. I have little hope the lawsuits will extract more from them than their added profits.
> His legacy is a deep stain on the design industry

This is a rather extreme statement. A person's career can be long and complex, involve many projects, not all of which will be successful. We all learn.

From the outside, it seems that Jony Ive was successful in a lot of endeavors, was successful in creating a disciplined design culture, and yes, sometimes, went too far (it seems) but even that kind of exploration can be useful for how it informs future work.
I would love if something like this existed except it used a .proto as the source of truth and had a way to provide ways to rename/query certain fields.

Would make it easy to replace shared DBs with APIs over time.
Howdy! I'm the author of PhotoStructure.

Hierarchical tags are fundamental to PhotoStructure! Read more here: https://photostructure.com/faq/whats-a-hierarchical-tag/

Any change you make to your assets in the PhotoStructure UI is stored both in your library database as well as either within the file itself using standard EXIF/IPTC headers, or as a standard sidecar format (like .XMP or .MIE), to ensure your work isn't wasted if you migrate to another tool in the future. More details are here: https://photostructure.com/faq/system-of-record/

I'm happy to field any questions about PhotoStructure or metadata Management in general, either on the forum or on discord (links on the website).
Yeah I could see in a few year Discord/Slack having "chat" channels, voice channels, and "forum" channels. Maybe even add in wikis, or dashboards.
New AMD Instinct MI200
Basing things on source IP is really inexact and easily muddied, though. For instance, the source IP is a workstation or a laptop—now we have to go through DHCP logs to figure out who had that IP address at the time the incident occurred. Or if we've properly implemented source limitations through a bastion host, all we'll see on the end server is the source IP of the bastion host, so we'll need to go to the bastion to figure out who was logged in at that time and what they were doing—hopefully there was only one engineer logged in at the time! And that assumes they didn't just SSH-jump through, in which case we just have the transitory SSH logs...which leaves us with the DHCP problem above unless they used their own userID to connect to the bastion itself. If it's a publicly available AWS host (which...oy gevalt), was that login from "dhcp-host-X.Y.Z.Q-suspiciouscablehosting.regionalisp.net" a hack, or an engineer trying to fix something by logging in from his home Internet connection?

Ultimately, it's just much easier to force individual logins and require sudo. Even just an engineer logging in and doing 'sudo su -' is significantly more traceable than everyone logging in directly as root. Even better if you can force the individual logins and sudo sessions to use multi-factor auth—then you can keep root non-multi-factored and get in with just a password on the console when your MFA solution has gone pear-shaped. :)
You can't move fast and break things with fences around.
I've usually seen this done with colored dot stickers affixed near to or on the library label on the spine of the book.
I prefer limiting to DJB ciphers where possible (the AES-GCM suites might also be helpful, but otherwise anything below is legacy crypto):

Ciphers chacha20-poly1305@openssh.com
KexAlgorithms curve25519-sha256@libssh.org

AFAIK, if RSA is off the table, then the moduli file isn't necessary.

RSAAuthentication no

SFTP-only accounts are advised in "SSH Mastery" by Michael Lucas to follow this form:

Match Group sftponly
ChrootDirectory %h
ForceCommand internal-sftp
AllowTcpForwarding no

I'm still seeing the external sftp subsystem in latest loads (last seen is Microsoft). Internal is better, and required for chroot.

Subsystem sftp internal-sftp

I like to put SFTP users on a separate server, just for them, and turn some other things off:

PermitTunnel no
X11Forwarding no
PermitRootLogin no
AllowTcpForwarding no

Those are some settings that I would prefer.
I'm an EU citizen as well as an American one. If you go to the suburbs in the outskirts of Paris, you will see what I am talking about. (the so-called "banlieue")

The US is going to have more obvious poverty also because they are more accepting of immigrants from impoverished countries.

> Look at the average lifespan of an EU citizen that’s almost 10 years longer than an American citizen.

Laughably false. A 10 year difference would be ridiculous!

You can look up everything that I am talking about. The (non-European) immigrant communities in Europe are incredibly poor, but kept out of sight because European development models involve affluent city centers and pushing minorities out to the suburbs, rather than the reverse which occurs in the US.

The US certainly has problems with these sorts of things, but headlines like:

https://www.newsweek.com/french-activists-39-percent-paris-t...

or

https://www.connexionfrance.com/Archive/Clubs-accused-of-rac...

are something unimaginable in the West outside of Europe.
With DD you can set up monitor downtimes in advance of expected anomalies. Also, at the beginning of the month costs can drop suddenly, so what you can do is set up separate 'over' and 'under' threshold monitors, and then set up downtime on the 'under' threshold at the beginning of the month.
Not an RF engineer, nor even electrical engineer, but from what little I know, if you think computer networking is voodoo magic (as I do), RF design (especially in tiny couple-mm-square chips) is like black arts mixed with ancient mythology.

RF does weird things, and controlling it so it can be useful for high speed networking in the wacky environments where we put computers is IMO a pretty big feat of modern engineering.

But the chip design is just pretty in its own right, with the layers coming through.
"You could have a compromise, so you don't accidentally fund eugenics or something."

The thing about basic research is that you usually cannot see the consequences down the line.

Few of the original researches that discovered ionizing radiation could anticipate the enormous destructive power of nuclear weapons. And yet their contributions were crucial.
"Put your oxygen mask first, before you help others."

Focus on yourself. Figure out what brings you joy. Follow it. Work hard. Don't complain. Be kind. And once you have something to share, offer it to everyone around you. Anonymously, unconditionally, shamelessly.

Many people seemed convinced that voting is a significant part of the solution. I disagree. Be the best version of yourself and then share that wealth with the ones around you.
> But the authors just jumped at the "autoconf/cmake" bandwagon, because they probably were never familiar with make, or just want to follow conventions (which is ok, I guess).

I'd personally recommend everyone use autoconf or cmake (or even better these days, meson) over straight make for the "conventions" purpose if anything. It's very easy to forget build system features that downstream linux distributions and package managers rely on. This includes but isn't limited to setting installation paths (this includes bindir, sbindir, libdir (especially important for multilib), and even mandir, docdir and infodir. don't just assume they're under share/ or share/ even exists!), proper cross-compilation support/detection, inheriting CFLAGS and other variables to set the path for certain programs, and a lot of more minute details.

It saves a lot of time downstream when all the packages can be built using the same script, as a lot of time is wasted on patching custom build systems. Even autotools and cmake (and meson) aren't always perfect at preventing developers from breaking one of their features through e.g. hardcoding/misuses of features, but it's at least less common, as they provide the mechanisms to conform easily.

Hell, even if you use a regular makefile as your "main" build system for personal convenience reasons, it's very appreciated if you can provide at least one of autotools/cmake/meson as an alternative for your friendly neighbor distribution maintainer, lest you end up with a perl-cross-make situation[1].

[1]: https://arsv.github.io/perl-cross/
World’s Top Chipmakers Provide Data to U.S. as Deadline Arrives
Any technology or way of thinking is part of a series of overlapping S-curves in time (https://pratt.duke.edu/sites/pratt.duke.edu/files/Layered%20...), during which the majority switch from one dominant regime to another; some technologies are on their ascent, some ways of thinking are near their peak and will soon decline.

If you can see through the hype, blockchains distributed across jurisdictions and organizations really do solve real problems for real people. Denying that is only putting blinders on. Maybe you don’t have those problems yet, maybe normal people don’t have those problems yet. That’s great, but it’s a snapshot in time; it doesn’t say anything about the dynamics of the systems involved, or what people will want in the future, or how and why that might change.

This is especially important to keep in mind when reading the prognostications of a futurist like Kevin Kelly.
I sympathize with the post you're replying to. Mostly because butts are about face level in these situations and people don't seem to realize it would be more pleasant for others if they'd angle them away from faces.
A common narrative but also wrong. Even when we take into account the externalized pollution the US and EU still have lower emissions compared to 30 years ago.
87 % of China’s emissions is caused by their own needs. 13 % for playing factory of the world.
Asia has a lot of people, no surprise they pollute a lot.
I got a very surprising bill from GCP. I used bigquery to query the google public patent database[1]. I thought I was using enough predicates for it to effectively be a point query (using patent ID, etc).

Turns out each single query was a full table scan of the 4TB dataset and cost about $5 each! I luckily stopped after 4 queries once my curiosity was satisfied, but I could have easily spent hundreds of dollars. It wasn't until some time later I saw my bill and realized what happened.

They did do a "one-time charge reversal" for me. I didn't really feel satisfied with that response. I wanted them to admit such datasets are a huge liability for users.

1. https://github.com/google/patents-public-data
Interesting how many languages are in here, HTML/CSS/TS on the front-end is no surprise, Go on the generated back-end is a little less expected than full-stack Typescript. The fact that the tool itself is in F# is really interesting. I kind of expected it to be some combinations of the others.

This is really cool. Poking around the source code, it's surprisingly simple. It's just a database -> template engine with a front-end/back-end template included.
> Perhaps there's an unmet market need for a product that both excels at synchronous and asynchronous communication.

The Rust community has had great luck with Zulip for that. It works well live, as well as asynchronously, and the content remains useful and findable later.

(We also have forums, which serve a different purpose (longer content), as well as GitHub.)
System76 publishes all their drivers in AUR. I hope their new shell will be distro-agnostic as well. Godspeed System76!
I remember when I used IRC to speak with developers of products. Everything felt temporary. I wonder if I still have any of the MIRC logs hanging out in a backup somewhere…
Kudos to the author for including exercise in this list.

Would also suggest it's worth considering a 5 or 10 minute meditation in the daily routine.
They do care about 1 thing and thats Pegasus source code.

A Senior Engineer of theirs got caught and jailed trying to sell it for 50 Million Dollars[1]. I assume they don't want their index of exploits leaked

[1]https://www.securityweek.com/ex-nso-employee-accused-stealin...
Dev teams also benefit a lot from having an async way to discuss bigger issues that require thoughtfulness and long form answers, especially remote teams. There's a reason mailing lists are still somehow alive and well in open source projects that have been remote first for decades.

We're using discourse internally for this (in conjunction with matrix) and it's allowed us to have discussions I don't think we would have otherwise had.
Why are there so many private keys in repos? It seems preferable to just generate them when needed instead of risk one being misused
Google Cloud does this with new trial accounts, there's a very explicit step between free and paid services.
To some extent, for a fair comparison, you should also use old sole panel efficiency here. Nuclear power plants have progressed tremendously in terms of safety.

There’s also widespread reporting that the evacuations and exclusion zones, in Fukushima at least, were excessive.