• 0 Posts
  • 18 Comments
Joined 3 years ago
Cake day: July 18th, 2023
  • mrbn@lemmy.catoProgramming@programming.dev•Might this be a scam?
    12·
    4 days ago

    Yes, this is 100% a scam or rather, fraud (and may be illegal where you live).

    He explains the con right in the follow-up email.

    The reason for this proposal is that I had been working with several US collaborators on regular US software engineering roles using their profiles due to the high rate. After securing the positions, the work is subcontracted to me.

    Let’s break this down.

    He gets people who would have nice resumes (or profiles,… like a young fella fresh outta college) to apply for tech jobs. He’s looking specifically for US tech jobs because of the “high rate” in which he means the jobs pay a high hourly rate/wage.

    Once the company hires you, you subcontract (aka pay him) to do the work. Of course he’s probably going to say something like, well you keep 20% of the “high rate” for yourself.

    The following is only speculation

    Since he’s asking you about interviews and team meetings, I have a feeling he’s not getting a lot of success recruiting “collaborators” in the US and likely thinks getting someone already in the US to recruit other will be easier (no language barrier, no international issue, etc). Having an American front man for this scam is likely going to make recruitment easier.

  • mrbn@lemmy.catoLinux@lemmy.ml•My Accessibility Stack and the future on Wayland
    1·
    4 days ago

    I don’t know how you add a call to an API that doesn’t exist

    As far as I know, these messages are passed to the portal using dbus. So the app could just fire the correct dbus message with correct parameters (you can find the correct values in the Wayland specs). The portal, used by the compositor, then takes the message and runs the requested action or returns something like not implemented or unknown method.

    The trickier part is testing when no portal supports the API calls.

    But yeah, interoperability between systems can be a pain in the ass.

    The process is analogous to sending an http request. Your app sets up the httpclient and points it to a URI and after sending the request you get back either the content with 200 status or 404. If you get 404 you can show the user a message like “this website doesnt support feature xyz”

  • mrbn@lemmy.catoLinux@lemmy.ml•My Accessibility Stack and the future on Wayland
    7·
    5 days ago

    not a single one of those compositors implement the entire API surface you need.

    Aegis has requested that those of us who wish to not see Talon on Linux die out do the following:

    • Do not, for any reason, discuss Wayland support with him;
    • As a community, gather together, and successfully implement the entire API surface needed for Talon on GNOME, KDE, and wlroots,

    At which point a new Wayland backend will be considered for Talon.

    I agree that it’s not up to Talon to implement the missing APIs in the compositors. However, I think the dev is doing a disservice to the users of Talon by not adding wayland support (ie making the calls to the APIs Talon needs to function). If Talon used those wayland protocols, users could point to the software and say it’s “not working on compositor because the compositor is missing wayland protocols”.

    IMO its a much easier sell to the compositor people when they know a useful piece of software is actively trying to target those APIs.

    That being said, I sure hope the situation improves. The state of accessibility on wayland is pitiful.