this post was submitted on 15 Jul 2024
1973 points (99.5% liked)
Technology
59588 readers
3397 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think NZ's is a similar story. GovHack is run in NZ as well, though I haven't personally been involved in an event.
A decade ago I participated in three and won several awards but was disappointed with the government response to all our collective efforts and stopped participating.
Specifically "not invented here" was prevalent as a response to projects that represented hundreds of man-hours of effort.
It was demoralising to say the least.
I'm not sure what the missing ingredient was, but two of our projects were directly related to government effort in relation to public transport and public housing. Neither went anywhere despite face to face presentations to senior stakeholders in the relevant departments.
The third was a search engine with a completely different approach to that in use by the popular engines.
That sucks. What was the novel search engine approach?
Using the idea of six degrees of separation to get to any person on the planet, I came up with the idea to use a word cloud that would represent the top N words in all documents.
When you click on a word, (say "alpha") the resulting word cloud would represent the top N words for all the documents with "alpha" in it.
As you click, bravo -> charlie, etc. the list of documents gets smaller and smaller, until just your required document remains.
This has several advantages, you don't need to distinguish between words and numbers or need to "understand" the meaning of a word or interpret the user intent.
More importantly, the user doesn't need to know the relevant words or vocabulary, since they're all represented in the UI.
Enhancements include allowing for negative words, as-in, exclude documents with this word.
Ah that sounds really interesting! Does it scale OK? I guess you could index at a word level and filter quite quickly for quick searches, but it seems you're going to have to store the full text of every website?
You store just the word count for each word on each URL.
The search is pretty trivial in database terms since you don't need to do any wildcard or like matching.
Ah of course!
I guess one of the things the Google originally solved was that the internet if full of crap and not all sites should have equal weighing. With AI spam sites these days, you'd probably also need a method of weighting results?
We never got that far to test that kind of issue and while I've been reimplementing it locally to search through employment advertising, I'm not at a point where I'd be able to test such a thing.
The original implementation used a data store written by another team member and it made the original project much too complicated.
Today I'd likely use duckdb to implement it. My local version uses text files for a proof of concept implementation.
It sounds like a really cool project regardless!