Epicurean Revolutionary Libertarian Socialist

I make FOSS things:

wiki-user: db0

  • 13 posts
  • 0 comments
Joined 3 years ago
Cake day: June 9th, 2023

Cross-posted from “FYI: StarTrek.website is no longer federating with Lemmy.dbzer0.com” by @Admin@startrek.website in !quarks@startrek.website

Crossposting here since y’all won’t be able to see it now that they’ve defederated us.


If you’re not familiar with how Lemmy/the Fediverse works, basically everything you read at StarTrek.website is hosted by us, even if the content originated elsewhere. That means we are responsible for everything here and we have to decide if we are comfortable boosting content from other instances.

If you’re curious, the final straw here was learning that db0 explicitly allows hosting discussions about hurting people, which needless to say goes against our instance values and we simply don’t have the manpower to moderate that volume of content incoming from their server to a degree that we feel meets our quality standards, which left defederating as the only viable option.

In keeping in line with past trends we’re announcing this because is is a larger instance and don’t want to leave any of the crew confused as to why something may be missing.


I don’t consider this a massive loss tbh. We already have !Risa@lemmy.dbzer0.com and !tenforward@lemmy.world was already more active than their whole instance. And I’m sure @Stamets@lemmy.dbzer0.com can provide the noxious lore of their instance if you’re interested. The only loss would be not having members such as @Kirk@startrek.website running around running interference for DDoSers like @ptz@dubvee.org. Also Admiral Patrick of the Tesseract fame, was also an admin on their instance iirc so this is a clear retaliation as far as I’m concerned, even though we didn’t actually do anything to AP.

But also

db0 explicitly allows hosting discussions about hurting people

What the fuck does this even mean? Can someone ask for an example? Is this about Luigi? IDFK…

PS: Will this drama season never end? I want my free time back >_<

I discovered this after upgrading our instance yesterday, which also upgraded all frontends to their latest versions as well. After I did, our Tesseract frontend stopped working and I noticed immediately as it’s been my primary for a while. Initially I thought it was an API version mismatch, but no, it was much worse.

Someone pointed out that the developer of the frontend added an explicit hidden and unmodifiably blacklist which includes any and all instances to the left of Kissinger. There’s a commit which also explains their specious reasoning about our instance specifically, as it seems we’ve been on their shit list for a bit longer than that.

This instance and its admin staff encourages identity politics, groupthink, mob mentality, and extremist solutions to societal problems. Users who advocate violence are not moderated so long as the admins agree with the target. Caution and critical thinking are advised when interacting with this instance or its users.

When you use tesseract to connect to one blacklisted such instance , you just get a message informing you that Tesseract is “incompatible with that instance” which leads one to think of a technical issue, like an API mismatch, rather than the dev being an opinionated coward.

Isn’t it funny how all the software developed by turbolibs, like Piefed and Tesseract, end up with hidden control mechanisms from developers who think they know better than everyone else? That they don’t just think they deserve to tell you what you should think, but they should manipulate you to think it? Isn’t it funny how libs go on about how bad it is to support lemmy due to the ideology of the devs behind it, and yet lemmy has 0 opinions as a software? It does make one think…

Anyway, I forked - it as one does - and disabled the blacklist, but since this is a massively ideologically compromised software, I’ll doubt I’ll keep this frontend up after Lemmy 1.0. I think we’ll bring up mlmym again now that someone’s maintaining it again.

The new release of Threativore adds Fediseer integration. It will allow you to keep your instance blocklist in sync with your fediseer censures. Not only that but the integration can be as fine-grained as you want, supporting collating multiple instance censures, filtering only censures with tags you want, or only censures collaborated by 1+ other instances etc.

Check out the usage manual for all the variables allowed.

For people who only want some basic protection, the default settings will by default protect you from all CSAM and bigoted instances as tagged by lemmy.dbzer0.com, lemmy.world and lemmings.world. This should provide a good initial blocklist even if you don’t populate fediseer yourself Bbut you can of course mix&match according to your needs.

This integration also prevents too many changes happening at one go in your blocklist. If threativore detects too many changes about to happen, it will ask for admin approval via DM before proceeding.

This sync will run every 10 minutes, so if you’re following the censures of other instances and they discover a new bad actor, you’ll be almost immediately protected, thus converting a fediverse weakness (information distribution) into a strength (information collaboration).

Let me know if you wish to see any improvements.

