stgiga

@wikifur.bsky.social CloudFlare is keeping the site from loading and it's happened long before the recent outage.

If you'd like to commission me, but don't want to use Fiverr, or would rather not donate through GoFundMe, I also have a Ko-Fi page.

ko-fi.com/zeerathezesty

Again, I hate to plug things and self promote like this, but it's pretty desperate for me right now.

(3/3)

If you’d prefer a commission instead, my commissions on Fiverr are still open. My rates are as follows:

Voice Acting - Starting at $10 per 100 words - www.fiverr.com/s/yv6WR76

Pixel Art - Starting at $10 for a character frame up to 48x48, or a tileset up to 128x128 - www.fiverr.com/s/o8yWXWN
(2/3)

Hello everyone. I hate having to talk about this, but I haven't been doing well financially lately. I likely won't be able to pay rent next month. I started a GoFundMe in August, and it's still up now, but things are dire for me by the end of this month

www.gofundme.com/f/donate-to-...

(1/3)

stgiga.itch.io/Tyroland now fully supports SC-8850
And yes, this means that I'm now the holder of the first full 88Pro AND first full 8850 sf2 records

@qntm.org So Unicode 17.0 drops tomorrow in my time zone (I, and Unicode, are in California), and I know you spoke about maybe getting Base131072 made real around the time Unicode 17 drops.

YouTube thinks I don't own part of my original song and you can find more out on @stgiga.blahaj.zone.ap.brid.gy

Personally, given Base32768 (& Base46341, Base55109, & Base57053)'s extreme efficiency, it's honestly worth wrapping compressed data in it like I did, because it preserves compression gains quite well compared to something like a Base64'd archive. It's a justifiable part of a file format IMHO.

Tinygma's Base32768's use of three giant ranges rather than tables makes cleaner code. Of note is that only one padding character, U+C200, is used, & only one of them exists when padding is needed. Also because of the use of Base32768, technically BWTC32Key's .B3K files aren't truly binary.

Keep in mind that I consider Base32768 to be one of the best ideas ever, and if you're the one who did it first, I'm impressed. It's *the* reason I consider UTF16 justified. Base32768 is just OP. Also I was in high school when I got involved with Base32768. I'm currently in uni.

Basically what had happened was that way back in 2018-2019 I tried using your library in browser JavaScript, but unlike CompressJS-flattened, it didn't work. So I spent around 6 months searching and saw Tinygma's on Qiita by kusano_k and used that. Apparently it can work in Node too.

Oh I'm aware. Having said that, at least from my understanding there are worse characters in terms of normalization. I had wanted to use your scheme but it was too tied to Node so I had to use Tinygma's one, which uses these ranges and works in Node too. With help, BWTC32Key has a Node port. 1/?

Base57053 (plus the padding) just clears maximum (no PUA, no noncharacters), and in it, every 5 characters holds 79 bits. However anything past Base32768 has unclean math AND diminishing returns in terms of savings because Base32768 is already so good. Plus font support becomes Unifont after 15.25

2/? If you use a lot more blocks to get 46341 characters, you can fit 15.5 bits (every two 16bit characters has 31 bits inside), if you use every assigned Plane 0 character (the magic number is 55109), you can fit 15.75 bits (every 4 characters holds 63 bits). Unassigned gets you to 57054 or 2^15.8

@qntm.org Apparently it's possible to go beyond the 15 bits per 16bit UTF16 character of Base32768 if you span multiple characters. BWTC32Key uses u3400-u4d01+u4e00-u9eff+uAC00-uC200 but using the entirety of the relevant blocks plus the 472 compatibility Ideographs puts you at 15.25 bits 1/?

For context, my VRChat existence came *after* all the updates. I joined the platform in November. I DO know that the issue happens when I do a "Save As" on a new .unity file. The way the issue manifests is that it somehow can't find the material for the trails, or it gets replaced with default blank

3/?
I know that VRoid, VRChat, and even the plugins needed for VRChat avatar creation have been getting updated often recently. It would seem that VR is "in"/cool again, given how very recently VRoid has emphasized VRChat use. Also, Pride is something the world needs right now. (Also I'm nonbinary.)

2/?
The bug also affects other particles (including ones by other authors at random), which makes me strongly suspect that an engine/Unity update happened that broke something. And given that you updated your particles in 2024, it would seem such the breaking update was quite recent.

Also your YouTube tutorial on how to install particles was invaluable in getting the particles I DID find on Booth's 0 Yen side to work on my avatar. Also of note is that the glitch doesn't just affect Pride particles (stuff like your music notes and Cyber/Glitch particles suffers the bug) 1/?

I sent you a DM and a follow so hopefully *that* gets Bluesky to recognize them. I predominantly use a Mastodon fork and would rarely use Twitter (not that I ever nuked everything), so Bluesky is a bit new to me. I only use Bluesky or Twitter if I have to reach out to someone who isn't on Mastodon.

Regarding the VRChat SDK

As for Unity, I'm using Unity 2022.3.22f1. I know you updated these assets in 2024, and I've used Unity 2019 assets in my 2022 project (I used a metric ton of other particles and stuff, and I currently have 17x the "official" maximum, but nowhere near the technical limits).

I'm using 3.7.6, the latest version.

@chimericcurios.bsky.social
The issue is that prefabs show up in the editor as blank, except for the flag ones. But loading THOSE into a test avatar results in the model showing up as an error ingame. My avatar doesn't do anything too wild (it IS a heavily-tricked out VRoid avatar.)

@chimericcurios.bsky.social
I'm having trouble getting your Pride trails for VRChat to work on my avatar. I'm using Unity 2022 and the latest versions of everything.

I'd advise running Base131072gen after Unicode 17 releases, unless you're worried about support. I'm currently waiting for Unifont 17 before doing certain things to UnifontEX. I can't wait 6 more months.

Actually it was due to the addition of 4000 Egyptian Hieroglyphs. At least the good news is that Base131072 is possible. I'd jokingly call it the "all-Unicode" encoding. Keep in mind that I have a vested interest in Base32768 as someone whose app uses a browser version.

Let me guess: "Symbols for Legacy Computing Supplement" helped make the difference.

I'm wondering what Unicode version became safe?

@qntm.org Apparently Unicode 17 is going to add over 4900 new Han characters (CJK Extension J), and I feel like the "safe" ranges for Base131072 should be assessed based on this.

Notch is a racist. Notch is a misogynist. Notch is a homophobe and transphobe. Do not give Notch your support. Do not give Notch your money.