SavvyWolf

joined 2 years ago
sorted by: new top controversial old
2
[Vote] Use the Fediverse Overseer to pre-emptively defederate from suspected botted instances (sh.itjust.works)
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]
7 comments fedilink
 

See the tool here: https://lemmy.dbzer0.com/post/95652

And some discussion of the issue here: https://lemm.ee/post/177673

This tool produces a list of instances which have a very high number of users compared to the number of comments and posts. These instances are assumed to have high number of bot accounts on them.

Some other instances have started blocking them, should sh.itjust.works follow suit?

Of course, this need not be permanent, and will be reversed when those instances resolve the issue.

For reference, this is a list of instances suspected of being botted by the tool's default settings: https://overseer.dbzer0.com/api/v1/instances?activity_suspicion=20&domains=true

Ayes and nays please!

I need 1 more thing an evil necromancer dictator would have in his garden in c/[email protected]
[–] [email protected] 2 points 2 years ago

A flower garden.

Not like, evil or anything. Guy just really likes gardening.

3
[Vote] Require a valid non-temporary email on signup (sh.itjust.works)
 

Registrations should require a valid email address and temporary/disposable (e.g. temp-mail.org ) email services should be rejected.

Note this should not be implemented as a whitelist; "obscure" email services such as Protonmail, Tutanota and personal email servers should be allowed.

Pros:

  • Cuts down on the number of trolls attempting to register, reducing load on mods and admins.
  • Improves our standing with other instances.
  • Ensures users have the ability to reset their password.

Cons:

  • Has privacy concerns - people may not want to associate their email address with everything.
  • Users may not (and perhaps should not have to) trust the admins of this instance with their email.
  • May not be supported well by Lemmy, and/or require a blacklist that needs updating.

Aye and nay in the comments, please.

Whats the latest personal project youre working on? in c/[email protected]
[–] [email protected] 1 points 2 years ago

I've been perpetually working on various gamedev projects for many years now. I'll finish one eventually, I promise!

Most recent one is a retro style JRPG. With a flexable skill system where each character has two classes and can pick some number of skills from them. Also has a number of equippable "quick time" events a-la Mario RPGs. Using ggez for it, which is a decent engine. Although for future projects I may pick something more feature complete like bevy.

Currently thinking about starting a new project to make a Sonic-like game, because if Sega isn't going to do it, I may as well give it a go. :P

Beehaw defederating update - sh.itjust.works in c/[email protected]
[–] [email protected] -1 points 2 years ago

Just a quick idea I had, and this may have been suggested before and maybe be untenable. But... Could communities be made invite/approval only as well as instances?

For example, on beehaw they want to ensure that everyone posting to their communities have been vetted in some way. So could have all the communities not allow posts by who haven't agreed to beehaw's "content policy"? Either by naturally having an account on beehaw, or by submitting a request to a moderator of the community.

Would allow people on other instances to see and follow those posts (but not post themselves, unless they go through beehaw's approval process), and beehaw people to go and interact with other communities on other instances.