InfoSec Person | Alt-Account#2

  • 3 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: September 28th, 2023

help-circle



  • My bachelor’s thesis was about comment amplifying/deamplifying on reddit using Graph Neural Networks (PyTorch-Geometric).

    Essentially: there used to be commenters who would constantly agree / disagree with a particular sentiment, and these would be used to amplify / deamplify opinions, respectively. Using a set of metrics [1], I fed it into a Graph Neural Network (GNN) and it produced reasonably well results back in the day. Since Pytorch-Geomteric has been out, there’s been numerous advancements to GNN research as a whole, and I suspect it would be significantly more developed now.

    Since upvotes are known to the instance administrator (for brevity, not getting into the fediverse aspect of this), and since their email addresses are known too, I believe that these two pieces of information can be accounted for in order to detect patterns. This would lead to much better results.

    In the beginning, such a solution needs to look for patterns first and these patterns need to be flagged as true (bots) or false (users) by the instance administrator - maybe 200 manual flaggings. Afterwards, the GNN could possibly decide to act based on confidence of previous pattern matching.

    This may be an interesting bachelor’s / master’s thesis (or a side project in general) for anyone looking for one. Of course, there’s a lot of nuances I’ve missed. Plus, I haven’t kept up with GNNs in a very long time, so that should be accounted for too.

    Edit: perhaps IP addresses could be used too? That’s one way reddit would detect vote manipulation.

    [1] account age, comment time, comment time difference with parent comment, sentiment agreement/disgareement with parent commenters, number of child comments after an hour, post karma, comment karma, number of comments, number of subreddits participated in, number of posts, and more I can’t remember.





  • I think the difference lies in two things:

    • You can share an article from a user of a different instance. In this case, your instance will have to look up the rel=“author” tag and check whether the URL is a fediverse instance. I’m not sure whether this is scalable as compared to a tag that directly indicates that the author is on the fediverse. Imagining a scenario where there are 100, 1000, 10,000, or 100,000 instances on different versions.

    • The tag is to promote that the author is on the fediverse. If the rel=“author” tag points to twitter for example, maybe Eugen Rochko + team didn’t want a post on the fediverse to link to twitter.

    These are my thoughts and idk if they’re valid. But I think just reusing the rel=“author” isn’t the most elegant solution.

    I know that mastodon already uses rel=“me” for link verification (I use it on mu website + my mastodon account), but that’s a different purpose - that’s more for verification. There’s still no way of guaranteeing that the rel=“author” tag points to a fediverse account. You’re putting the onus on the mastodon instance.





  • Excellent question!

    Before replacing the instruction with INT 3, the debugger keeps a note of what instruction was at that point in the code. When the CPU encounters INT 3, it hands control to the debugger.

    When the debugging operations are done, the debugger replaces the INT 3 with the original instruction and makes the instruction pointer go back one step, thereby ensuring that the original instruction is executed.







  • That’s not a very valid argument.

    First and foremost, most devs probably see it as a job and they do what they’re told. They don’t have the power to refute decisions coming from above.

    Second, in this economy where jobs are scarer than a needle in multiple haystacks, people are desperate to get a job.

    Third, yes, there may be some Microsoft (M$) fan-people who end up being devs at M$. Sure, they may willingly implement the things upper management may request. However, I’m not sure whether that’s true for most of the people who work at M$.

    Your comment suggests to shift the blame to the devs who implement the features that upper management request for. Don’t shoot the (MSN) messenger.


  • Looks cool and I’m glad something new has arrived after nitter.

    A few things, however:

    1. It doesn’t look like I can view comments on tweets; I can only view the tweet. (Firefox mobile if that matters)
    2. It’s pretty slow. It’s not a big problem, but it is very noticeable.
    3. Somewhat irrelevant, but why is it called TWStalker? It’s a… bit of a weird name. ‘Stalker’ makes me feel like I’m doing something illegal even though I definitely am not.


  • A Basil Plant@lemmy.worldtoTechnology@lemmy.world*deleted by creator*
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    9 months ago

    Will you (the community) be setting your username to your public username (a username you use everywhere) or something that’s different from your public username?

    Idk why, but signal feels more… personal(?) and I’d hate for general people to stumble across my signal account just by guessing whether my signal username is my public username.

    I’d be fine if they got my Discord account, mastodon account, Lemmy account (they’re all different usernames anyway) because they’re public-ish accounts. Signal feels less public and I’d want to go with a username that only I can send to people I know.

    It looks like there will be a message requests area and it looks like usernames can also be changed (should a username ever be doxxed).

    I’m still on the fence.