e0qdk

Thanks!

Very cute, but I don't understand the title. (Is that Ahahahahaha in Chinese, maybe?)

Aww, I'm not trying to stomp anyone. :(

I was just curious if it was actually the full list and before I knew it I'd spent 45 minutes checking Pokemon names to figure out what was missing, so I figured I'd share the corrections.

If Kolanaki got that close just from memory, that's pretty impressive! I had to look it up!

• Electrode, Diglett, Nidoran♂, Mankey, Venusaur, Rattata, Fearow, Pidgey, Seaking, Jolteon, Dragonite, Gastly, Ponyta, Vaporeon, Poliwrath, Butterfree, Venomoth, Poliwag, Nidorino, Golduck, Ivysaur, Grimer, Victreebel, Moltres, Nidoking, Farfetch'd, Abra, Jigglypuff, Kingler, Rhyhorn, Clefable, Wigglytuff
• Zubat, Primeape, Meowth, Onix, Geodude, Rapidash, Magneton, Snorlax, Gengar, Tangela, Goldeen, Spearow, Weezing, Seel, Gyarados, Slowbro, Kabuto, Persian, Paras, Horsea, Raticate, Magnemite, Kadabra, Weepinbell, Ditto, Cloyster, Caterpie, Sandshrew, Bulbasaur, Charmander, Golem, Pikachu
• Alakazam, Doduo, Venonat, Machoke, Kangaskhan, Hypno, Electabuzz, Flareon, Blastoise, Poliwhirl, Oddish, Drowzee, Raichu, Nidoqueen, Bellsprout, Starmie, Metapod, Marowak, Kakuna, Clefairy, Dodrio, Seadra, Vileplume, Krabby, Lickitung, Tauros, Weedle, Nidoran♀, Machop, Shellder, Porygon, Hitmonchan
• Articuno, Jynx, Nidorina, Beedrill, Haunter, Squirtle, Chansey, Parasect, Exeggcute, Muk, Dewgong, Pidgeotto, Lapras, Vulpix, Rhydon, Charizard, Machamp, Pinsir, Koffing, Dugtrio, Golbat, Staryu, Magikarp, Ninetales, Ekans, Omastar, Scyther, Tentacool, Dragonair, Magmar
• Sandslash, Hitmonlee, Psyduck, Arcanine, Eevee, Exeggutor, Kabutops, Zapdos, Dratini, Growlithe, Mr. Mime, Cubone, Graveler, Voltorb, Gloom, Charmeleon, Wartortle, Mewtwo, Tentacruel, Aerodactyl, Omanyte, Slowpoke, Pidgeot, Arbok

I noticed while making this list that Lickitung was incorrectly spelled "LIKITUNG" on the third day.

Edit: Also, for Nidoran♂ vs Nidoran♀ you have to look at the picture to distinguish since they just say "Nidoran" but they do say it twice!

That's pretty good! But... that's only 147. :-)

Nidoran♀, and Nidoran♂ are separate and you're missing Nidorina, Nidoqueen, and also Rhydon.

Some other corrections:

• Pigeotto -> Pidgeotto
• Ninetails -> Ninetales
• Diglit -> Diglett
• Primape -> Primeape
• Duouo -> Doduo
• Cloysyer -> Cloyster
• Ghastly -> Gastly
• Electrabuzz -> Electabuzz
• Gyrados -> Gyarados
• Omantyte -> Omanyte
• Arodactyl -> Aerodactyl

(Yes, I looked it up. No, I have no life. :p)

Cheers!

Everything I've set in Settings is forgotten: Default Listing reverts to All, Default Post Sort reverts to Hot, and so on.

mlmym (the "old" interface) stores its front-end specific settings in your browser via cookies and local storage. The way it's implemented works for the most part and probably makes the front-end simpler, but has some downsides like not retaining your choices between logins. There's an issue open for this in the bug tracker: https://github.com/rystaf/mlmym/issues/104

I'm not sure why it forces a logout periodically even when you're using it regularly though. (I mean, the cookies are probably not being updated and just expire eventually -- but I don't know if that was a deliberate choice or not.) It might be a good idea to open an issue for this?

kbin.social has been totally down for a while. I don't think your posts are actually federating when you post into a kbin.social magazine right now; the votes you are getting are probably from other lemmy.world users only.

I don't recognize the main dish or dessert -- beyond being some sort of pudding presumably with blueberries and something else on top.

What are they called?

[...] male-gazey content. I am 2) a woman extremely disinterested in that.

