PennyJim

joined 1 year ago
[–] [email protected] 1 points 2 weeks ago (2 children)

I somewhat recently got my current phone, so I'm not yet willing to buy another, but I'll keep that in mind. As well as Obtainium, as that sounds better than the fdroid app I have right now.

Sounds like I'll be missing out on the most private ROM though :(

(Also what's HTH?)

[–] [email protected] 2 points 2 weeks ago (1 children)

Graphene only works on Pixel phones, right?

Does it? I've only heard of it, not done even a lick of research yet.

 

I've only heard of GrapheneOS (and that authy is insecure in the same breath, so I need better 2fa apps).

The biggest thing I can think of that I don't want to lose is the Motorola gestures. I constantly chop to open my flashlight and twist to open my camera.

Besides that, I have never touched the rom before, and I have both wells Fargo and discover banking apps I use semi-regularly. The banking apps I could probably move to just doing their actions on the website, but that difficulty is something I would like to be aware of going in.

I also use Mihon (successor to Tachiyomi) so problems with that and solutions would be nice.

[–] [email protected] 20 points 4 months ago

Who knows when it'll decide controlled fire isn't enough anymore

[–] [email protected] 1 points 4 months ago

Didn't even upvote it in the screenshot. Have some manners

[–] [email protected] 1 points 4 months ago

I assume they shoot the fuel in with some light particle acceleration. Maybe they just let it diffuse in, but it's a gas so it's not that hard to get it to enter.

The hope is they get the cost of maintaining the electromagnets (power and cooling) to be cheaper than the power we can extract from the reaction.

My question is more about what's the logistics of getting power out? We're making a lot of heat, so it's probably steam power at the heart of it, but a lot of this effort is to keep the heat in is it not?

[–] [email protected] 1 points 5 months ago

Dumb bug report? The inability to do more than one craft per tick?

That was not "curiosity," that was encountering the issue in the dlc and finally fixing it since their excuse was no longer valid.

 

Or at least my attempt at improving it with the limitations of runtime scripting.

I'm posting because I would like some feedback on it.

The current things I still need to do are to listen for more command events so I can reimplement their messages, including fixing the admin promotion one. The current admin promotion message simply responds to the event of someone becoming admin, which doesn't contain info about who promoted them like the localized string expects.

As well as try and make a function that can send a message one tick late, as sending a message in the command event happens before the command is actually handled. Meaning the default error message happens after a custom one.

Finally, I need to implement some graceful way of handling shortcode collisions. I think discord does :shortcode~1: or something. Then I wonder if I should handle the order somehow, or let the modified pairs choose it for me. Though, with the companion mod of Twemoji, it re-registers the shortcode dictionary on the fly so the server can choose which standard to use. I think that might affect ordering, but I'm not actually sure.

I also have a branch that was attempting to do the colors differently, but I worked on that while slightly burned on the project and I don't like dealing with color math (it confuses me).

Sorry for the rambling, this kind of became my Todo list.

 

Or at least my attempt at improving it with the limitations of runtime scripting.

I'm posting because I would like some feedback on it.

The current things I still need to do are to listen for more command events so I can reimplement their messages, including fixing the admin promotion one. The current admin promotion message simply responds to the event of someone becoming admin, which doesn't contain info about who promoted them like the localized string expects.

As well as try and make a function that can send a message one tick late, as sending a message in the command event happens before the command is actually handled. Meaning the default error message happens after a custom one.

Finally, I need to implement some graceful way of handling shortcode collisions. I think discord does :shortcode~1: or something. Then I wonder if I should handle the order somehow, or let the modified pairs choose it for me. Though, with the companion mod of Twemoji, it re-registers the shortcode dictionary on the fly so the server can choose which standard to use. I think that might affect ordering, but I'm not actually sure.

I also have a branch that was attempting to do the colors differently, but I worked on that while slightly burned on the project and I don't like dealing with color math (it confuses me).

Sorry for the rambling, this kind of became my Todo list.

 

Or at least my attempt at improving it with the limitations of runtime scripting.

I'm posting because I would like some feedback on it.

The current things I still need to do are to listen for more command events so I can reimplement their messages, including fixing the admin promotion one. The current admin promotion message simply responds to the event of someone becoming admin, which doesn't contain info about who promoted them like the localized string expects.

As well as try and make a function that can send a message one tick late, as sending a message in the command event happens before the command is actually handled. Meaning the default error message happens after a custom one.

Finally, I need to implement some graceful way of handling shortcode collisions. I think discord does :shortcode~1: or something. Then I wonder if I should handle the order somehow, or let the modified pairs choose it for me. Though, with the companion mod of Twemoji, it re-registers the shortcode dictionary on the fly so the server can choose which standard to use. I think that might affect ordering, but I'm not actually sure.

I also have a branch that was attempting to do the colors differently, but I worked on that while slightly burned on the project and I don't like dealing with color math (it confuses me).

Sorry for the rambling, this kind of became my Todo list.

[–] [email protected] 4 points 7 months ago

Look at the M on their chest, I think it's a costume party and the boxing gloves are from a little Mac costume

[–] [email protected] 1 points 8 months ago

I have enjoyed the training diary, but I'm seriously addicted and have tons I'm reading. So the actual quality is both suspect because of how much I read between each chapter and how low my bar for reading is.

It did feel like the recent arc of taming this one monster was a little dragged out, and then I was a little disappointed by the actual result of it.

[–] [email protected] 3 points 10 months ago

Setting CDPATH=:~/Documents/Dev makes navigating to any of my projects so much easier.

Thanks for bringing it to my attention

[–] [email protected] 5 points 10 months ago (9 children)

I've seen a number of comments imply the possibility of case insensitive tab completion. Is this real and how do I do it?

I have multiple times fumbled with forgetting to capitalize something, only for the terminal to 'dunk' at me

[–] [email protected] 3 points 10 months ago

Good God that caught me so off guard

[–] [email protected] 4 points 10 months ago* (last edited 10 months ago)

Wait what? You can export settings? That would've been helpful to know last night

Edit: it's under advanced settings

 

Can you edit whether or not a posted post is nsfw?

I was asking a question to the author of a Lemmy bot api and mentioned I assumed that was or would be the case. He then told me he wasn't sure because the Lemmy documentation isn't that thorough and to post an issue on the Lemmy GitHub.

I just want to make sure that's actually something that isn't implemented yet before I ask for it.

10
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

So here's a post. It'll be deleted shortly.

view more: next ›