The newest release of Threativore allows admins to flag users with warning flags, which don’t lead to any immediate consequences, but they allow admins to keep track of potentially problematic users and also a way to send a warning to those users that doesn’t come from any specific admin account.

This was triggered by having a few problem users in our instance which had bad takes low-key enough to not cop an immediate ban but kept popping up in reports and moderation. In isolation any of those things might make an admin give the benefit of a doubt, but when seen holistically, it makes things more obvious.

Currently it only supports a warning flag, but I can easily add more if people have ideas. These flags can accumulate between admins and you can always see what others have added.

I’m hoping people can use this functionality more liberally than bans, as it will provide a warning to users for bad behaviour, and once someone gets more than 2 or 3 it would be a good chance to take more significant actions.

Flags can also be set silently (i.e. without informing the user) and also with an expiration date, if wished.

Hey peeps, I got a few things to talk about.

First of all I am happy to announce that the Divisions by zero will be joining the newly minted Haidra non-profit org. The plan is to use Haidra as the fiscal host for your donations to the instance and have things a bit more organized in the backend. Haidra is our own non-profit, so it should carry our values and avoid conflict with people who don’t understand our ethos.

With the non-profit in place, I wanted to put into action a plan I had for a long time. To implement some sort of radical instance democracy. I don’t believe in Benevolent Dictators for Life and thus I always look for ways to receive a mandate for my actions all stakeholders, rather then deciding top-down. Unfortunately the nature of hosting a service like this does not allow anarchist democracy to be practised, as at the end of the day, there’s a sysadmin with the passwords holding all the power, but given that for this specific instance, that sysadmin is myself, I want to try and experiment with this.

As part of Haidra, the project itself (i.e. the divisions by zero) maintains full autonomy, so its own decision-making remains in its own community. However as a member project, it also effectively gets a vote in the internal running of Haidra. For me use your mandate, I need to figure out a way to receive it. To this end, I want to try and implement some sort of system to allow such democratic decision making.

Unfortunately we cannot reasonably allow every registered member to vote on instance policies, as it’s trivial for any bigot to join and make sockpuppets and throwaway accounts to affect our policies.

So I want the voting process to be somehow run by the instance stakeholders, so I came up with the concept that the only people who should be able to take decisions on the instance, are those who have monetary contributed to the hosting and personnel costs, or who are putting significant effort into nurturing communities here and potentially in the larger fediverse. The idea is that if you’ve put into action your support of this instance, you should deserve some say on how it’s run. That said, while I’m still doing most of the work behind the scenes, I still need to feel good running this instance, so I will need to come up with ways to reject people from the voting process if they don’t match our ethos. I won’t in good faith allow bigots to vote, just because they have money.

Now the trick is how to do this in a way that is manageable. While I have access to the accounts subscribed on Ko-Fi and Liberapay, connecting them to accounts in here is a massive PITA. Likewise it’s not easy to easily remember who is contributing in direct action to this instance.

So once more the mad science lab that is my brain, has come up with some new ideas. First I have updated the threativore bot so that it now also provides a REST API on top of its bot functionalities. The REST API can now be used to retrieve extra user info that is maintained by the instance admins about users on our instance, that is not always relevant to the software (and as such is unlikely to be added to the API by the devs).

One big aspect of this update is that I can maintain user tags inside threativore. These tags are free-form and will allow us to mark users as contributors through ko-fi or other means. In fact, I even setup a complete backend DB connection to threativore and a webhook for ko-fi, so that as soon as you donate to the instance, you will be marked on threativore as a contributor, so long as you used the same email address on both (if you didn’t, and you want to be recognized, please send me the email you used on ko-fi in a PM and we can override)

However, because I can’t just do things only a little bit, I decided to extend the tags functionality to also have a key for “flair”. Each tag assigned to a user has an optional flair key, which can be an emoji, or a link to an image. Currently those flairs don’t serve any purpose, but I have already pinged some of the popular third party UIs (which we’re currently hosting and I wholeheartedly suggest you use), to assist us in making those flairs visible.

In fact, those flairs are not even restricted only to our own instance, we can potentially flair any user from any instance and I have a lot of plans to make expand this functionality. The only limitation is finding UI developers to handle that end.

In fact, I have already created and onboarded some starting flairs for our instance. Some of them will be automatically assigned by the ko-fi webhook, and some others will be automatically assigned by the way you answered your registration application. Here they are:

Ko-Fi

