@here Trying new things and taking advantage on new platform by doing first pool. That one is dedicated to programmers, doing this as a hobby or with a profesionnal purpose. Does PHP, language choosed to build SeAT, blocking you to contribute to SeAT (in core, or with third party things) ? Which programmation language are you using ? Or with which one are you more fluent ?

@here Greetings, this is for all Illustrator or Photoshop like fans ! SeAT is looking for a new and more modern logo as a successor from our good old font icon. The winner will get his amazing logo on all SeAT supports (our fancy new Discord Guild, documentation, the app itself from more than hundreds of install, etc...) He'll also earn a 3B ISK reward 😮 Please submits all your prposals in #channel_822585588854161490 channel !

@here You have plenty of channels to talk, exchange and ask on this Discord. Refrain on DMs - we all do things aside SeAT 😉 For a quick introduction : #channel_821361165791133719 can be used for any general topics - even EVE or Space related ! #channel_821361566184112181 can be used to exchange about Plugins topic - you may gather ideas, suggest things, etc... #channel_821361546608508938 is for general support question - if you're stuck with your instance, don't unserstand an error, etc... #channel_822585588854161490 is available when a contest is running (currently, we're looking for a new Logo - don't hesitate to send your suggestions !) #channel_821361505735278592 can be use for any technical related topic (if you want to alter a thing in core and don't understand how, or want to exchange about queue stuff for exemple)

@here We just released a fresh set of packages (incl. a fresh docker image). This is a rather important functional update (amongst other things) as the endpoint version we were using for character information is being removed: https://developers.eveonline.com/blog/article/v4-of-esi-public-character-information-to-be-removed-on-21.10.2021. The removal is happening on the 21st of October, so you have a little while to do it.

@here I just tagged a new docker image version, 4.2.0. This image bumps the PHP version, the base OS and should fix some Let's Encrypt related certificate issues. Happy upgrades!

@here Good evening little capsulers. Those of you who used to crawl arround the Discord probably had noticed I was far less active than I used to be. Maybe it scary a few of you by the meantime. Sorry about that, it's not my habit. Things are - the life is flowing and stuff is changing - they're are newcomers and leaving ones. I had a lot of fun by contributing to SeAT, and walk in qu1ckkkk's shoes - but today, I'm non longer involving into EVE and have a freaky tons of app to maintain (not open source unfortunately - sad me 😢 ) By not playing the game - neither having the fillibng after a crazy working day to continue the day but with SeAT - it seems to me a better option to turn the page and handover to the next generation (oh my, such old guy 😮‍💨 ) Saying that, I am in the leaving wave (the one which is behind the crazy truck moving accross stars and gate to gate). @user_301981661761896449 will start to take the lead on SeAT core - as it has already started since a few months now. We try to make the move as smooth as possible. However, as he's still learning the core - he might need some handies who assist him - submitting support (thanks to those of you who try to give few hints to all those lost sheeps). DO NOT PANIC It's said, but really, do not panic - SeAT will remain at its exact same location on GitHub. Hotfixes will continue to flow. Major releases will continue to be shipped. I will leave - I didn't left yet. That mean I'll contribute to the next major version of SeAT (said SeAT 5!). Those of you in the back of the room - do not ask WHEN - answer will be as usual : when it will be ready 🙂 As it's a major version, we have to find some cool new features, refactor boring stuffs, etc... Those of you discord crawler already have seen few screens of the new UX - especially with the skill board while I was working actively on it.

By the way, some of you might have seen we're thinking about a switch between mysql/mariadb engine to postgresql - it's still an idea and will be confirmed at a later stage (mostly stress tests). In any cases, we already have a migration path if must be the case. Which mean there will have no data lost from existing instances. The bad part of the news now. As I said, I'll stop to maintain SeAT on my own - which also mean I'll stop to maintain my own third party packages (also known as plugins)

• https://github.com/BenHUET/eveseat-calendar

• https://github.com/warlof/seat-connector

• https://github.com/warlof/seat-discord-connector

• https://github.com/warlof/seat-teamspeak

