meta product

no thanks

7m - 4m = 3m

“Give it six months”

It only needed 3!

Sure, not disagreeing. Its a shame its barely enforced

Mostly - it gets messy with content being posted though. They absolutely should be deleting all personal information about you.

I am however unsure how this applies to posts and comments which don’t contain personal information.

Deleting posts is basically pointless - reddit keeps everything you delete, it just is no longer shown to front end, regular users.

If you are concerned of your posts and comments being used to feed openai, its way too late

If this gets support for Signal, or any dumb phone + signal app, id buy immediately

Cant be a good date if you’re checking your work email in the middle of it

The joke is that the guy spent his entire life savings on … this

Great point - I missed that. Plus, in smaller text on one image it does say “The USB-C port does not support screen monitoring.“

Seems like a great price for a KVM. Last I looked (granted, circa covid era), KVMs were multiple 100s

edit i mention how this is wrong here https://lemmy.world/comment/10366921

matrix is chat for fediverse

Im making no estimation one way or the other

Thats what adding strong typing does for you

here’s a good question answer on this topic

https://stackoverflow.com/questions/18922407/boolean-and-type-checking-in-python-vs-numpy

plus this is kinda the tools doing their jobs.

bool_ exists for whatever reason. its not a bool but functionally equivalent.

the static type checker mpy, correctly, states bool_ and bool aren’t compatible. in the same way other type different types aren’t compatible

Well, yes exactly

1. Create fixes
2. Request merge. assume denied
3. Fork numpy and add your changes there
4. after just continue to pull new changes over from source of the fork and deal with any merge issues with the fix

This explanation is pretty clear cut

What exactly is your use case for treating np.bool_ and bool as interchangeable? If np.bool_ isn’t a subclass of bool according to Python itself, then allowing one to be used where the other is expected just seems like it would prevent mypy from noticing bugs that might arise from code that expects a bool but gets an np.bool_ (or vice versa), and can only handle one of those correctly.

mpy and numpy are opensource. You could always implement the fix you need yourself ?

“all the clones are the same except my clone”

Nice, congratulations for completing a personal project. One day I also hope to complete a personal project.

What reference material did you use to build it? As in like the activitypub specification

I don’t think its mysql specifically, but for some reason the worst systems I have used, all have mysql/mariadb as a database.

It seems shitty applications gravitate to mysql, use it poorly, then bring a bad name to mysql.

But given all my years of experience with it, MSSQL > Posgresql > Mysql > Oracle