These 4 are coming from Ko-Fi subscribers. The idea is to use them to flair people so I can quickly see whose votes would count in the democratic process. Initial plan is that every subscriber should be allowed to vote, but only subscribers who fund a lot can open new votes for mandates.

  • An icon of tankart of grog in orange-red, black and white colors: Drinking Mate is the tag for people who have donated in Ko-Fi, once off. The tag will expire after 2 months.
  • An icon of a doubloon with a black hole in the center in orange-red, black and white colors: Threadiverse Enjoyer: The people at the lowest end of the ko-fi support.
  • An icon of anchor crossed with two staves in orange-red, black and white colors: Deck Hand: The people who support significantly through the year (as it stands, each of them effectively covers half a month of hosting per year)
  • An icon of two crossed cutlasses with a skull in the center in orange-red, black and white colors: Salty Dog: The people who massively support each month (each of them effectively covers ~1/5th the monthly cost)

Liberapay

  • An icon of a doubloon with a black hole in the center in orange-red, black and white colors: Threadiverse Enjoyer: Same as Ko-FI
  • An icon of powder barrel in orange-red, black and white colors Powder Monkey: The people who support significantly through the year
  • An icon of  two crossed belaying pins and a hourglass in the center, in orange-red, black and white colors: Buccaneer: The people who massively support each month

Affiliations

The below flairs are going to be assigned depending on how you answered the registration application. If you mentioned more than affiliation, you will be assigned all of them matching.

  • A book with a loaf of bread in the cover  in orange-red, black and white colors: The bread book: Will be assigned if you mentioned an anarchist.
  • an icon of pirate jolly roger skull wearing a hat, in orange-red, black and white colors: Jolly Roger: Will be assigned if you mentioned a pirate
  • an icon of a wildebeest, in orange-red, black and white colors: Wildebeest: Will be assigned if you mentioned a FOSS advocate/software.
  • Early Bird: a parrot, orangered colors: Early Bird. Will be assigned if you registered before our instance had an registration application process, so only around 5K users ever got this one.
  • ADHD: A lightning butterfly in orangered color: ADHD Assigned if you specified you have ADHD
  • ASD: The ininity symbol in an orangered/white color: ASD Assigned if you specified you have ASD
  • Snowflake: a snowflake in orangered color: Snowflake is assigned if you mentioned someone who is neither an Anarchist, Pirate, nor FOSS (advocate)
  • First: a victory cup, orangered color: First is assigned if you were the first to mention that particular Anarchist, Pirate, nor FOSS (advocate)

Other

  • a minimalist compass icon. Orangered color Vouched: This signifies a user for whom a trusted user of this instance has vouched for. This is another way to be able to take part in the decision-making of this instance. Vouching will be restricted to tiers higher than An icon of a doubloon with a black hole in the center in orange-red, black and white colors threadiverse enjoyer and a star icon, in orange-red, black and white colors MVPs.
  • a star icon, in orange-red, black and white colors MVP: Is a flair which I plan to assign to signicant contributors to the instance in some way. Perhaps lifetime funding and/or fediverse presence? Perhaps we should vote on it :D

All of this is only the beginning of what I want to do here, but this beginning will be short-lived if we can’t get UI developers on board. So if you’re maintaining one of the 3rd party UIs in the sidebar, please contact me. Likewise, if you’re excited by any of this and you can help hack the exising lemmy UIs (including the default one) for our instance purposes, please speak up and that would be a good ground for an MVP a star icon, in orange-red, black and white colors flair! :)

In the meantime I will use threativore to start doing some scripting to allow only-staholder voting, and we’ll try it out soon.

If you have ideas and improvements about all this please post. If you have ideas for more flairs and way reasons to get them, let me know. If you have thoughts about how this democratic experiment should be structured, now is a good time to write them!

With threativore 0.8.x I have finally released a feature I’ve been planning for a while, the ability to maintain and view it via REST API.

The first thing that is released in the REST API is the ability to see a user’s information, which at the moment contains the user’s profile ID, their threativore roles and the newest fields, which is tags for users