This however is a true thing and I will not port them to next release. As a result, that mean those of you who are using such packages will need to either find alternatives, continue support on them or even spawn their own. I hope all those information didn't give you the blues - as it shouldn't. SeAT still have a long life uppon it and have an amazing community. Stay strong, stay together 🙂

Ladies and gentlemens, I have a poll that I need to share with you to determine which road we should take. As some of you may know, with SeAT 5, we was thinking about doing a switch regarding the used database engine. Historically, SeAT was using MySQL, followed by MariaDB. Those are widely used database engines when we're talking about websites. However, if it's easy to use, it's also less powerful than a professional grade engine like MsSQL or Postgres. They need a lot of tweaks out of the boxes and provides less functionalities than the two previous ones - even if it tends to change a little bit. As an exemple, you can design custom structure on which you'll apply integrity checks, neither complexes rules - and there is technically no way to maintain indexes properly. Regarding indexes, yes, you can "maintain tables" using optimize command. However, what it will really do is a clone of the optimizing table, rearrange indexes and drop the original table. This operation will result in large IO and rewrite operations (think about your poor nVME or SSD 😭). We know some of you are frequently dropping data - because unused and unwanted - in order to keep storage at a decent level - for various reasons. The bad of such actions is it's turning your tables in a walnuts - resulting in poor performances.

Furthermore, playing with Postgres since a few months help us to identify that some query plan might be better under Postgres than under MySQL/MariaDB - especially using parallelism while reading indexes. Now about SeAT 5 We're thinking about shorting its release plans. We would add a lot of new toys, but it's sometimes hard to play with IRL, fun, and Open Sources stuff. The drawback of this is we start to reach EoL of currently used Laravel version - and PHP is going really fast lastly. We also know a few of you would play with all those new techs stuff and this is a thing we understand. Last but not least, we would know what's your concern regarding Postgres switch. Should we do it, or stay under MySQL/MariaDB and think about that at a other day ? In all cases, keep in mind we will provide a migration process which will help you to keep all your current data's in the new version (being or not a new DB engine behind). 🅿️ switch to PostgreSQL now 🇲 stick on MariaDB for now

@here To those of you who would help with SeAT translations, we've setup a Crowdin project this day. Crowdin will ensure all files exist for all covered languages at any time - and help you to translate stuff with an user friendly website https://crowdin.com/project/eveseat Who can help to translate ? Anybody can help to translate - either a whole file or a single caption How can I translate ? 1) go to https://translations.eveseat.net 2) either create or login with your existing crowdin account 3) pick a language on which you want to work and either select Translate All button or pick a file in the list Which packages can be translated ? All core packages with a translation file can be translated. Currently, we've setup the following :

• web (contains most major UI content)

• api (contains API UI content, mostly settings)

• notifications (contains notifications UI content, mostly settings)

When translations will be available ? Translations will be synched on a period basis with SeAT repositories - and updated captions will be available on next package release I would help, but my language isn't available, what to do ? Ping one of the following persons which will add your language to covered list and notify you once done. From there, you'll be able to translate. @user_76781846418956288 @user_398925835794645002 @user_301981661761896449

