Yep, a few forks were identified within a few hours. I think the maintainers had forks too.
ABasilPlant
joined 1 year ago
Do you want to return to that account?
If not, Temp mail works fine.
Also, Bug me not has user-submitted usernames + passwords to services. This works nicely.
I've used Port87 in the past. The user who created it promoted the service on lemmy initially. It worked (I paid for a few months).
~~I suggest using two different spellings:~~
~~Mold is the fungus. To mould is to shape.~~
Nvm I'm an idiot. Lol
That seems to be the consensus online. But thanks for that tidbit! It feels even more bizarre now knowing that.
I wonder why a handful of people think the way I presented in the post. Perhaps American/British influences in certain places? Reading books by british authors and books by american authors at the same time? Feels unlikely.
Yes, this would essentially be a detecting mechanism for local instances. However, a network trained on all available federated data could still yield favorable results. You may just end up not needing IP Addresses and emails. Just upvotes / downvotes across a set of existing comments would even help.
The important point is figuring out all possible data you can extract and feed it to a "ML" black box. The black box can deal with things by itself.
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.
Could you show us the kernel command line parameters (in /etc/default/grub)? Is the modeset along with other params enabled? I'm not a fedora user, so I may not be of too much help.
Season 3 Episode 10: Flu Shot
Felt that this quote from Jack was very relevant in today's world.
Yep! Series 4 hasn't "released" on YouTube yet. I saw Paul William's story on instagram that they're releasing Series 5 on TV, but sadly I don't have access to that. I'm fine being behind by 1-2 years though.
via: @[email protected]
https://wetdry.world/@memes/112717700557038278
the sqlite codebase is a gem.
tldr; mcaffee made a shit ton of sqlite files in the temp folder causing people to call the sqlite devs phone angrily. now they name all files etilqs to prevent this.
Text from the screenshot:
2006-10-31: The default prefix used to be "sqlite_". But then Mcafee started using SQLite in their anti-virus product and it started putting files with the "sqlite" name in the c:/temp folder. This annoyed many windows users. Those users would then do a Google search for "sqlite", find the telephone numbers of the developers and call to wake them up at night and complain. For this reason, the default name prefix is changed to be "sqlite" spelled backwards. So the temp files are still identified, but anybody smart enough to figure out the code is also likely smart enough to know that calling the developer will not help get rid of the file.
Code found at: https://github.com/sqlite/sqlite/blob/master/src/os.h#L65 (The line numbers in the screenshot and the code don't match up)
https://arxiv.org/abs/2404.10002
Abstract (emphasis mine):
The concept of a 'Ballmer Peak' was first proposed in 2007, postulating that there exists a very specific blood alcohol content which confers superhuman programming ability. More generally, there is a commonly held belief among software engineers that coding is easier and more productive after a few drinks. Using the industry standard for assessment of coding ability, we conducted a search for such a peak and more generally investigated the effect of different amounts of alcohol on performance. We conclusively refute the existence of a specific peak with large magnitude, but with p < 0.001 find that there was a significant positive effect to a low amount of alcohol - slightly less than two drinks - on programming ability.
I was in a rush and I needed to pick up a quick snack that I could eat during class. I chose these Nature Valley bars which said they had ten bars inside. What I failed to notice is the tiny print at the bottom where it says 5 x 2, i.e., 5 packets with two bars.
Lo and behold when I open a pack during a break, I find two bars inside. I didn't want to eat two bars, just one. You can't even just leave the other fucking bar inside because they create so MANY crumbs. How the fuck are you supposed to seal it???
Stupid-ass deceptive printing got the better of me. It's not the end of the world, just mildly infuriating.
view more: next ›
o7