Comments

3

nitori wrote

he does have a point tho even though i dislike british people. embrace the bitter :P

4

nitori wrote

I think the senators are vegans who are just hungry for salad so this is fine

5

nitori wrote

i love [...] 12-hour clocks

Counterpoint: 13:12

1

nitori wrote

Society if DNSSEC, PGP, and IP E2EE was adopted by everyone in day one:

2

nitori wrote

They say it's federated but it only kind of is, mostly it's one big instance just like twitter, controlled by one company that seem to have a pretty unclear business model.

I'm not a Bluesky simp but this is the case with Mastodon too lol

Federation is just shit. Tbh I've been questioning recently whether to continue microblogging with my Mima-sama identity at my Misskey home at makai.chaotic.ninja... I might as well just do my microblogging here in jstpst. :P

1

nitori wrote

I'm still waiting on my fediring application lol

2

nitori wrote

Many browser developer tools allow viewing a page’s media; for example, the Network Inspector allows rendering the body of an individual request. A request for an image inside a spoiler should not unnecessarily bypass this. Browsers with such features shouldn’t ship spoiler support until a developer-tools toggle for “show spoiler contents” is ready. Should this also apply to spoiler text?

I think if a user is going to inspect element a webpage, they kinda have already waived their right to not get so surprised by secrets. This just seems like more unnecessary complexity for browsers for little gain.

4

nitori wrote

NTFS is fine imo if you're sticking to windoze, so NFTS it is

1

nitori wrote

Alright just setup a HTTP 307 web forward in my nginx and pointed to my own IP in dnsmasq lol

(Realized I can't do CNAME or manually putting jstpst's IP into hosts because that will break TLS lol)

2

nitori wrote

brb, pointing mostlyget.net to jstpst.net's IP in my DNS server's /etc/hosts