Live data from Hacker News

Request for Technically Risky Projects

news.ycombinator.com

11–20 of 31 posts

Re: Request for Technically Risky Projects

#12
Way outside my field, but a platform for global climate management that links current actions to future outcomes and accountability to nations and companies would be very cool, assuming it is taken seriously by parties involved (which is an even harder challenge). This is technically hard, but harder still from a people perspective.

Re: Request for Technically Risky Projects

#13
post #8
post #5

Earlier quoted context omitted.

Let's hope that a well-constructed, well-behaved and well-participated argument forum maintained over long enough timescales can lead towards better outcomes for everyone. Best of luck with the project. You might be aware of it already, but just in case, the most progress I've seen in the area of web-based argument mapping has been Arguman ( https://github.com/arguman/arguman.org ). They're also following an open sou…

Thanks, I'm aware of it. There are quite a lot of tools in this space already. Unfortunately, many are unaware of each-other and therefore making the same mistakes and learnings over and over again. Looking at all these tools makes it clear how difficult it is to create one that actually "works". Most of the researchers at the canonical debate lab created their own tool in the past and are now discussing how a next-g…

Cool. In some ways, that sounds like the software industry in a nutshell, to be honest :)

Can you share a sense for what any of the core unsolved problems are? (I'd be happy to read a mailing list / previous discussions if there's too much background to be worth communicating in a comment here)

I've noticed that Arguman seemed to run into community management and spam issues. More broadly speaking there seems to be a societal challenge in getting people to trust and feel invested in honest debating and to accept best-known truths.

Re: Request for Technically Risky Projects

#16

A Laser Mosquito Turret for homes, that uses a directional microphone to home in on the target.I don’t believe that it would be difficult to build the laser part, but the difficulty would be in making it safe for home use.

https://photonicsentry.com/

Re: Request for Technically Risky Projects

#17

No one seems to trust vpns. I wonder if a VPN company almost needs to be law technology. All of our attempts at privacy is technically sound but lacks the backing of solid lawyers ready to hold it down. That’s got to be worth something.

So the implied trust due to legal backing through same ownership as a law firm?

Interesting.

Re: Request for Technically Risky Projects

#18
post #9

The "cold-start" problem of new social network sites

Apologies for the condescension, and with all due respect, building a social network is a bit neo Silicon valley frothy.

the idea of building another facebook is just...ugh.

however, a friend of mine has been working on a community site for fishing enthusiasts for years. it's _extremely hard_ to bootstrap a community site of any kind, even if it's not "social networking" per se.

Re: Request for Technically Risky Projects

#19
post #2

Creating a "Wikipedia of Arguments", one can refer to in public discussions. It turns out that this is a way harder problem than I thought. I'm in this space for some time now and am happy to talk about it. Relevant links: https://github.com/canonical-debate-lab/paper/blob/master/RE... https://www.societylibrary.org/

That is a brilliant paper, I expected it to be centralised around logical fallacies (which is how I view arguments/debates) but it goes into so much more detail around the nature of online debate.

It's interesting to dive into the factors that influence online debates; reputation, trolling, anonymity, echo-chambers, the hive mind, language barriers, commercial interests.... There's so much more to an online discussion than just the argument presented...

Re: Request for Technically Risky Projects

#20
I have two regarding embedded software stack,

1. Memory Safety C-language literally dominates embedded software stack, while every on knows it is not memory safe and terrible memory bugs will be found but not yet discovered.

2. Compile time The whole GNU toolchain take minutes if not hours to make, which makes CI/CD painfully long.

Post reply on HN