{
  "user_url": "https://lemmy.dbzer0.com/u/db0",
  "roles": [
    "UserRoleTypes.MODERATOR",
    "UserRoleTypes.ADMIN"
  ],
  "tags": [
    {
      "tag": "ko-fi_tier",
      "value": "deck hand",
      "flair": "https://lemmy.dbzer0.com/pictrs/image/0cc8915a-acf8-451b-8350-c889f469ac42.webp",
      "expires": "2025-03-15 13:18:46.305405",
      "description": "This user is donating a moderate amount to their instance through Ko-Fi"
    },
    {
      "tag": "pirate",
      "value": "true",
      "flair": "https://lemmy.dbzer0.com/pictrs/image/156d1970-0600-4bea-b3d2-53435be3c314.webp",
      "expires": null,
      "description": "This user likes pirates"
    },
    {
      "tag": "anarchist",
      "value": "true",
      "flair": "https://lemmy.dbzer0.com/pictrs/image/61a552e5-d1db-43a5-a120-f584e3082c2d.webp",
      "expires": null,
      "description": "This user likes anarchism"
    },
    {
      "tag": "foss",
      "value": "true",
      "flair": "https://lemmy.dbzer0.com/pictrs/image/00ac9132-cecd-41e6-ba81-8ffd51043bdd.webp",
      "expires": "2025-01-14 13:07:57.467910",
      "description": "This user likes free software"
    },
    {
      "tag": "liberapay_tier",
      "value": "powder monkey",
      "flair": null,
      "expires": "2025-03-16 20:05:57.525031",
      "description": "This user is donating a moderate amount to their instance through Liberapay"
    }
  ]
}

The tags are free-form and any threativore admin can assign any tags to any users with whatever values. For example one of my plan in lemmy.dbzer0.com is to add a boolean tag for pirate if the user mentioned a pirate in their application form, or alternatively anarchist or FOSS respectively. Likewise I have automated adding tags based on whether someone has donated to the site through ko-fi recently and at which tier.

Currently these tags don’t have any effect, but I want to bring together the various frontend developers, such as @ptz@dubvee.org from tesseract, @sheodox@lemmy.world from alexandrite, @aeharding@vger.social and so on to see if we can come up with a standard where we can specify within threativore how the tags could be utilized. Or perhaps agree for a standard location where the threativore can always be sought by UIs to retrieve info (as it’s not part of the lemmy API proper)

For example I can arrange for a new field per tag, which would contain an emoji code, or an image url, which would be displayed by the UI as flavor for that user. I want to provide ways for each instance to be more unique, (until and if lemmy itself adds such functionality in the backend).

Another functionality which is not immediately obvious is that I now added code to allow threativore to reach in directly to the lemmy DB and extract any data needed. This is for example how lemmy.dbzer0.com can match users on ko-fi with users in lemmy. I plan to extend this functionality in the future to hopefully provide more ways for threativore to detect and deal threats, even without info publicly available in the API.

With all this I want to make threativore a valuable companion software to lemmy, to provide a lot more extensibility through the UIs and empower instance admins to do even more for the looks and security of their instances.

If you want to deploy threativore, I provide a simply code chunk you can add to your lemmy UI in docker-compose. You can even disable the anti-spam capabilities if you want (although they don’t do anything until you populate them), and just keep it as an API only.

Let me know what you think.

You know that little information thing below posts telling you which other communities a specific post has been posted to?

That one, won’t appear if you crosspost a pure-text post. Sure you’ll get a link in the body, but lemmy won’t “intuitively” know the two posts are connected.

By using an image in the URL of the post, not only do you give your text post a thumbnail, but you allow lemmy to easier link them together when cross-posting.

If you’re wondering “But where the hell do I find an image for each post”, well, Generative AI to the rescue! I always just fire up Lucid Creations and use it to generate something fitting to the subject, or just something pretty at 768x512.

cross-posted from: https://lemmy.world/post/276633

Been using this one for over a decade. Works with Firefox’s bookmark keywords feature.

Make a new bookmark, set the link as follows:

https://lemmy.world/c/%s (or your own Lemmy instance)

And in the “Keyword” field, use “c” or “lemmy” or whatever.

Now, when you want to visit a specific Lemmy community on your home instance, you can simply type:

“c community_name” in the address bar, or “lemmy community_name” in Firefox and it will automatically open the community.

Hey y’all I wanted to make something clear. While the lemmy.dbzer0.com allows anyone to create community because I feel there’s a lot of creativity to be found by giving people this freedom, I also don’t want a sea of flotsam in our communities list.

So while I’m not going to shut down community creation, I am planning to start curating the available communities a bit more from now on.

What it means for you is that if you plan to create a community, I expect you to actually have a plan to grow it. Not just register the name so that you squat on it and hope other join so that you end up the top mod other users built-up.

