eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

205
active users

#parameters

0 posts0 participants0 posts today

#ReleaseMonday — New version (v0.27.0) of thi.ng/genart-api, a platform-independent extensible API for browser-based computational/algorithmic/generative art projects:

This version features an overhaul of the platform provided PRNG (pseudo-random number generator) handling and makes it easier to create multiple PRNGs for artworks which require/desire them...

Related section in the README:
github.com/thi-ng/genart-api/b

Also, just as a reminder, the project has:

- no external dependencies
- adapters for 3 art platforms (EditArt, fxhash, Layer)
- 6 example projects
- testing/dev sandbox with two parameter editors
- WebAssembly bindings & demo (currently for #Zig only)

Happy coding! :)

thi.ng/genart-apithi.ng/genart-api

A Site Selection Framework For Urban Power Substation At Micro-Scale Using Spatial Optimization Strategy And Geospatial Big Data
--
doi.org/10.1111/tgis.13093 <-- shared paper
--
“In this study, [they] model spatiotemporal heterogeneity and incorporate it into optimizing the location of substations. The optimized substation placement ensures electrical service coverage for over 99% of the area during peak power usage seasons, compared to the current coverage of 72%...”
#GIS #spatial #mapping #spatialanalysis #spatiotemporal #siting #demand #electricity #heterogeneity #substations #powertransmission #electricalpower #distrubition #service #city #urbanisation #extremeweather #model #modeling #parameters #factors #energycrisis #energy #urbanplanning #routing #outages #framework #UrbanPS #bigdata #AI #machinelearning #Pingxiang #Jiangxi #China #casestudy #coverage #utilisation #dynamic #load #loading #loadbalancing

Replied in thread

@dazo
Thank you for that valuable input

I've looked further into it and saw that it is quite extensive to set up and also has a suit that seems to be more targeted at larger environments to back up in a nice and cool manner, double confirming your words

When I discovered that for me it was easier to just jump back to bacula backup which I have known for decades

bacula.org/

#bash#csh#ksh

Those of us who have other phones can check if another Linux for Android runs on their device

Atm I'm looking at Lineage OS for my Android devices

I have scrolled through the most important parts of lineage us website.

One thing that you have to realize is that you're taking a grave risk when you are installing another operating system on the Android phone, at least that's what the manufacturer will tell you.

The manufacturer will **not** tell you that, you're freeing yourself from their **stranglehold** when you do this.
They will also not tell you that chances are, your device will work much more efficiently, because it will not have any bloatware, I repeat any bloatware what so ever

One thing they will never ever tell you, is that they make deliberately as difficult as possible for you to install another operating system, on your phone, your device, which you own, which you are the absolute Master of

The phone manufacturer will absolutely make sure, that they will never tell you, that they even put traps on your phone, when you install another operating system, just so that it bricks, so that you come running screaming and go back into their strangle hold

All these factors make installing another operating system on an Android phone risky, tedious, nerve wracking, and not worth it, if the phone is brand new, and the money you spent on it, isn't just chump change that you can easily afford if it breaks.

Just looking at the enormous list of do's and don'ts that you have to follow to the letter, clearly show per model, per manufacturer, how many traps have been put in, just so you are prevented to install another operating system, with which you free your phone from the stranglehold of the manufacturer, a phone that you have bought with your money, a phone that you own, a phone that you have the right to put whatever operating system you want upon.

On top of everything, your specific model of phone, needs to be supported even if there's just one letter difference, you should not even attempt to install that version of Linux on your phone, because the chances of breaking your phone literally bricking your phone, are astronomically High

The phone I need Lineage OS on is the one I'm working on right now, the phone overheats dramatically fast, has very poor physical Cooling, which became apparent when a broken patch was pushed to the phone, by Xiaomi, a couple of months ago.

Because of the overheating it needs to be shut down for most parts of the day making it a useless device

Xiaomi does the following to make it very difficult for you to unlock their fabricated devices:

* The boot unlocker is personal and you need to make an account for it
* An arbitrary limit is put upon the amount of Xiaomi devices that you can unlock per day per week per month.
* Every account can only unlock four devices
* Essentially Xiaomi is sending a f$ck you, towards you, as the owner of your devices, when you want to unlock the bootloader, so that you can put an arbitrary, much more stable operating system on the devices which YOU possess

My specific device is not supported yet by Lineage OS Xiaomi Redmi Note 12S
That means that I have to stop right there because the installation sequence specifically states that you need to double check that the image you put on the device is specifically designed for not only your model but your model to the letter so I need one for the Xiaomi Redmi Note 12S

By now I do not care which Linux distribution I put on this Android, just as long as it's specifically supported

The Journey through which I went to attempt to install Lineage OS on my Xiaomi Redmi note 12s has taught me the following

