#changelog URLs

[windmillcode]

LibTracker Updates 11/25/24: Simplify Dependency Management with this simple SBOM Tool

We are excited to announce the latest updates to *LibTracker*, our VSCode extension designed for professionals to simplify software bill of materials (SBOM) management. With LibTracker, you can effortlessly analyze and manage your apps, ensuring up-to-date versions, addressing security vulnerabilities, and resolving licensing issues—all at a glance.

Access it here: [LibTracker on VSCode Marketplace](https://marketplace.visualstudio.com/items?itemName=windmillcode-publisher-0.lib-tracker)

### New Features in the Latest Release:

- **Grouped Paths**: Added the ability to associate multiple apps with a root folder, easing project transfers between computers.

- **App Detail Page**:

  - **Subdependency Information**: View detailed info and license info for subdependencies.

  - Toggle between root and subdependency data to explore license and CVE details.

- **Bulk Group Path Update**:

  - Recursively searches for app basenames within directories. or the exact subPath. Can specify a recusion level

### Upcoming Features:

- **App Detail Page Enhancements**:

  - Integration of CVE details for all subdependencies.

  - Search functionality extended to include nested child rows.

  - Expand and collapse all subtables within rows for streamlined navigation.

  - Responsive design updates to allow a card-based layout for improved usability.

- **Toggle Select All Apps**: Introducing a select-all option on the project detail page.

- **Workspace Folder Management**: Development depends on VSCode API’s ability to support VSCode profiles.

- **SBOM Generation**: Investigating whether to retrieve license and CVE details for every version of each package used in the app.

### Future Milestones (Exploring Feasibility):

- **Git Backup Changes**: Enhancements to streamline version control and backup capabilities.

- **AI-Powered Summaries**: Considering automated generation of license and CVE category summaries.

- **Subdependency Navigation**: Exploring the possibility of linking subdependencies in the license pane to their locations in the dependency table

- **Advanced Table Features** - the current package does not support

  - child row search

  - expand and collapse all subtables in a given row

  - responsiveness (remove columns or using cards at a certain viewport)

[warrenwoodhouse]

Keep a Changelog

Free software for developing a more efficient changelog file.

[quailfence]

The Undertale and Deltarune wikis have moved off of Fandom

Exactly what it says in the tin - the UT and DR Wikis have forked from Fandom, just in time for chapters 3 and 4. New URLs are undertale.wiki and deltarune.wiki respectively.

If you want to support the new wikis, do these things:

Change any links to the fandom wikis to the new ones. This helps the new wikis get higher up in the search results

Install the Indie Wiki Buddy extension, which automatically redirects you to an indepentent wiki if one exists for a certain topic. In fact, their changelog is how I found out that the new wikis existed

[goblin-social]

Goblin changelog, 24/04/2024

You can now follow tags in Goblin, thanks to the stellar work of @sirilyan@kobold.page

Extended the de-duplication of posts to mastodon threads and conversations (it only applied to goblin posts until now). This is how a 'toot-storm' looked before:

And this is how it looks now:

Fixed images not showing up in reblog trails when coming from outside goblin.

Added a new text style: Big:

Added 'human-readable' urls for the posts: No longer https://goblin.band/notes/9sf708u0zvw8neq3, but https://goblin.band/@sesamenom/not-goblin-related-but-does-anyone-know-why

[hydrus]

Version 621

windows

zip

exe

macOS

app

linux

tar.zst

I had an ok week. I fixed some bugs, did some duplicates work, and cleaned up some build and environment issues, and there's some more user work for ratings.

full changelog

ratings

Thanks to a user, we have more rating options.

First, under options->thumbnails and options->media viewer, you can finally set the size of ratings!

Second, under services->manage services, you can now set many more 'star shapes: triangles pointing up/down/left/right; diamond; rhombus pointing right/left; pentagon; hexagon and small hexagon; six point star; eight point starburst; hourglass; large + and X shapes.

In an experiment, you can also set custom svg star shapes. I've thrown a couple of very basic examples into a new install_dir/static/star_shapes directory, but you can add more yourself. Try to add something that's squarish and has a clean simple sillhouette on top of a transparent background.

We're debuting some unusual new drawing tech here, and you may see some new misalignments or clipped borders at certain sizes. I'm going to keep working here to nail down good padding and margins, and we'll play around with svgs more to see about getting nice clean borders showing up. If it all works out, I expect we'll migrate all the existing hardcoded polygons to svg. We're also looking at unicode character icons too.

duplicates stuff

The duplicates filter now prefetches the next five pairs of images, for faster image rendering (it used to just do the next pair). You can now alter this number under options->speed and memory.

I fixed an issue where flat colour images of the same num_pixels but differing resolution were counting as pixel duplicates.

The duplicates auto-resolution system now lets you do 'system:known url' and 'system:number of urls' for 'test A or B', and 'system:number of urls' for 'test A against B using file info'.

build stuff

I went on a 'cleaning out old libraries' kick this week, prompted by a user report about the PSD-reading library we were using (psd-tools). The psd library was pulling in a drawing library, aggdraw, which, in Linux at least, was including a very old and vulnerable version of a bz2 decoder. I don't know if this decoder ever actually ran for what we were doing, but I didn't like having this complicated library with possible security problems when all we use it for is grabbing resolution, icc profile, and a preview image. I hacked together a file parser and some other solutions we had lying around, including an ffmpeg renderer, and now the program no longer needs psd-tools. Some PSD rendering may be a little worse, but I also improved some transparency handling, so some files are better.

Similarly, I removed the swfrender executables from the bin directory. These are a fun old tool to make flash thumbnails, but the project has been discontinued for a long time, and the exes are very old and we shouldn't be relying on them, especially for a crazy format like flash. New flash files you import will get the default 'flash' icon. For the future, the excellent Ruffle library is putting together a modern version of this render executable, so when that is ready, I'll investigate bringing this functionality back.

On the other side of things, the AVIF library test last week went well, so I'm folding that in today. We should have better AVIF rendering.

next week

I want to integrate the 'A is an exact match of B' tech into the manual duplicate filter so we can test it with real world data.

[behindthewox]

Is there a list of all the fixes and improvements that have been made over the last 6 months?

I have not been active and therefore I've missed a lot of fixes, only hearing of them through other people who don't always have the complete information to share. I was waiting for a changelog post for a reliable update to make a blog post about all the helpful improvements I've heard about but that never happened... which is disappointing because I was looking forward to positive things to post about and practise some positive reinforcement. And good things need to be shared and celebrated, both big and small.

There is a new feedback forum, which is nice to see. I'm not sure it's a great idea to make separate feedback forums for WoP, WoO and "the rest" but I see the point. Some feedback is only relevant to certain sites and having it all in one place would require a tagging/filter system. I have more thoughts, but let's leave it at that for now.

So use the new feedback forums! This blog is still here, but it should be more of a last resort for when you feel like there's nowhere else to go.

For all WoX sites: www.feedback.worldofjademountain.com (the url is a bit misleading, but it's the one all WoX sites link to so...)

For all WoPotter sites: www.feedback.worldofpotter.eu

For all WoOlympians sites: www.feedback.worldofolympians.com

PS! Anyone wanna catch me up on the fixes and improvements that somehow never made it to the changelog?

Note: there's a few things in my inbox that I've been meaning to deal with but I haven't been in the right headspace for it. I'll get to it eventually.

[caratlibrary]

CARATLIBRARY OFFICIAL RULES

Membership Criteria

In order to be accepted as a member, you must be compliant with the following requirements:

You are an active SEVENTEEN writer. If you write for multiple groups, SEVENTEEN is one of them. 

You have at least one written work featuring a member of SEVENTEEN posted on your blog.

You are active (published at least one narrative work featuring a member of SEVENTEEN in the past year).

You have a masterlist or summative post with links to all your works.

If you write smut, you must be over the age of 18. 

Content Criteria

In order for your writing to be reblogged, it must be complaint with the following requirements:

All content must have appropriate content warnings at the top. We will not reblog any work supporting or containing uncritical portrayal of racism, sexism, transphobia, homophobia, fatphobia/disordered eating, or abuse.

All content must have a word count at the top.

Content longer than 500 words (not including warnings and summary at the top) must be under a readmore cut.

Smut must have appropriate warnings at the top and any explicit content must be under a readmore cut.

We only reblog written works that are narrative in nature. Narrative in nature means that the work must attempt to tell a story. Merriam-Webster: narrative (adj): having the form of a story or representing a story. As such, we will not reblog hard/soft thoughts, headcanons, MTL posts, and non-narrative reaction posts. 

Tracking Tag

In order to have your content reblogged:

You must use the tag #caratlibrary in the first five tags of the post.

This tracking tag is for members only. If you’ve changed your URL, please let us know so we can update our membership list.

The network will only reblog posts with the tag #caratlibrary– posts from members without the tag will not be reblogged.

Exclusion Criteria:

We will not tolerate:

Smut involving underaged characters (under 18)

Minors (under 18) publishing or interacting with smut

Plagiarism in any capacity

Behaviors exhibiting racism, sexism, transphobia, homophobia, fatphobia, or abuse. 

The application keyword is “melona”

Any instances of the exclusion criteria can be grounds for termination of membership.

Member Updates:

If you’d like to update your url, name, age, masterlist, or active status, please reach out to admins.

CHANGELOG: 09.18.2023: Rules posted

[thelaikaconstellation]

changelog

url changed!

from @/artarchivist to current

system moniker changed to "lotus"

we remade! this is our new "main" account

we follow/like from here

personal blogs masterlist (more active)

[piratesexmachine420]

If you, like me, never played Minecraft during its earliest years, it can be difficult to comprehend how unhinged its development cycle used to be.

Everything is Alpha, until they are or they aren't. Classic was Alpha until it wasn't. Indev was "in alpha" and then immediately forgotten so who even knows what it counted as. The game was "still in alpha" when Alpha was first released. Late Infdev was Alpha except for the all the places where it still said Infdev, besides when it was retconned in a blog post for no reason; early Alpha was Infdev except for all the places where it said Alpha; and also Infdev was still technically around at the time. Notch would constantly lie, or over-promise, or over-commit and balk. There was gonna be a Dungeons and Levers Expansion. There are somewhere between five and eight different versions of 0.0.15a and we straight up don't even know because nobody kept any damn changelogs. The private alpha went from 0.0.3a to 0.0.9a for no reason. 0.25_05 SURVIVAL TEST was the fourth patch of 0.25. You would just open Tumblr or IRC and find out that everything was different. Half the time there wouldn't even be a new version number. You couldn't go back if you wanted to. At one point in early September, 2010, there were five different versions of the game all available at completely different URLs. Skeletons used to shoot purple arrows.

[moko1590m]

2025年05月22日 14時00分 「AIがMicrosoftの従業員を徐々に狂わせていく様子を見るのが趣味」というネットユーザーの投稿が話題に 2025年5月19日、GitHubが実装しているAIツール「GitHub Copilot」の新機能「コーディングエージェント」がパブリックプレビュー版で公開されました。この機能はGitHubのIssueをCopilotに割り当てるだけでCopilotが解決してくれるというものですが、実際の動作を見るとあまりにもダメダメであるとの投稿が話題になっています。 GitHub Copilot coding agent in public preview - GitHub Changelog https://github.blog/changelog/2025-05-19-github-copilot-coding-agent-in-public-preview/ GitHub Copilotのコーディングエージェントは、コードを検証して編集し、テストも行い、それぞれのIssueにコメントを残すところまで実行してくれるAIエージェントです。 このエージェントは既にMicrosoft公式リポジトリの「runtime」に導入されているのですが、コーディングエージェントが「解決した」としている問題が実際には解決していなかったりするなど、いくつかの問題があることがわかっています。 例えば「ハイブリッドグローバリゼーション用のCompareInfo.Versionを実装する」というプルリクエストでは、Microsoftの開発者であるマトゥス・コザク氏らがGitHub Copilotに修正を依頼していますが、GitHub Copilotは何度も何度もテストに失敗したり、不自然な修正を実施したりする様子が見られます。 別のプルリクエストでも多数失敗しており、「AIのために時間を無駄にするのをやめて、自分で問題を解決したらどうですか？大量の電力を、質の悪いコードを出すマシンのために無駄にしているのです」との批判コメントまで付けられています。 オンライン掲示板のRedditでは、「私の新しい趣味：AIがMicrosoftの従業員を徐々に狂わせていく様子を見る」と題する投稿が話題となり、「AIが『直しました』と言い、人間が『いいえ、まだ壊れています』と言い、AIが変更を加えて『問題ありません、直りました』と言い、さらに数回繰り返すところが気に入っています」といったコメントや、「残念なことに、私もまさにこのパターンに従う人間の開発者と一緒に働いたことがあります」とのコメントのほか、「問題は、今後10年間でモデルが実際に改善され、実現可能になるという確かな証拠がないことです。テストと研究はとも��く、製品に導入するのは全く別物です。大手ソフトウェア企業は、株主の利益を満足させるために運営されています」など、未完成で不確かな製品を公開することに異議を唱えるコメントが付けられました。 なお、GitHub Copilotのコーディングエージェントは有料サービスのCopilot Pro+およびCopilot Enterpriseの契約者に提供されており、GitHub CLIだけでなくiOSとAndroidのGitHub Mobileユーザーも利用できるようになります。記事作成時点ではあくまでパブリックプレビュー版であり、今後機能の改善が期待されます。 この記事のタイトルとURLをコピーする ・関連記事 GitHubにソースコードの「続き」を自動で補完する機能「GitHub Copilot」が登場、OpenAIの協力により - GIGAZINE ソースコードの「続き」を自動で補完する「GitHub Copilot」がすべてのユーザーに利用可能へ - GIGAZINE コード補完AIのGitHub Copilotは著作権問題に加え「オープンソースコミュニティを破壊する危険性」がある - GIGAZINE ついにGitHubのコードで学習したAI「GitHub Copilot」が集団訴訟に直面 - GIGAZINE Microsoftはコード補完AIツール「GitHub Copilot」でユーザー1人あたり月額3000円近くの損失を出しているという報告 - GIGAZINE 「GitHub Copilotがコードを違法にコピーしている」と主張する開発者による訴訟の大部分を裁判所が棄却 - GIGAZINE GitHub Copilotでコードの品質は改善されるのか？ - GIGAZINE GitHub Copilotに無料プランが登場、機能面での制限は少ないものの月間使用回数に制限あり - GIGAZINE GitHubで非公開にされたはずのリポジトリがMicrosoftのAIアシスタント「Copilot」を通じて公開されていたという指摘 - GIGAZINE ・関連コンテンツ GitHub用の「Copilot Extension」が登場、DataStax・Stripe・MongoDBなどを外部アドオンとしてCopilotに組み込むことが可能に OpenAIがAIベンチマーク「SWE-Lancer」を公開、フリーランスエンジニアに100万ドルで依頼するレベルのタスクをこなせるか測定 GitHubの無料ユーザーもプライベートリポジトリを無制限で使用可能に MicrosoftがうっかりMITライセンスプロジェクトをMicrosoft名義に書き換えて謝罪 GitHubのソースコードで学習したプログラミングAI「Copilot」は著作権侵害なのか？ UNIXのmanコマンドに6年間誰にも気付かれずに眠っていたイースターエッグとは？ Microsoftが新ブラウザ「Edge」初となる拡張機能の詳細を誤って公開 「無料が基本」のオープンソース文化圏で有料ソフトウェアの販売は受け入れられるのか？

「AIがMicrosoftの従業員を徐々に狂わせていく様子を見るのが趣味」というネットユーザーの投稿が話題に - GIGAZINE

[perfectdocumentation]

Effective API Documentation Strategies (With an API Documentation Example)

Effective API documentation is the backbone of a developer-friendly product. Whether you're offering a RESTful service, GraphQL endpoint, or SDK, your documentation must be clear, comprehensive, and easy to navigate. Poor documentation can discourage developers, increase support requests, and slow down adoption. Here are key strategies to ensure your API documentation is both useful and user-friendly.

1. Know Your Audience

Understanding who will use your API is the first step. Are they beginner developers or experienced backend engineers? Tailor your tone and examples accordingly. Use plain language for newer audiences and more technical depth for advanced users.

2. Organize Content Logically

Structure your documentation for ease of navigation. A typical layout might include:

Overview – What the API does

Authentication – How to get access

Endpoints – Core functionality

Examples – Real-world use cases

Errors – How to interpret error messages

SDKs & Tools – Any helper libraries available

Using a sidebar or table of contents can help users quickly jump to the relevant section.

3. Use Interactive Elements

Interactive documentation improves the developer experience. Tools like Swagger (OpenAPI), Postman, and Redoc allow developers to test endpoints directly in the browser. This can dramatically reduce the time it takes to understand and use the API.

4. Provide Clear Code Examples

Examples are often the most viewed part of API docs. Include request and response examples in multiple languages if possible (e.g., cURL, Python, JavaScript). Annotate them to explain each part of the request and what to expect from the response.

5. Be Honest and Upfront About Limitations

Transparency about rate limits, known issues, or incomplete features helps build trust. Include a changelog or release notes section so developers can track updates.

6. Keep It Updated

Outdated documentation is worse than no documentation. Set up version control and a documentation workflow that updates the docs with each API change. Use automation when possible.

✅ API Documentation Example (REST API – Notes Service)

Base URL: https://api.notesapp.io/v1

🔐 Authentication

All requests must include a bearer token:

http

CopyEdit

Authorization: Bearer YOUR_API_TOKEN

📄 GET /notes

Description: Retrieve a list of notes.

Request:

http

CopyEdit

GET /notes Host: api.notesapp.io Authorization: Bearer YOUR_API_TOKEN

Response:

json

CopyEdit

[ { "id": "note_123", "title": "Meeting Notes", "content": "Discuss Q2 goals...", "created_at": "2025-04-15T09:00:00Z" } ]

📝 POST /notes

Description: Create a new note.

Request:

http

CopyEdit

POST /notes Content-Type: application/json Authorization: Bearer YOUR_API_TOKEN { "title": "New Note", "content": "This is a test note" }

Response:

json

CopyEdit

{ "id": "note_456", "title": "New Note", "content": "This is a test note", "created_at": "2025-04-17T14:32:00Z" }

Conclusion

Great API documentation empowers developers, reduces friction, and enhances your product’s adoption. By combining clear structure, real-world examples, interactive elements, and ongoing maintenance, you create a reference that developers trust—and love to use.

[aakashweb]

WP Socializer v7.9 Release

WP Socializer v7.9 is now available. This is a maintenance release that includes a number of enhancements and bug fixes. It is now available for both free and PRO versions.

Please find the changelog below. You can also follow us on Twitter for latest updates @aakashweb

✨ Changelog

New: Support for Bluesky icon.

New: Support for Podcast icon.

Fix: Social profile links in follow bar are set with rel=”me” value.

Fix: Handle follow icons editor crash when Elegant page builder is installed.

Fix: Theme customize page is misaligned.

Fix: Disable share buttons in REST API output.

Fix: null check when current page URL is not available.

Getting the update

You can update the plugin directly from your WordPress administration page by navigating to Dashboard > Updates. This applies to both free and PRO versions of the plugin.

You can also download the free version of the plugin from WordPress.org and upload it manually. For the PRO version you can follow the documentation. If you haven’t got the PRO version yet, you can get it here.

-----

This article was originally posted on Aakash Web

[warrenwoodhouse]

Keep a Changelog on GitHub

[lexyeevee]

Lexy's Labyrinth changelog

it's been two years since i last mentioned it here, and i did a bunch of work on it over the past month or so. here's some of it

• added Chip's Challenge Level Pack 5, a new pack of 149 community levels, which you can jump directly into

• you can finally just hold R to restart the level

• added some saturation to the tileset and made some tiles easier to distinguish visually

• it's more clear what actually killed you

• it's pink now

• rewind uses a third less memory, and some work has been done with an eye for maybe having unlimited rewind in the future

• it's now 99.5% compatible with Chip's Challenge 2, which is pretty cool, and can also match the original Lynx rules fairly faithfully

• MSCC mode that makes everything move instantly, i don't know why you would play like this though

• a small percentage of CC1 levels can't be beaten under the default CC2-like rules, but via shenanigans, some of those have been made playable without having to change the compat mode

• shared levels encode into URLs that are about a third shorter

• the level editor has a bunch more bells and whistles (some still in progress)

i made a free, open source, web-based chip’s challenge (1+2) emulator a bit ago

features include:

works both on a computer and on a phone…  more or less

comes with ~800 community levels, plus it can load levels in any format (including from the commercial games, either the classic version or the ones on Steam)

built-in level editor where you can make your own levels and share them with just a link

totally original art, sounds, and music, though you can load in the classic tileset if you really want to

undo and rewind

now you are a fox solving puzzles for fun, instead of bill gates being kind of weird about a girl

a couple tiny emulation bugs still, oh well

✨ Lexy’s Labyrinth ✨

[goblin-social]

Changelog, 13/12/2023

AKA: What it has been done these past few days

1. People have spoken! We now have a glorious single reblog/quote button instead of one per each action:

2. Now reblogs with content have a different counter than regular reblogs (all the reblogs used to be counted as normal 'reblogs' and quote-reblogs just didn't have any metric on its own)

3. Also, you now can quote-reblog a post without adding any text, as long as you add some tags, as god intended when she created quote-reblogs (also, now the posts you are reblogging don't include the previous tags in the reblog trail of your post... ahem, that was a mistake, they never were supposed to be there).

4. Added url previews on posts! you add an url? you add an url like the football? previews! 100s of previews for mother!

5. When you reblog an image-only post now, the image is shown in the editor too (it was showing only text before)

6. Fixed tags showing up twice in some posts. Also make them look cooler. :sunglasses:

[hydrus]

Version 578

windows

zip

exe

macOS

app

linux

tar.zst

I had a good week mostly doing some simple work. In a bonus, animated webps are now fully supported.

full changelog

highlights

Animated webp decoding is not widely supported, but we discovered a method this week and I plugged it into my old (slightly janky) native animation viewer. I have made it work just like the for gif and (a)png, where, within hydrus, images and animations will count as different filetypes. On update, all your existing webps will be queued for a rescan. If they are actually animated, they will become 'animated webp' and get num_frames and a duration, and they'll play animated in the media viewer. Let me know if you run into any trouble with it!

I added an 'eye' icon menu button to the top hover window in the media viewer. It has those five new checkboxes for 'draw stuff in the background' I added last week, and I expect to add 'always on top' and similar options to it in future.

The 'known urls' media menu has a couple changes. It is now just called 'urls'; it gets a 'manage' command, moved from the 'manage' menu; and you can now open an URL 'in a new page' (i.e. opening a new search page with 'system:known url=blah'), so if you need to find all the files that have a particular URL, this is now just one click.

next week

I am now on vacation for a week. As normal I'm just going to disappear to shitpost fake-E3 and otherwise try diligently to achieve nothing of any importance. I'll be back Saturday 15th, with v579 on Wednesday 19th. Thanks everyone, see you later!