I don't know if people actually expect the training data to be published. For me its frustration, if its not open - don't call it open-source. It's so easy to continue to use the words the same way as we did before AI.
> you can modify, inspect and make derivative works
Even with a team of researchers inspecting the weights and understanding what is going on internally is a tedious operation. Having the training data doesn't really solve any issues here. But what it it does do is allow for auditability and public scrutiny - which imo is pretty important if you rely on these models.
Completely agree with this, I'm sick of people conflating the two. Open-weight models should be treated no more favourably than proprietary freeware.
Sure you can run tests and benchmarks on open-weight models, but that is the extent - there is no scrutiny, no auditing for bias or copyright contamination - just a black box that you rely on for "intelligence". I'm still shocked the way people can hand over not just huge swathes of data, but also decisions of all shapes and sizes - to AI companies with no way of being able to assess how the sausage is made.
Americentrism? Code compliant where? I tried my place in New Zealand, but the address isn't recognized. I couldn't find anywhere on the site what countries/regions are accepted.
To be fair it's going to be nontrivial to implement all the codes everywhere. In some cases it's going to be impossible for an app like this to judge - In the UK, for example, there are "permitted development" rights which allow certain things (like a garden office or other outbuilding) without going through a bureaucratic process. But while some of the rules are easy to automate (eg, must be less than 2.5m high) some are not. For example, the UK allows building over 50% of the garden[1]. But if it was just measurement based, you'd be able to build over 50%, then 50% of the remaining 50%, etc etc. So the rule is "50% of the original garden". That's going to be difficult for an app like this to find out.
What province/state/territory in NZ? I can add it in. We just research the code compliance stuff manually so we couldn't cover the entire world but I can add your case in.
From my understanding this is the next iteration of OpenX4 E-Paper Community SDK - an sdk made by some of the core contributors of CrossPoint that abstracts the hardware of eink devices.
Huge props to the devs, that haven't just embraced people forking their repo - but have actually put in a lot effort to make it easier for anyone that wants to develop on these platforms.
I like the idea a lot, any effort to spend more time with loved ones and off the phone is a noble pursuit. I think one thing that could add to this and help to habitualize it - would be ongoing statistics.
Something like..
- 3.8 days dedicated since you began in March
- 4.5 hours dedicated so far this week
- perhaps even being able to set up weekly goals could work
You are already using localstorage, so expanding on that sticks to your no account/analytics ethos.
It really bothers me that people refer to open weight models as being open source. They fundamentally aren't and are more akin to freeware than anything else.
As a (unfortunately) wordpress dev this seems to solve my single biggest painpoint with WP. Which isn't plugin security, but the overall plugin architecture.
WP treats plugins as content, literally in the same top level `wp-content` directory as uploaded images. This makes CI/CD among other things, a nightmare. But EmDash plugins are just TS modules, which has got to make things easier even if plugin configuration does end up in the db somewhere.
Wordpress has no concept of a "staging site" and no way to make changed and then "export" them from dev to production; you basically have to either restore it as a backup or just replay the changes by hand.
Ah. I understand your circumstances better. Short answer - I wouldn’t deploy menu changes. That’s usually low-lift that I would do it manually.
If I was doing it in a recurring basis I would investigate creating a process to export the menu data and import directly using a custom plugin. Or create (via plugin) and endpoint to sync both environments (a bit more work).
I did this one time before for a subset of pages and admin users. There are likely plugins that do this already but you could likely roll your own just for menus in an hour imho.
I’m not the one you asked, but when I did WP work a few years ago I would solve it via a hook that was triggered on Jenkins deploy. The hook would always fire and listeners to that hook would execute migration scripts and similar callbacks. For example used it to migrate some tags to categories and vice versa.
I remember when I looked at Wordpress for the first time, like 15 years ago, and was baffled that a dev/test/prod workflow involved copying filesystem content, database content, and changing URLs that got saved in the database. I couldn't believe what a steaming pile of garbage architecture it was.
Fast-forward to last year and I'm asked to look at it again. Surely, I think, in the ensuing time somebody would have rectified the architectural stupidity. It's a wildly popular platform, I thought. Surely it can't still be so terrible...
The "copying filesystem content, database content" part of that is perfectly sane. I should have phrased that better.
The insane part is the search-and-replace on the database backup to find hard-coded URLs referencing the environment's hostname. That's ridiculous. It speaks to the lack of serious operational experience that went into building the software.
Ah. That’s like a 15-line rite-of-passage plugin you write once and never have to worry about it again. Filter content going into the database and use relative uri for the same site. Configure everything else via environment variables.
I moved away from Wordpress altogether earlier this year because I got tired of babysitting MySQL.
reply