redcalcium

joined 1 year ago
[–] redcalcium@c.calciumlabs.com 8 points 1 year ago* (last edited 1 year ago) (1 children)

If you add support for kbin, you'll probably going to add support for kbin's microblogging feature. If you added support for kbin's microblogging, might as well add mastodon support. Heck, might as well add pixelfed support to the mix, why not? Voila, now you have a super federated app.

[–] redcalcium@c.calciumlabs.com 32 points 1 year ago

It's not 3rd party app developers fault that kbin didn't have any stable api yet. Now that they fast track the api development, I think we can expect more 3rd party apps coming soon.

[–] redcalcium@c.calciumlabs.com 14 points 1 year ago (1 children)

Revolt!? That dog is fucking embrace it!

[–] redcalcium@c.calciumlabs.com 30 points 1 year ago* (last edited 1 year ago) (2 children)

Who cares if it already exists, just make it.

Also consider the possibility when the other, more popular projects got enshittified. Now the fleeing users have an option to switch to your project. It actually happened on one of my side project. I made it because I want to try building my own version of X. It got ~2000 users, but later down the road, X got sold to a new shitty owner that waste no time to enshittify it, and my side project suddenly grow to 20,000 users overnight.

[–] redcalcium@c.calciumlabs.com 12 points 1 year ago

Investors: shut up and take my money!

[–] redcalcium@c.calciumlabs.com 1 points 1 year ago* (last edited 1 year ago) (1 children)

uBlock Origin is already less effective when running in Chrome than in Firefox. For example, it can't detect CNAME cloaking on Chrome, while it can do that in Firefox. When Chrome finally enforce manifest V3, uBlock Origin will be even more neutered in chrome due to limited number of blocking rules.

[–] redcalcium@c.calciumlabs.com 1 points 1 year ago (1 children)

I got curious so I start digging into how mastodon do it. It's more like a hack, really. Mastodon uses WebFinger to resolve user account, so when you change domain, you can leave the old domain up so your federated servers can still resolve your users and realized the domain has been changed and update their federation data. But it turns out you can't exactly retire the old domain either because it's still tied to user account internally. So if you lose control of your old domain, you're probably as screwed as fmhy.ml.

I'd like to think FMHY was true to their name and didn't pay for the domain.

[–] redcalcium@c.calciumlabs.com 4 points 1 year ago (1 children)

.ee is owned by Estonia. Just pray Estonia wouldn't do the same shenanigan and cause your instance to go down.

Who know deleting a power user account could DDOS the entire federation?

[–] redcalcium@c.calciumlabs.com 1 points 1 year ago* (last edited 1 year ago)

I haven't noticed any performance issue so far. I think they use wasm which help with speed. Too bad it's not open source, but the fact it's developed by a single guy working on it full time is actually very interesting, considering the webapp is actually work better than some apps developed by bigger teams. It can even edit PDF and gif!

[–] redcalcium@c.calciumlabs.com 4 points 1 year ago (1 children)

At least for Lemmy, you can "force" it to sync a particular post or comment by pasting the url into your instance's search bar.

 

Meanwhile in my computer running OpenWorm:

 

Unlike other browser-based x86 emulators, OSes running inside v86 can actually access internet via a transparent proxy relay. You can load your own OS images, or choose one from a pretty comprehensive list (Arch Linux, Windows 1.01 to 2000, SerenityOS, *BSD, Android 1.6, Haiku, QNX, and so on).

The VM images are loaded in stages, so it boots fast. When you run a program or code that's not loaded yet, it'll fetch the image and perform a JIT compilation of x86 code to wasm. The delay when fetching additional images and performing JIT compilation is noticeable, but the program run fast afterward considering this is a full x86 emulator running entirely within a web browser.

view more: next ›