3 ms·
The site's definition of "content-first suckless" is more or less synonymous with "created before 2005". Which is fine if you are into that aesthetic, but it is
by paxys 4y ago
The site's definition of "content-first suckless" is more or less synonymous with "created before 2005". Which is fine if you are into that aesthetic, but it is a terrible way to judge the value of the content itself. A few lines of CSS to set sensible margins, spacing and text contrast isn't the end of the world. Heck even Wikipedia is not "content-first" enough to be included in the results. And it doubly sucks for those who are expecting the tiniest bit of accessibility on the internet.
- marginalia_nu 4y agoPlain HTML typically has great accessibility. Its when you start adding CSS and scripts it worsens.
- paxys 4y agoTry using a screen reader on a website that uses HTML tables for layout and you will quickly realize how wrong that statement is.
- marginalia_nu 4y agoEh, can work pretty well compared to CSS. Table cells are always in the order they appear on screen, and if you read them in sequence the order makes sense. That does not apply with CSS based designs.
- LastTrain 4y agoOK, but go try a screen reader on a sampling of both kinds of sites and you will quickly find out that what you think is true is wrong.
- CJefferson 4y agoWhat damage does CSS do to screen readers and accessiblity? I've used several accessible browsers it has never bothered any of them.
- marginalia_nu 4y agoCSS can completely change the position and semantics of a tag. Floats, z-index and position:absolute/relative are especially tricky.
- colinsane 4y ago> Heck even Wikipedia is not "content-first" enough to be included in the results. try searching “wikipedia” on wiby before claiming this next time, thanks.
- paxys 4y agoWhat set of Wikipedia articles are indexed by this engine?
- colinsane 4y agoif i understand it right, whichever Wikipedia articles users have submitted will (usually) be indexed. i don’t know that there’s an API to query the index set, or not. i submitted the Wikipedia article on The Experience Machine an hour ago, so i’m watching to see if that’s approved (it’s not instant). given that the Wikipedia article on PAL is indexed (i see it when i search “wikipedia”), i expect most Wikipedia articles are acceptable and it’s just a matter of which ones people (like you) will have submitted.
- colinsane 4y agotangential to your question, i think it’s worth pondering what makes (or would make) a per-page moderated/curated search engine like Wiby valuable, though. Wikipedia articles are easy to find. they’re all generally good quality. you don’t really need a new search engine to make Wikipedia more accessible. Personal websites, on the other hand, are a mixed bag. there’s a tremendous amount of worthwhile stuff out there, where one page might explain how to solve a niche technical issue and the adjacent page might just be the author sharing photographs of a recent hike, or their wedding, etc. currently, both of these pages tend to be low-ranked on most search engines. i believe one prospect for Wiby is to bring the former to prominence. it’s definitely not a general-purpose search engine like Google. but try searching “raspberry pi” or “home automation”. on Google you will get pages focused narrowly on products: where to buy rpi’s, a dozen different home automation brand webpages, etc. on Wiby you get blogs documenting things people built related to rpi or home automation. it could be something like a search-based, topic-agnostic Hackaday. it’s not perfect. it only has a few relevant results for each topic. but there are certain specific types of results which are near impossible to find on Google but can be found on Wiby. maybe that can be valuable. maybe it will fade way. i won’t forecast the future, but i am intrigued.
- anikom15 4y agoIf you want Wikipedia just search Wikipedia. I don’t need the first page of results filled with sites I already know about. Why does Wikipedia even need to be indexed at this point?
- wibysearch 4y agoThere is a threshold for how much css/js gets loaded. Exceptions made for side wigits on a page, and web forums. I've found myself confused by this: https://en.wikipedia.org/w/load.php?lang=en&modules=ext.cite.ux-enhancements%7Cext.quicksurveys.init%2Clib%7Cext.uls.common%2Ccompactlinks%7Cjquery%7Cjquery.makeCollapsible%2Cspinner%7Cjquery.spinner.styles%7Cjquery.uls.data%7Cmediawiki.toc&skin=vector&version=lm4sa https://en.wikipedia.org/w/load.php?lang=en&modules=ext.cite... On a side note why does every wiki site have something like this? I can't tell what it is and haven't had time to look into it. But thats more than just a few lines of js to layout a page. Lastly, some sites like Wikipedia have hundreds of millions of pages, allowing them in would swamp the index as some people cant help but want to submit hundreds or thousands of pages from the same site (which would get blocked). I don't have enough resources to carry the zillions of wiki pages and have them drown out everything else. Most people know where to go if they want to look something up in Wikipedia and Google does a great job of it for just about every query you make, there will be Wikipedia prominently up there as a top result.
- LastTrain 4y agoThere was a time, getting to be quite a long time ago now, when you'd search for something - software to run on your old SGI, pictures of your 1982 ERA Vans, etc. etc. - and you'd find it. You'd find it because someone's 'thing' was old shoes, and they'd built a web shrine to their thing. These were people who had knowledge of things unrelated to HTML/HTTP/CSS and so the sites were rudimentary. You are right, the engine should focus more on content and less on the complexity or quality of the formatting - but I also kind of get it.