Android phone manufacturers do not like their clients. Android phone manufacturers detest their clients and treat them like slaves. Android phone manufacturers want their phones to be theirs forever, even when they sell them to you.

The rights to own a physical piece of hardware, are irrefutable yet manufacturers hate your rights in that respect

@altbot

lineageos.org/

#LineageOS#bash#csh

Another day, another #GenArtAPI release (v0.25.0):

This update mainly features the new `@genart-api/wasm` package, providing Zig & TypeScript bindings for core GenArtAPI functionality (i.e. so far mostly parameter handling).

This WASM bridge/integration is designed as an API module for the thi.ng/wasm-api toolchain. Installation & build instructions are in the readme.

New package homepage:
github.com/thi-ng/genart-api/t

Example project (w/ param editor):
demo.thi.ng/genart-api/param-e

Example Zig source code:
github.com/thi-ng/genart-api/b

thi.ng/wasm-apiGeneric, modular, extensible API bridge and infrastructure for hybrid JS & WebAssembly projects

New release of thi.ng/genart-api (v0.24.0) — a platform-independent extensible API for browser-based computational/algorithmic/generative art projects:

This release contains quite a few new features, as well as several important fixes for bugs which were accidentally introduced in the two most recent versions...

- extracted the debug time provider & FPS overlay to separate package
- updated `bigint` param handling (esp. randomization)
- added `collector` and `iteration` metadata accessors
- updated platform adapters (esp. the #fxhash one)
- fixed image & ramp param handling
- added a bunch of utilities to core API to deduplicate code in various adapters
- updated/fixed examples & docs
- added more tests (and updated core API to be more testable outside the browser)

All changes since v0.21.0:
github.com/thi-ng/genart-api/c

🎉

thi.ng/genart-apithi.ng/genart-api

#ReleaseFriday (1st release cycle of 2025) 🎉 — New additions & updates to thi.ng/genart-api, a platform-independent extensible API for browser-based computational/algorithmic/generative art projects:

- Added fxhash.xyz platform adapter (incl. support & adaptations for 10 of the 17 built-in GenArtAPI param types)
- Added `bigint` & `binary` data param types
- Updated parameter type definitions & factories (date, datetime, time, numlist, strlist, text, vector)
- Ensure any given default values are valid (and can be coerced)
- Added MurmurHash3 (128 bit version) functions (e.g. seed PRNGs)
- Added tests for all parameter types (factory functions & implementations)
- Added tests for utility functions
- Added GitHub actions (running tests)
- Various API docs updates, clarifications & fixes
- Update/refactor EditArt & Layer platform adapters
- Updated main & adapter readmes

New adapter package `@genart-api/adapter-fxhash`:
github.com/thi-ng/genart-api/t

Commits since last release:
github.com/thi-ng/genart-api/c

thi.ng/genart-apithi.ng/genart-api

Another new release of #GenArtAPI (v0.20.0), due to some urgent additions & updates of partially outdated documentation and refactoring/cleaning up of some parameter types. This project already contains more docs than code and because things are moving so fast, I forgot to update some parts... (Sorry for any confusion caused...)

Other notable updates:

- Simplified the core API's param value getter for obtaining time-based or randomized values (please check docs[1])
- Updated vector param definition
- Added a `.configure()` method for the EditArt platform adapter to allow manual selection of adapted params (to override the default auto-selection)[2]

You can see all the changes since the last release here:
github.com/thi-ng/genart-api/c

[1] docs.thi.ng/genart-api/core/in
[2] github.com/thi-ng/genart-api/t

GitHubComparing v0.19.0...v0.20.0 · thi-ng/genart-apiGeneralized API for browser-based generative art projects, plug & play support for platform specifics, parameter declarations, GUI creation, IPC - Comparing v0.19.0...v0.20.0 · thi-ng/genart-api

#ReleaseSunday and already second #GenArtAPI update this week, plus the addition of a new platform adapter package for publishing artwork to editart.xyz (ready ahead of #Genuary2025 😉)... (cc/ @pifragile)

This new release (all packages at v0.19.0 now) also includes several updates to API docs and adapter readme's:

- github.com/thi-ng/genart-api
- github.com/thi-ng/genart-api/t
- github.com/thi-ng/genart-api/t

All implementations are WIP (but fully functional, to the best of my knowledge!). If there's demand, I'm considering adding more parameter type adaptations also for the EditArt adapater (e.g. to support vector/XY params, as already done for the Layer adapter...)

Since I've been told "people/artists don't read anymore", tonight I'm starting to record a video walkthrough, wish me luck! :)

editart.xyzEditArtEditArt - co-create a piece of generative art along with the artist.

New release of thi.ng/genart-api, a modular cross-platform API/SDK for browser-based computational/algorithmic/generative art projects, helping to reduce artists' efforts to adapt work for different art platforms/environments/uses/workflows.

Main new v0.18.0 additions:

- The param editor reference implementation now groups parameters by their declared group and sorts them by given order (both optional)
- The `@genart-api/adapter-layer` package supports adaptations/translations for more param types, incl. vectors, which are not yet natively supported by that platform. E.g. vectors will be transparently represented as multiple, separate numeric params on the platform side, but your artwork is blissfully unaware of this and still only would deal with vectors. The platform adapter does all the reconcilation and handling of param changes...
- Started adding tests
- Updated API docs & readme's

As always, feedback highly appreciated — this project is in active development...

I'm aware, the target audience for this larger project is quite limited, but the benefits are real (and palpable!), not just for artists in this field (but especially for them!)... I'll do my best to illustrate the (recurring) problems being solved here, demystify some of the concepts and squeeze in recording a short(ish) video showing how to develop a small project from scratch using this system/setup and then repurpose it and show related tools still in development...

#ReleaseFriday (the 13th) — New version (v0.17.0) of thi.ng/genart-api with the following updates:

- Added platform adapter IDs for use with external editors/tooling
- Updated editors[1] to check for platform adapter & API version compatibility, display warnings if needed...
- Added/migrated three different seedable PRNG implementations in API core package (SFC32, XorShift128, XsAdd). These are completely independent and can be used by platform adapters and/or artworks (also multiple instances)
- Initial release of first platform adapter for an upcoming art platform (currently invite only)
- Restructured all example projects
- Updated readme & API docs (docs.thi.ng/genart-api/core/)

[1] The param editor/sandbox requires your artwork to use the latest version of these packages: `@genart-api/core` and `@genart-api/adapter-urlparams`.

demo.thi.ng/genart-api/param-e

New improved version (of editor) with many more features (incl. variation/preset management) is in the works...

Major #GenArtAPI project updates from this past week:

thi.ng/genart-api

- Restructured the project as monorepo, splitting out core API and platform adapter(s) as separate packages
- Switched package scope from `@thi.ng` to `@genart-api` to highlight project/platform independence (not directly related with other thi.ng projects).
- Published new packages: `@genart-api/core` and `@genart-api/adapter-urlparams`
- Moved API docs to docs.thi.ng/genart-api/core/
- Added support for n-dimensional vector parameters and added support in the reference platform adapter and in param editor
- Updated all examples & parameter editor. The latter is now only compatible with this latest API version (v0.16.0)
- Updated docs/readme

If you want to find out more, the project readme has _a lot_ more information. Also feel free to get in touch with any questions/proposals!

It just dawned on me that I haven't been mentioning five(!) recent thi.ng/genart-api updates, all from the past month... 😱

The latest version (v0.14.0, just released) is largely about an overhaul of messaging related functionality and also addresses use cases related to managing multiple artworks embedded (via `<iframe>`s) in a single document/page (think: online gallery scenarios...)

If you're already using GenArtAPI message/event listeners in your own artwork, you might have to rename some of them. This commit has the important details:

github.com/thi-ng/genart-api/c

Also, the online parameter editors have been updated and are now only working with the latest version of the API, so be sure to update your artwork projects to stay compatible:

Generic editor harness (for your own compatible artworks):
demo.thi.ng/genart-api/param-e

Demo (with test artwork):
demo.thi.ng/genart-api/param-e

Other recent changes/additions (in no particular order):

- added new message types to poll the artwork/API for current state/info
- update message names & naming convention
- added ability to configure the API behavior/features (also via messaging)
- option to emit frame messages w/ current timing/frame info
- message broadcasting to multiple GenArtAPI instances/artworks
- inject common defaults for optional settings in param specs
- fixed date/datetime param handling (in editor)
- updated/fixed time providers
- updated debug time provider (w/ FPS visualization overlay)
- use gzip compression for image param values (in default platform adapter)
- added version info
- various documentation updates
- (WIP) WASM bindings for Zig-based artworks
- (WIP) unpublished progress on real platform adapters

Some of these features are all about enabling new use cases and improving usability of external tooling around artworks adapting GenArtAPI, for example:

- Ability to broadcast start/stop messages to either individual or all artworks embedded in a page
- Ability for the param editor to configure the artwork currently being worked on to emit timing & frame information (which then can be integrated in the editor UI without the editor knowing anything else about the artwork)
- Enable editors to identify an artwork/project and store param presets grouped by project ID
- Allow editors (or other tools) to check the API version used by the artwork by first sending a `genart:get-info` message, then listening for `genart:info` response (then maybe display a warning if version is incompatible)
- etc.

If you want to find out more, the project readme has _a lot_ more information. Also feel free to get in touch with any questions!