Just received my new ArmSoM Sige7 and started testing the provided Ubuntu 22.04...

Just received my new ArmSoM Sige7 and started testing the provided Ubuntu 22.04 image and Rockchip loader. Flashed the board, set up the system, and ran initial CPU stress tests. Power usage looks great: ~7.5W under full load and ~2.5W idle, with temps staying cool and the fan barely audible. Promising start for this RK3588-based board! [...]

https://sapiolab.nl/just-received-my-new-armsom-sige7-and-started-testing-the-provided-ubuntu-22-04

【繁體中文版】

📝 Sharkey/Misskey 實例重裝後的聯邦宇宙同步問題解決指南

如果你曾經重新安裝過 Sharkey 或 Misskey 實例，可能會遇到一個棘手的問題：其他實例的使用者突然無法與你正常互動了！

🔴 常見症狀：
• 好友請求卡在待處理狀態，無法接受或拒絕
• 你的大頭貼和橫幅圖片在其他實例上顯示不出來
• 遠端使用者嘗試互動時會收到錯誤訊息

🔍 問題根源：
這是因為 ActivityPub 協議設計時，假設每個使用者的識別碼（Actor URI）是永久不變的。但當你重裝實例後，系統會生成全新的使用者 ID 和加密金鑰，導致其他實例快取的舊資料失效。簡單來說，其他伺服器還在用舊地址找你，當然找不到！

✅ 解決方案：
最有效的方法是請對方實例的管理員刪除你的舊使用者記錄，系統就會自動重新抓取你的新資料。雖然會失去追蹤關係和歷史互動記錄，但這是最乾淨的解法。如果想保留資料，也可以選擇手動更新公鑰，但操作較為複雜。

💡 預防建議：
重裝實例前記得備份資料庫和設定檔！未來 ActivityPub 社群也正在開發身份可攜性的標準，希望能從根本解決這個問題。

#Sharkey #Misskey #ActivityPub #聯邦宇宙 #Fediverse #技術筆記 #實例管理 #去中心化社交

【English Version】

📝 Solving ActivityPub User Sync Issues After Sharkey/Misskey Reinstallation

If you've ever reinstalled your Sharkey or Misskey instance, you might have encountered a frustrating problem: users from other instances suddenly can't interact with you properly!

🔴 Common Symptoms:
• Follow requests get stuck in pending status, unable to accept or reject
• Your avatar and banner images don't display on other instances
• Remote users receive error messages when trying to interact with you

🔍 Root Cause:
This happens because the ActivityPub protocol assumes that each user's identifier (Actor URI) is permanent. When you reinstall your instance, the system generates a completely new user ID and cryptographic keys, causing the cached data on other instances to become invalid. Simply put, other servers are still looking for you at your old address!

✅ Solutions:
The most effective approach is to ask the admin of the remote instance to delete your old user record, allowing the system to automatically fetch your new data. While this means losing follow relationships and interaction history, it's the cleanest solution. If you need to preserve data, you can manually update the public key, though this is more complex.

💡 Prevention Tips:
Always backup your database and configuration files before reinstalling! The ActivityPub community is also developing identity portability standards to fundamentally solve this issue in the future.

#Sharkey #Misskey #ActivityPub #Fediverse #TechNotes #InstanceAdmin #DecentralizedSocial #FediverseTips

【日本語版】

📝 Sharkey/Misskey 再インストール後の連合宇宙同期問題の解決ガイド

Sharkey や Misskey のインスタンスを再インストールしたことがある方は、厄介な問題に遭遇したかもしれません。他のインスタンスのユーザーが突然正常にやり取りできなくなるのです！

🔴 よくある症状：
• フォローリクエストが保留状態のまま、承認も拒否もできない
• あなたのアバターやバナー画像が他のインスタンスで表示されない
• リモートユーザーがやり取りしようとするとエラーメッセージが表示される

🔍 問題の根源：
これは ActivityPub プロトコルが各ユーザーの識別子（Actor URI）が永久不変であることを前提に設計されているためです。インスタンスを再インストールすると、システムは全く新しいユーザー ID と暗号鍵を生成し、他のインスタンスにキャッシュされた古いデータが無効になります。簡単に言えば、他のサーバーはまだ古いアドレスであなたを探しているのです！

✅ 解決方法：
最も効果的な方法は、リモートインスタンスの管理者にあなたの古いユーザーレコードを削除してもらうことです。そうすれば、システムが自動的に新しいデータを取得します。フォロー関係や過去のやり取り履歴は失われますが、これが最もクリーンな解決策です。データを保持したい場合は、公開鍵を手動で更新することもできますが、操作はより複雑になります。

💡 予防のヒント：
再インストール前には必ずデータベースと設定ファイルをバックアップしましょう！将来的には ActivityPub コミュニティがアイデンティティの可搬性に関する標準を開発しており、この問題を根本的に解決できることが期待されています。

#Sharkey #Misskey #ActivityPub #連合宇宙 #Fediverse #技術メモ #インスタンス管理 #分散型SNS #連合型SNS #developer

It seems that I am becoming experienced with migrating very old Windows 10 installations on older hardware to newer hardware and then upgrading them to Windows 11.

The whole process is time consuming. Sometimes it is fairly easy, sometimes there's a whole lot of things that need to be done.

The one I am working on now was originally on an HP Pavilion desktop PC with a 1st Gen Intel i3 processor.

Had to convert SATA mode from RAID to AHCI.

To get a CloneZilla clone of the system, I had to fix an MBR GPT mismatch by deleting the GPT info, as this Windows 10 install was Legacy boot, not yet UEFI.

sgdisk -z /dev/sda (where sda is the drive to remove the GPT info from)

Did a full backup using Samsung Data Migration to a Samsung SATA SSD before that, just in case that operation caused data loss or a problem.

Then resized and moved partitions using gparted.

I planned on restoring the CloneZilla image to an nvme drive, not a SATA drive (as it was originally). So in order for Windows to be prepared for that, and not get an "inaccessible device" error, I ran this command in Windows right before making an image:

sc.exe config stornvme start= boot

Then got a CloneZilla image. Cloned it to another machine that could do both legacy and uefi boot (the original machine could only do legacy).

After all that, the commands to convert from legacy to uefi boot didn't work because there was no recovery partition. I had to copy the winre.wim file from another Windows installation (got it from another customer computer that I have currently with Windows 10).

Had to put that winre.wim file in C:\Windows\System32\Recovery - then run "reagentc /enable" to enable the recover environment.

Then this command worked:

mbr2gpt /convert /allowFullOS

It would not before enabling the recovery environment.

Next step is rebooting the machine in UEFI mode and making sure the Windows 10 installation has, in fact, been converted from mbr to gpt.

When that is done, I can run the upgrade process from Windows 10 to Windows 11 using an installer created by the rufus disk creator utility that bypasses the hardware checks Windows 11 normally has.

After a successful upgrade, I can finally move it to the newer computer that the customer purchased from me.

#Windows #Windows10 #Windows11 #CloneZilla #TechNotes

Développeurs : Technotes ajoute des notes de la communauté sur la documentation d’Apple http://dlvr.it/TLkG0R #Développeurs #Technotes