Does he WANT worldwide eternal Jihad against the US/West?
If there's a better use for "Some people just want to watch the world burn" in the history of the world, I can't think of one. He's always been a toddler brain clueless to consequences and, in this case, he likes the idea that HE would get to be the Big Boy to push the Big Red Button. Fun toy.
- I'd like to see this as a hosted app versus something that has to be "installed" in a chatbot.
- It needs a text search feature for both the outline and full text. That would allow searching for text containing "government", highlight instances and seeing their context. And same for searching the outline for "government" and seeing supporting text.
This could be an equally useful paradigm for fiction and for source code. For fiction, it would be really useful if this could be trained to identify character introductions and locations and their mentions. Imagine how convenient it would be for the outline to mention a plot point about "Mary Sullivan" where the paragraph in chapter 22 only says "his mother" when talking about "John Sullivan."
I've thought about a hosted app and it's something I'd like to do eventually. The API costs and building a reliable service make it a bigger project though, so it's not happening soon.
Text search is a good idea. It makes reading more active because you pick a concept, see where it shows up and how it fits the structure. The fiction use case you mentioned is similar in a way, finding where a character or concept appears even when the text doesn't use the exact same words. I'll look into it.
At minimum, you have to provide a snapshot/example of what you're building.
I'm most intrigued by your comment pile digestor. I've often wanted something like that while cruising the Internet but I'm not sure how'd you monetize it. In the commercial world, software for analyzing customer-submitted questions and comments has been a valuable service for a long time, even before AI/ML engines came along. So, that's useful but it's a hard problem, very domain-specific.
Anyway, as others have said the main things you have to do to attract interest/business are: 1) Explain specifically what pain you are solving for what specific user/customer, 2) Offer specifics (examples, features) of how you solve that pain better than anyone else.
I agree with you this would be valuable, mostly for persuading the general public.
The skepticism you're getting amounts to "biased people/government won't care no matter what" and "fancy tech makes the evidence look more doctored, not less." They're not wrong but there are some disputes this could settle. Some people have argued that the moment where an ICE agent appears to withdraw Pretti's gun might just be him retrieving his own fumbled gun. Maybe a synthesized view could clear that up.
Personally, I think it will come down to the moment where one goon said "He's got a gun" and another one took that as license to shoot him three times. The other 6 or so gunshots were a kneejerk pile-on to that cowardly act.
So much for the 2nd Amendment, right?
Right, the analogy would be "What does being a builder mean if carpenters are swinging the hammers?" We'll have to be software "Foremen" who develop plans and know enough algorithms, data structures and architecture to tell the AI how to frame the house and what kind of pipe to lay even if we're not doing that ourselves.
I'm intrigued and might need something like this but...
Your splash page doesn't give much of an idea of what this app does (far less than what you said in the comment above).
IMO, I shouldn't have to create an account to see what an app has to offer. A few screenshots and a feature list might help me decide if creating an account is worth the trouble.
In general, how is this better than a spreadsheet of contacts or the contacts app on my phone?
A valid critique of our landing page. We will get some screenshots on there.
What is the problem we are trying to solve? Contact data is stale the moment it is shared.
You might use your phone's contact app, or a spreadsheet, but how do you know that the details in your phone/spreadsheet are still accurate? And how do you know that other people's spreadsheets have YOUR accurate details?
What we are trying to do is turn contact details into living data. EasyDex is the infrastructure to propagate contact detail changes between users and businesses securely, seamlessly, and instantly.
Your only operative complaint is "confused." What are you confused about? The high-level goals and requirements? Your own approach and criteria for success? Structuring your time/effort?
Without knowing what you are asking exactly, there are a ton of ways to structure a large project.
One of my favorites is: Pick some challenging (but not too challenging) use-case that intersects an interesting subset of the core requirements. Decide on ONE design principle you want to follow (highly testable, clear separation of concerns, pluggable sources/endpoints, whatever) and then build the crappiest/minimal version that does those two things (handles the main use-case and strictly adheres to your design principle) while being totally crappy in every other way (i.e. bad UI, brute-force algorithms, whatever).
As you design/build this "slice"/MVP of functionality, keep notes about out-of-scope parts you can't/won't touch according to the rules above. Those will become seeds for the rest later.
This method yields a lot of advantages: 1) It provides a way to get started without analysis-paralysis, 2) it results in proof-of-concept, perhaps a demo for what you are going to eventually build, 2) You think through a lot but don't build so much or get lost in details you won't build, 3) If you hate the MVP, you can throw it away and build it again the right way (which will be better, as a result).
For a really big project, just iterate on the above by picking more slices/use-cases. You might have to refactor/redesign as you go but pretty quickly you'll have built up enough scaffolding that the rest of the project will flow easily or be delegated easily.
reply