• 8 Posts
  • 28 Comments
Joined 3 years ago
cake
Cake day: July 18th, 2023

help-circle




  • 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.


  • 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”


  • 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.

















  • If you are looking to do something like Github’s Personal Access Tokens (PAT) then it is easiest to just think about it like a password:

    • Create a high entropy (secure) string
    • Store the hash of the string in a database table
    • Store the permissions and other metadata with the PAT’s hash
    • Validate the PAT (permissions, revoke status, etc) on each request to the server

    Storing the hash of the token, like you do with passwords, is a good practice in case your db is ever compromised as it wont leave the tokens accessible and reusable without a lot of effort.


  • Yeah, unfortunately that stuff is almost impossible to estimate. Inform your client that fixing the build will be a game of whack-a-mole where you’ll fix one thing and 5 new errors will show up. I would give yourself lots of time since you’ve never worked on Maui (? You didn’t say that in your post but if you’ve never heard of xamarin, i’ll assume maui is new).

    I would break your work down into two milestones: a) compile and run, b) fix all the busted views. It should come to no surprise that a) will be hard to estimate so give yourself lots of time, and b) will be easier to estimate because you’ll be able to review each View and determine what kind of fixes you need to make.

    Good luck


  • Yes. The transition from Xamarin to Maui has been similar to transition from .net framework to .net core.

    A few things you will run into:

    • namespaces have changed
    • certain things will be deprecated but still currently work (ie FillAndExpand)
    • platform specific setup has changed (you’ll need to convert to the new way, but code will likely remain the same)
    • upgrade your nuget packages to the Maui equivalents (the ones we used had Maui versions so we didn’t have to change any of them)
    • certain ways of doing things have change slightly, like how to run things on the main UI thread (you’ll see warnings)
    • your xaml code will remain mostly unchanged but your layout may need to be fixed (especially if your dependencies changed their interfaces)

    That’s all I can think of right now. There’s no easy way to do it and it’s going to suck. Focus on getting it to build with all your dependencies upgraded and then go from there.


  • Kind of a nothing burger.

    These repositories, belonging to more than 16,000 organizations, were originally posted to GitHub as public, but were later set to private, often after the developers responsible realized they contained authentication credentials allowing unauthorized access or other types of confidential data. Even months later, however, the private pages remain available in their entirety through Copilot.

    The repo was listed as public and archived. It’s not clear from the article but I suspect that the “private” information is just a copy of what was made public and not the information added after it was made private.