refalo

joined 6 months ago
[–] [email protected] 9 points 22 hours ago

you must be fun at parties

[–] [email protected] 4 points 3 days ago

you can't know that

[–] [email protected] 0 points 5 days ago

I think that entire comment is actually incorrect. My understanding is that they did not "remove" any maintainers, but actually rejected patches from Russian citizens (because of their employer), and also removed some Russian names from the maintainers list who already have code in the kernel.

[–] [email protected] 0 points 6 days ago (2 children)

That doesn't invalidate my statement though.

[–] [email protected] 1 points 1 week ago

freedom TO vs freedom FROM

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago)

I was more referring to mainline specifically, otherwise your chances of having many people actually benefit from your changes without a lot of effort is small IMO.

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago) (11 children)

I still don't think something so important should be beholden to the whims of one company (Linux Foundation) or their country's laws (USA).

I would strongly prefer to use an operating system that didn't have this problem. Do any even exist?

[–] [email protected] 4 points 1 week ago (1 children)

go against their spirit

I think this is more of a failure of the license itself. It's not a good look to allow something explicitly and then go "no not like that!"

[–] [email protected] 0 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

For professionals used to Photoshop, yes it is that bad. People want what's familiar because they're used to it and they're busy or lazy. They don't want to learn something new.

If GIMP wanted to increase their userbase by a million overnight, they would make it look more like Photoshop.

The problem is they and many current users are huge FOSS zealots and see this kind of thing akin to selling your soul to the devil.

 

Interpreting C++, executing the source and executable like a script.

  • Writing powerful script using C++ just as easy as Python;
  • Writing hot-loading C++ script code in running process;
  • Based on Unicorn Engine qemu virtual cpu and Clang/LLVM C++ compiler;
  • Integrated internally with Standard C++23 and Boost libraries;
  • To reuse the existing C/C++ library as an icpp module extension is extremely simple.

There is also a Qt helper module: https://github.com/vpand/icpp-qt

 

Tried to use several different API endpoints as described in the link, but they all return 403 with a cloudflare "Just a moment..." html reply. Even tried copying an existing jwt token from a working logged-in browser but the same thing still happens.

Any idea what I could be doing wrong?

curl -v --request POST \
     --url https://programming.dev/api/v3/user/login \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '{"username_or_email": "redacted", "password": "redacted"}'
...
< HTTP/2 403
...
<!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title>
...
23
submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]
 

I am noticing that some comments, which are coming from users on other verified (via /instances) federated instances, do not show up on a post. For example: https://programming.dev/post/13648105

Does not show this comment on it: https://lemmy.ml/comment/10803786

Any ideas why? I checked the modlog and the comment wasn't removed, and their post history to me does not look like someone that is likely to be banned from the instance, so I'm not sure what else it could be.

 

My lemmy account is on the programming.dev instance but I use newsboat for RSS reading of some lemmy.ml communities, along with browsing the local homepage of lemmy.ml and some other instances in a regular browser. Is there a way to do either of these things from the programming.dev instance so that I can easily comment on posts without having to manually locate the same post by browsing to /c/[email protected] on my own instance?

view more: next ›