@here There will be changes on our initial release plan. First, SeAT 5 - the next major version of SeAT will not be the one we were talking about until now Second, SeAT 6 - is already in work and will contain all we were talking until now when we were talking about 5th gen. By the meantime, I profit of that message to announce Japanese is now a supported language in SeAT. Welcome to the japanese community (even if they're already arround for a while now) 🇯🇵 Further reading, what's the plan :

About the 5th Generation

5th Generation will be release with the following in aim :

• security

• stability

• flexibility

target release is by the end of the year

Dependencies

• Laravel 10.x

• Simple Cache 2.x (locked due to dependency within laravel-excel, which prevent us to use 8.1 cache interface)

• PHP 8.1.x

• MariaDB 10.10.x

Architecture

• Eveapi Jobs will non longer check if data were cached before processing - this should prevent some issues with paginatted endpoints

• Eseye low coupling (Http Client, Logging and Cache)

-- Eseye log will be bound to laraval logger on eseye channel by default -- Eseye cache will be bound to laravel cache on eseye channel by default -- Eseye will be usable based on dependency injection - if you're using it with your plugins, you may have small changes to apply

Chore

• New logo usage

• Update of our docker-compose and startup script

-- logs will be store on host rather than inside container, and will be shared by all containers -- startup script will non longer touch permissions resulting in a faster boot .

About the 6th Generation

6th Generation will be release with the following in aim :

• user experience (also known as UI)

• admin experience (also known as shell stuff)

• new toys

User experience

• user interface will be completely reworked on top of Tabler.IO and Bootstrap 5

• user will benefit of a plain new navigation bar, with actions sorted in categories and more flexible for third party actors

• dashboard will become a thing with content loaded based on user profile (meters related to fight for PVP user, meters related to industry for Indie user, etc...)

Admin experience

• tracking of jobs will be improved on a per token basis view

• settings will be merge into a single place called "universal settings layouts" helping to get consistency accross components settings and menu entries

• logs will be available in frontend

Dependencies

• JQuery usage will be removed in favor of Vanilla JS (we will continue to publish it for this release in order to avoid excessive breaking changes, however, this library is non longer a needs with new generation browser which are natively embeding most of its capabilities into their own API - resulting in faster processing, faster rendering) - for those of you which might be worried : https://youmightnotneedjquery.com/

• Select2 will be removed in favor of Tom Select, lightweight and with built-in support in new template : https://tom-select.js.org/

• To be or not to be Postgres... still a question

@everyone

@role_822447788590891029 @role_822447791301066782 A security hotfix has been deployed on the eveapi package which is bumping its version from 4.18 to 4.18.1 The fix is preventing character to keep their corporation roles when they're changing corporation. This update is shipped with docker image 4.2.24 Thanks to @user_614098468218339348 for its contribution

@role_822447788590891029 @role_822447791301066782 There is some important update available for you according to an undocumented change in ESI This update is required in case you want to continue beeing able to processing the following endpoint /v2/corporations/{corporation_id}/roles/ - shortly, it's used to collect roles attached to corporation members Symptom: The job Seat\Eveapi\Jobs\Corporation\Roles is failing with the following error Seat\Eseye\Exceptions\EsiScopeAccessDeniedException Change is available in the following :

• eveapi@4.18.2 in case you're using Blade install

• docker image 4.2.26 in case you're using Docker install

You can follow usual update guidelines:

• for Docker https://eveseat.github.io/docs/upgrading/general/#docker-installation

• for Blade https://eveseat.github.io/docs/upgrading/general/#blade-installation

SPECIAL ATTENTION In case you're using custom scopes, be sure you have the following scope esi-corporations.read_corporation_membership.v1 registered in your application on the eve dev portal : https://developers.eveonline.com/ Also ensure it's asked in your scopes profile by SeAT - otherwise user granted access to their data against ESI will not be updated

@role_822447788590891029 @role_822447791301066782 Be sure to update your running SeAT instances with eveapi 4.20.0 release before May 8th This package is shipped with Docker image - 4.2.30 (hash 11c0a3996e6bfa4521a57a1143489b26a597390805ddd71e5bf02701c04def33) It introduces some form of throttling for Prices Jobs according to an ESI update for the following endpoint /markets/{region_id}/history/ Also, be sure you don't alter the price update schedule (esi:update:prices) which should run only once a day (default set to 0 13 * * * - once a day, at 1pm)

eveapi 4.20.1 has just been delivered with updated market prices throttling Thank to @user_160579063176626177 and @user_614098468218339348

@role_822447788590891029 Those who want to give a try to the next SeAT version can deploy a stack using 5 as image tag inside docker-compose file instead 4 https://github.com/eveseat/seat-docker/pkgs/container/seat/93412753?tag=5 Replaces image: eveseat/seat:4 with image: eveseat/seat:5 in lines bellow https://github.com/eveseat/seat-docker/blob/0278ddbbd1beb314848abebed79d24cb654c0589/docker-compose.yml#L77 https://github.com/eveseat/seat-docker/blob/0278ddbbd1beb314848abebed79d24cb654c0589/docker-compose.yml#L103 https://github.com/eveseat/seat-docker/blob/0278ddbbd1beb314848abebed79d24cb654c0589/docker-compose.yml#L124 CAUTION THIS IS A PREVIEW BUILD - DO NOT TARGET A PRODUCTION ENVIRONMENT YET

NEW AVAILABLE UPDATE An update is available regarding prices history processing. Symptoms :

• outdated prices

• job named Seat\Eveapi\Jobs\Market\History in public queue is failling with the folloowing message has been attempted too many times or run too long. The job may have previously timed out.

@role_822447788590891029 sorted with image 4.2.32 and hash sha256:c8c9a0bb05de8eae3c08b39f68b4aa68dcc3cd256e6b0b1e9686fef37397aca4 usual update instructions https://eveseat.github.io/docs/upgrading/general/#docker-installation @role_822447791301066782 sorted with eveapi package and version 4.20.2 usual update instructions https://eveseat.github.io/docs/upgrading/general/#blade-installation

NEW AVAILABLE UPDATE An update is available regarding prices history processing (yes - yet again). This one should aim especially people hosting an instance in US region which lead to longer running queries than we initial expect. Symptoms :

• outdated prices

• job named Seat\Eveapi\Jobs\Market\History in public queue is failling with the folloowing message has been attempted too many times or run too long. The job may have previously timed out.

@role_822447788590891029 sorted with image 4.2.33 and hash sha256:6ba4120612422c25be5dee7255cd00d6534b90f6e7df9f11e2a33ee8f9144b3a usual update instructions https://eveseat.github.io/docs/upgrading/general/#docker-installation @role_822447791301066782 sorted with eveapi package and version 4.20.3 usual update instructions https://eveseat.github.io/docs/upgrading/general/#blade-installation

we created #channel_1113334797201317941 , feel free to test it out! ¯\(ツ)/¯

NEW AVAILABLE UPDATE An update is available regarding prices history processing (yes - yet again). I hope it will be the last one - compared to the previous, we are non longer dispatching all jobs at once and shifting them using delay - but rather chaining them all together. The overall completion should be arround 180min at worse. However, individual job is taking less than 60 seconds when instance is hosted in US. In order to assist with diagnose, History job logging has been enforced.

• every queued job for the same price batch will also display the overall batch size and the current job count. This should give you more visibility regarding the overall process

• various debug level log entries have been added arround the job - be sure you're using error when in production, otherwise, your logs will grow quickly

Symptoms :

• outdated prices

• job named Seat\Eveapi\Jobs\Market\History in public queue is failling with the folloowing message has been attempted too many times or run too long. The job may have previously timed out.

@role_822447788590891029 sorted with image 4.2.34 and hash sha256:5d99bd88f764309f7f937f0aaba0235ca1464fed8c712a8118b3ec459a92675b usual update instructions https://eveseat.github.io/docs/upgrading/general/#docker-installation @role_822447791301066782 sorted with eveapi package and version 4.20.4 usual update instructions https://eveseat.github.io/docs/upgrading/general/#blade-installation

@everyone With the recent shutdown of EVEPraisal, you may have noticed some changes that allow various plugins within seat to select alternative evepraisal instances to source pricing data from. Unfortunately the reason that EVEPraisal was banned by CCP (leading to its closure) was not remedied. As such people are now taking the recently open sourced evepraisal code and spinning up their own instances. This is causing large and detrimental load on the CCP servers. Therefore the following message has been asked to be distributed regarding this activity. If you, or anyone you know is hossting an EVEPraisal instance, please try to keep the number of active sites as low as possible. Ie, work together and share sites where you can. Or use another market service where possible. eg fuzzworks or janice. And second is a message from me (kind of). If you, or anyone you know, is running this code. Please see the parent repo for an update that was published ~1 hour ago as of this message. This reduces the load placed on ESI by a factor of 4!! (https://github.com/evepraisal/go-evepraisal/pull/175). Apologies for the ping to all, but please spread this message where you can so that we can reach the owners of these 'new' instances of EVEPraisal. CCP are in the midst of banning insstances that are incurring too heavy a tax on their endpoints, so it is in our best interest to work together to solve this problem.

For an easy alternative to evepraisal, please have a look at fuzzwork! eg https://market.fuzzwork.co.uk/appraisal/

For an easy alternative to evepraisal

@everyone as of tonight you will notice that your SeAT servers will be failing all authenticated ESI jobs and you will not be able to log new people in, or log in from new devices. As time progresses all logins will be unavailable. We are working to resolve this issue asap. Once a new update is available to fix this I will ping here again. We apologise sincerely for this outage

@everyone docker container version 4.2.40 has been published which includes the update to eveseat/services:4.3.1 and eveseat/eseye:2.4.1 TLDR! Update now to restore login capability and job processing!

@everyone The seat documentation and packages are all being updated for v5. We are working through the upgrade process and ironing out issues as we find them. That said, we currently don't recommend you update (unless you understand that it may break and you may need to roll back to v4) We are also aware of an issue with v4 picking up the v5 plugin versions and failing to launch. We are looking into this as well. More details to follow on that. (patch was released for v4 docker. Please ensure your containers are up to date)

@everyone CVE ALERT There was a security issue with Squad filters mechanism which has been reported and mitigated. This issue is applying to the following :

• eveseat/web :

versions 5.0.1 commits d05ca291446f00b24942215e993ef15c2c9a37ea

• eveseat docker image :

tags 5, 5.0, 5.0.21, 5.0.20, 5.0.19, 5.0.18, edge (all platforms) digests : sha256:63aec5491765e7c7f62586c889455b33e8b8461fc5db837b69d77325509d3268, sha256:aa50c18a92410ddedb54e9341f151b24eb32824dd221dfa58866113ae5178611, sha256:3be844858fc7271b81c931a8860deeec48a82f9c7ee1bf514bc5a33b811ef88e, sha256:c0b214c604992fd4c122313d99891170ad3e17c5350a65ad1dec879161c9f65f, sha256:14dce1ad622c7feeb5ad8fac749f3a83b58319137718dcb1f66fcf6b84733ac0 This issue has been reported fixed to the following :

• eveseat/web :

versions 5.0.2

• eveseat docker image :

tags 5, 5.0, 5.0.22 digets: sha256:d4bf3d731ab97b6dfeb94bf54f794b88acc26a482d6059800c93cea4aba05780 ---- When filters were applied together on certain relationship (ie: corporation AND character role), users were limited based on only one of the rules instead all of them. ---- In case you're running one of the following, be sure to update your environment as soon as possible. If you're seeing this message without beeing a SeAT instance owner, please report to your instance administrator. In order to upgrade your instance, be sure to follow the generic upgrade instruction https://eveseat.github.io/docs/upgrading/general/

@everyone 🎺 🎺 🎺 🎺 🎺 🎺 Short and Quick: At this point in time we would like to advise that SeAT v5 is considered the current stable release!! We reccomend that all new installs be v5, and that users migrate when able form v4 to v5. v4 will still be supported, but as has been the case for some time now, all development focus other than security will be placed into v5 devs: I will in the coming days be archiving the main / master branch of all remaining core packages to the v4 branches and placing 5.0.x into main. github actions will all also be updated to work correctly for tagged releases at this time.

@role_822447788590891029 build 5.0.31 is containing two hotfixes which will prevent your instance to spam ESI whereas you reached invalid call limitation @role_822447791301066782 eveapi 5.0.8 is containing two hotfixes which will prevent your instance to spam ESI whereas you reached invalid call limitation see https://github.com/eveseat/eveapi/releases/tag/5.0.8 for details follow usual guidelines to patch your environment https://eveseat.github.io/docs/upgrading/general/

@role_822447788590891029 build 5.0.33 is containing hotfix of an issue which was preventing your instance to contact ESI and process data @role_822447791301066782 eveapi 5.0.10 is containing hotfix of an issue which was preventing your instance to contact ESI and process data see https://github.com/eveseat/eveapi/releases/tag/5.0.10 for details follow usual guidelines to patch your environment https://eveseat.github.io/docs/upgrading/general/

@role_822447788590891029 build 5.0.35 has been published that contains a fix to skill level filters in squads. Please update ASAP if using this feature. @role_822447791301066782 this is contained in web:5.0.9 see https://github.com/eveseat/web/releases/tag/5.0.9 for details follow usual guidelines to patch your environment https://eveseat.github.io/docs/upgrading/general/

Hi all. As you may have noticed we are having a bit of an issue with our docker builds atm. We are working to resolve this as sso as we can! There was a change to how artifacts are processed in the current version of the plugin so we will need to spend some time to make this work as intended again.

The build issues are now resolved and the seat-docker image has been updated! Note: the CI workflow will need some work in the nearr future so expect to see some superfluous container images built in the future as this is debugged.

Hi everyone!! With the v5 transition well and truly behind us it is important for us to consider what the next steps for SeAT development will be! In this vein, I have created a survey that is aimed to be completed by you (SeAT server administrators). If you could take a small amount of time to fill this out and let us know your thoughts then this would help us out tremendously! If you have any questions re this, then please discuss them in #channel_821361165791133719 survey link: https://cloud.brewsurvey.com/links/a81f3db2-3175-47ed-b118-6bd98451ac13

@everyone If you havent already, I would appreciate if you could respond to the survey in the above post! It provides invaluable information to the development team to guide our efforts! I will be closing the survey at Sunday, 13 October 2024 at 11:28 which is Sunday, 13 October 2024 at 11:28 Cheers!!

Hi All!! Thank you all for your time in responding to the survey above. Between the information gained from the survey and internal conversations I have put together a document describing my plans for the development of SeAT going forward. Attached is that document. The high level breakdown of future effort is described by four categories:

• Backend Performance Improvements

• GitHub Issue Backlog

• Community Plugin Organisation Standup

• SeAT 6

As part of the task to process the GitHub issue backlog I plan on implementing some of the described milestones into tags in order to organise the issues. If you have any questions please discuss this in #channel_821361165791133719 Cheers!

@everyone I have just tagged a new release of eveseat/eveapi with some changes to the schedule based on some observations by CCP. Please update when possible. For docker owners the schedule will be automatically modified when you update. For blade owners, ensure that after you update you first run migrations then the schedule seeder. (As per docs you should anyway: https://eveseat.github.io/docs/upgrading/general/#blade-installation) This does not change the frequency of the schedule, however just staggers it at a random offset so that we dont all hit ESI with requests at the same time. This only affects the killmail and contracts command schedules. Further it will only adjust the schedule if you were running the default schedule, it wont change any customised schedules. (Note the docker containers are still building, should be ready in about an hour)

@everyone please be aware there were some releases with errors recently. In order to address these, please update to latest versions. If you are on an arm build using docker, there is a fault with our docker builds for arm which means we are not getting updates at the moment. To address this, do not update, and if you have the in your docker-compose file change the versions of the image from 5 to 5.0.57

@here Docker builds should now be restored to full functionality 🙂 There is an ongoing issue where github failures crop up on the arm builds, but I can workaround this for now just by rerunning the job. I will work on improving this in the background.

@everyone Recent changes to EVEs SSO have meant that existing versions of SeAT are sending invalid login requests. This leads to an inability to authenticate new characters. I have finally merged the changes made by recursivetree into core in order to address this. For @role_822447788590891029 please update and you will receive the latest package versions :)[specific docker tag 5.0.69] For @role_822447791301066782 You are looking to update to web:5.0.23, eveapi:5.0.22 and eseye:3.1.2 and ensure you run migrations. -- https://github.com/eveseat/web/releases/tag/5.0.23 -- https://github.com/eveseat/eveapi/releases/tag/5.0.22 -- https://github.com/eveseat/eseye/releases/tag/3.1.2 With this update it is highly recommended that after applying the update the SeAT cache is cleared to fully apply the web patch. To do this use the command php artisan seat:cache:clear