Practically this means that we expect to see some activity on those communities, a sidebar that explains what it’s about, reasonable names and titles etc. Please also do the effort of adding a banner and an Icon. I’ve developed a free Generative AI art tool you can use even!

Communities which we perceive to be abandoned or squatting will be summarily purged. My plan for now is to purge empty communities within 1 week after giving a warning. I haven’t decided how to deal with communities which have posts and subscribers yet, but if it’s inactive long enough and the amount of posts is trivially small, I’ll probably start purging those within a month. I do not think I’ll purge communities with significant amount of posts and subscribers however.

I also plan to post a report about purged communities when we do so, so that people are aware.

Thanks for reading. Let’s try to keep the quality of the divisions by zero sufficiently high.

EDIT/UPDATE: Recent versions of lemmy make this even easier by allowing turning the !instance format into a relative link to your instance. For example !div0@lemmy.dbzer0.com. However when you do this, don’t use the auto-fill option which turns it into a markdown link, as that will break this functionality.

When you link to another community on lemmy with a absolute link like so Div/0 this links to that community directly from that instance’s domain. This means users who follow that link from other instances, will not be able to comment or subscribe. They will have to go back and edit their URL manually to workaround this.

If you instead link to a community using a relative link like so Div/0 it will lead them to the community using their own instance as a mediator, allowing them to interact with it naturally.

The source for the above relative link is like this [Div/0](/c/div0@lemmy.dbzer0.com). So basically just add only the /c/... part and ensure your instance’s domain is at the end

Quick post to answer some basic usage questions that can throw off new users.

Where should I register?

The age old question of fediverse. The answer is pick an instance that is not right-wing and you should be fine.

https://join-lemmy.org/instances makes this very easy. Once you find an instance, just go to its /signup endpoint. For the instance you’re reading right now, it would be: https://lemmy.dbzer0.com/signup. Another great option is to use the lemmyverse which provides a lot more info about potential instances and communities, including a trust score.

Do I need to create a profile for each instance?

No! Each instance can access each other instance, unless it’s been defederated because its admins are toxic (this is why I told you not to join right-wing instances earlier).

I joined an instance, but the community I am interested in is in a different instance

No problem. Simply add the instance domain at the end of the url endpoint.

For example, say you’re in lemmy.ml and you realized that stable_diffusion is in lemmy.dbzer0.com. To access it, simply add @lemmy.dbzer0.com at the end of the url after the community name. So:

https://lemmy.ml/c/stable_diffusion@lemmy.dbzer0.com

Or to put it differently, you can access any community, in any instance by adding /c/ (The requivalet of reddit /r/) and then community_name@instance.domain

If this doesn’t work, then it’s likely this instance is not yet federated with yours. To solve this, you need to search for it. See the next section.

But how do I even find the community I want to if it exists in any of hundreds of instances?

One option is to use the lemmyverse, as it’s very user friendly, if you specify which instance if your home, it will automatically convert all links to your own instance.

Alternatively use the use the built-in search.

Note that if you search for an community in an lemmy instance your own instance doesn’t yet know about, it won’t find it. You need to give it more precice instructions to find it, which require the whole “address”. To follow our example above, you would put !stable_diffusion@lemmy.dbzer0.com in your search field.

When searching for a community in a new instance, it might take a few minutes to take effect. The first search will not return anything, but if you search again after a couple of minutes, it should appear.

How do I find my community from reddit?

https://sub.rehab/ allows you to search for any subreddit and see if its official community exists in the threadiverse. You can then search for it specifically to subscribe. If you’ve already registered an account somewhere, make sure you visit the settings in sub.rehab and set your home instance there, so that all links go through it.

Community? Instance?

An instance is a lemmy server hosted by someone. it has its own set of users and communities. lemmy.dbzer0.com is an instance. You can access (almost) every instance from any other instance.

a community is like a subreddit in reddit, or a channel in discord. It’s a topic in inside an instance. stable_diffusion is a community inside the instance lemmy.dbzer0.com.

In more plain terms, consider a lemmy instance like a street, and a community like a number on that street. When you write !stable_diffusion@lemmy.dbzer0.com you are giving the exact address and number to search for.

I keep seeing the same posts

In you’re in a smaller instance and you’ve subscribed to communities in other places, you might have set up your default visibility to not show them.

Switch your view to Subscribed/Hot to get a similar view like the reddit frontpage.

Switch to All/Hot to get a similar view to reddit /r/all

You can store this setting permanently as default in your user settings

Tips and PSA

Also see