I feel some men might also not want to see content focused on games where a big goal is to romance a man as a woman, presented in a femgazey way or a way tailored to our desires even if not sexualized.

Fair enough. There are a lot of eroge where you play as a women that are absolutely, clearly intended to be played by men though; that part alone isn't likely to be off-putting, but I can see specific presentation and femgaze heavy works being just as off putting to some guys as malegaze heavy works are to some women. If the audience is mostly straight guys, posting fan art of something like an explicit BL work probably isn't going to get much positive response, I suppose. :-)

There's so little content posted regularly in the visualnovels community though that I feel like anyone actively trying to start discussions there on the subject of VNs would likely be welcomed, but I might be wrong about that. The most successful posts I've seen are generally notices about sales and some business news with people occasionally posting memes and such as well.

If that doesn't feel right to you though, I get it, and hopefully reviving the other community works out.

Is the issue that the posts will be frequently inaccessible?

I don't think your posts are federating out at all when kbin.social is down -- basically only people on your own instance can see it, if I understand how federation works correctly. If you check the view of the community from lemmy.world the last post visible is from a month ago, for example -- https://lemmy.world/c/Otomegames@kbin.social?dataType=Post&sort=New -- even though I can see on your instance that you've started several threads since then. I can't even load the community from reddthat since it was probably never requested and kbin.social is down currently; it just errors out.

Does Lemmy have a way to get inactive mods removed and replaced?

I don't know. Tagging @Blaze@reddthat.com for suggestions since they've been trying to grow the Fediverse for a while and may know how to go about it, if it's possible.

kbin.social's been down for a while, and having serious problems for months.

There is a general visual novel community at !visualnovels@lemmy.comfysnug.space which might be a better place to post to. It's not very active, but I know there are at least a few people around paying attention to it. I might chime in on some threads occasionally if you post there. My tastes are more in line with VNs aimed at the straight-male demographic, but I'm willing to try other VNs beyond that if there is a really good story or novel mechanics or some other non-sexual factor that makes it interesting.

If that community doesn't fit your needs, I think there is also !otome_games@lemmy.world -- but it seemed completely dead the last time I looked. You might be able to revive it though if you want to try.

I was curious, so I did some searches on this topic for you and found these pages:

• https://news.ycombinator.com/item?id=18155134
• http://www.catb.org/esr/faqs/practical-python-porting/

The second link in particular notes:

The reason that things are much easier with all ASCII data is that practically every Unicode encoding in existence maps bytes 0x00..0x7f to the corresponding code points, so byte strings and Unicode strings that contain the same all-ASCII data are basically equivalent, even semantically. What usually trips people up with non-ASCII data is that the semantic meaning of bytes in the range 0x80..0xff changes from one encoding to another.

But, thinking like a systems programmer again, for many purposes the semantic meaning of bytes 0x80..0xff doesn’t matter. All that matters is that those bytes are preserved unchanged by whatever operations are done. Typical operations like tokenizing strings, looking for markers indicating particular types of data, etc. only need to care about the meaning of bytes in the range 0x00..0x7f; bytes in the range 0x80..0xff are just along for the ride.

So the trick for beating Python 3 strings into submission is to put in encoding and decoding calls where you need to, choosing a single-byte encoding that doesn’t mutate 0x80..0xff. There are many of these; most of the Latin-{1..6} sequence (aka ISO-8859-1..10) is has this property. What you do not want to do is pick utf-8 or any of the multibyte Asian encodings. Latin-1 will do fine; in fact it has an advantage over the others in memory consumption, which we’ll describe below.

Whether depending on this is actually correct or not is beyond me, but it seems like people have actually been using that pass-through behavior in practice and put it into things like Python2 -> 3 migration guides.

The first link suggests that the seemingly undefined ranges are valid as C0 and C1 control codes which may be why it doesn't throw errors.

To clarify, the word OP brought up is "aiseki".

(Takoboto is a dictionary site.)