liwords VS endoflife.date

Check out https://woogles.io (disclaimer I am a cofounder). AGPLV3 platform with world class bots, puzzles, a free analyzer, clubs/tournaments, and more to come. You can see the source code at https://github.com/woogles-io/liwords. We recently hit 5M games played and have hosted a few major tournaments.

A small team of us work on a project https://github.com/domino14/liwords - this is an online crossword-board-game playing website. We have around 6000 MAU, are fully free and open-source, and need a lot of coding help!

We built woogles.io (a crossword board game playing site with almost 10K MAU) in Go. See https://github.com/domino14/liwords

https://github.com/domino14/liwords - warning it’s not that well-developed but it’s ok

A small team and I made https://woogles.io - we were inspired by lichess to make a site to play crossword board games during the pandemic (like Scrabble, Words with Friends, etc).

We did raise money on Kickstarter - 25K but are purely donations-driven and open source (AGPL3) Most months we just get enough to cover the cost of running the servers. We have around 6000 monthly active users, have hosted several big worldwide championships, have puzzles, and just earlier today released a board editor / broadcast mode for annotating real life games in real time. We also have a top notch bot AI and WASM-based analyzer.

Our stack is Go, Typescript + React, with NATS/PGSQL on the backend.

woogles.io

The people behind those websites and apps have no clue this software exists. The exception is woogles.io because it is associated with the Macondo AI. /u/14domino is the brain behind both of those things

https://woogles.io raised $25K on Kickstarter and built a more beautiful site. Come join us (we’re still taking donations :)

- Playing online: there is woogles.io which I personally would recommend; it's made by players for players and is free to use. Among the features are: play against humans, play against strong bots, tournaments, feedback on your moves after the game, availability of different languages and game variants. Other options are: playscrab.com (also made by players for players); isc.ro (the Internet Scrabble Club); the app Scrabble Go and, if you don't mind playing with slightly altered game rules, Wordfeud, which comes along with a large online league (not technically affiliated with the app itself).

> where you can see overlapped timelines when support ended

I tried to generate a visual timeline for a given page (https://github.com/endoflife-date/endoflife.date/pull/2859, has some screenshots), but it was limited to a single page (so you'd only see nokia devices at once for eg).

It turned out that it is too hard to generate clear charts with vague data. We often only know whether is device is supported or not (true/false, see comments about samsung below in this thread), and don't have clear release dates.

I'll get to it someday (PRs welcome), but it might not work for the usecase we want (picking phones) because data on mobiles is very vague.

repairability score -> sounds interesting, will file an issue and see. The hard part is that there's no clear identifiers for devices (SWID/CPE are just not good enough) for us to track this kind of data from elsewhere easily.

Here's the PR where it was added by a user, "Based on a Rails core team member's comment"...

A lot of the communications regarding End of Life for Support is done very effectively here: https://endoflife.date/

https://endoflife.date (not mine)

a little similar to endoflife.date if anyone has ever come across it for Software versions?

We do this at https://endoflife.date API, and it works quite well.

I've created the `db.json` with the [end of life](https://endoflife.date/) api.

Something I've recently worked on is building an SQLite database of all the dependencies my organisation uses, which makes it possible to write our own queries and reports. The tool is all Open Source (https://dmd.tanna.dev) and has a CLI as well as the SQLite data.

Ive used it to look for software that's out of date (via https://endoflife.date), to find vulnerablilities (via https://osv.dev) and get license information (via https://deps.dev)

It's been hugely useful for us understanding use of internal and external dependencies, and I wish I'd built it earlier in my career so I could've had it for other companies I've worked at!

This is neat: https://endoflife.date/

I'm looking for a 3rd party vendor that can do the mindlessly tedious work of maintaining a library of software support dates. Think hundreds of thousands/millions of versions of software in an enterprise with ridiculous tech debt. Something like endoflife.date but much more far encompassing.