One note about this after I have used it for a little bit after experimenting is that the vote score text seems like it is a target for tapping to cast a vote. Though, that might just be my fat-fingering things as I am prone to do on mobile. I have also struggled to get the hover text to show up in the past on mobile, so I sympathize with this post.
You can kind of hack this using custom css in your profile. I just tried this and confirmed that it worked, but I couldn't quite get the alignment just right. Basically, the info is there on the element, but it is in the title attribute. So, you have to make the existing content not visible (without hiding the entire element) by setting the font size to 0. Then, you pull out the title and stick it in there in its place.
One note is that the --font-size-16 is the default. If you have changed your font preferences to be bigger or smaller, you can try changing the number on that css variable to be bigger or smaller. Here is a list of the possible values that are defined in the stylesheet:
I was able to replicate your problem. I was able to make a post with other apps successfully.
Based on the error message, either Interstellar is sending an incorrect post type, or piefed is doing some schema checking beyond the officially documented api. I won't be able to look at it until tomorrow probably, so perhaps @rimu@piefed.social or @jwr1@kbin.earth will be able to look into it sooner.
From what I can find, the managing director of the company that runs serverspace.io (ITGLOBAL.COM NL), which is the company that rents me the VPS space, was arrested by Dutch authorities. The infrastructure in Amsterdam was disconnected without warning when this happened. Since my latest database backup is unfortunately not very recent, and because there is still hope that the severs will come back up, I am waiting and hoping that I regain access to the data. They originally published some somewhat optimistic message, but as of today their website is inaccessible.
I could not find any statements from Dutch police or really any source other than IT Global themselves. But, this event may be related to "Dmitry Gachko" (owner of ITGlobalcom Rus) being added to this sanctions list: https://eur-lex.europa.eu/eli/dec/2024/1484/2026-07-13
I recieved no warning, and I did not know about the ownership structure of serverspace and did not consider that the infrastructure was exposed to this risk. I figured "VPS in Amsterdam from a Dutch company" was rather safe. But "Dutch company operating in NL" does not mean the same as Dutch owned...
First of all, let's dispense with the conspiratorial thinking here:
Is this Piefed/Piefed.social’s “business model” now?
The monetization links in these posts are for the artist, nothing to do with any instance/software. Also, the user making this post is on a lemmy instance, and the community it has been posted to is on a lemmy instance. Nothing about the monetization here has anything to do with piefed other than that you saw it from a piefed instance.
Are you sure you are viewing the Subscribed view on the home page? As far as I can tell, it seems to be working correctly for me and isn't showing posts from communities that I am not subscribed to.
You have a couple options for how to prevent these posts from showing up in the future in places like the All or Popular front pages:
Block the OP (there are usually just a handful of accounts that make up the vast majority of these posts)
Block the community
Hide communities with "moe" in the name (most of them have this naming structure). You can add this at your filters page just above the keyword filters.
Block the domain (most of the images are hosted at files.catbox.moe)
I am not sure what is broken to cause that to pop up all the time, but you can remove it with a bit of custom css added to your profile:
.reply_form_inner > .alert {display: none;}
I am on mobile and can't really verify in the codebase that this won't also hide any other potential flashed alerts that might show up at this position. I tried to be quite specific with the css selector to avoid a false positive match.
You can post from the masto-verse to lemmy/piefed/mbin communities, but you have to format your toot in just the right way. Essentially you need three parts:
The first line of text in your toot is the post title
The second line should be the @-mention of the community user (e.g. @anime@ani.social)
The rest of your toot will now be the body of the post.
I mentioned ani.social since that is the instance I tend to use lemmy the most often. As an example of a post made from mastodon to a lemmy community, you can see here. That post is what led me to look up how to do it correctly.
PieFed and mbin both allow users to follow individual masto accounts, so toots can federate over even if they aren't formatted in exactly the right way. However, lemmy is more strict about it needing to be structured in a way that it can interpret what goes where and to what community the post should belong.
Not easily like that. The communities in a feed need to be specified individually instead of using wildcard notation in that way.
If you are looking for all the communities on an instance, you can use the advanced search on the communities page. As an example, this link should show all the communities local to ani.social that your home instance (piefed.zip) knows about.
A kind of different alternative is that you can look at all the posts created by the users of a particular instance. That can be done by choosing the instance of interest from your home instance's instances page (link in the footer of the page). I hope you were able to follow that confusing instance of a sentence. In any case, click the instance of interest and then there is an option to view information about that instance.
Continuing the example from above, this page is what clicking ani.social takes you to. From there you can browse the users, posts, and communities local to that instance (as seen from your home instance).
One clarifying point about the posts from a particular instance is that it is all the posts created by users of that instance, even if they community that post belongs to is not from that instance. Additionally, it does not include posts made to communities belonging to that instance if the user is remote to that instance.
36:29 - I don't remember who contributed the dev docker compose, but I use it for local development. The main difference that I use it for is that it maps all the source files from your folder and uses the flask development web server (instead of gunicorn). This means that you can tweak python/css/template files locally and then your flask will reload itself and automatically reflect those changes. It makes iterating things a lot quicker compared to doing something like rebuilding an image each time.
PieFed has a default list of domains/instances that are blocked when you do a fresh install for a brand new instance. A critical difference between PieFed and the Tesseract blocks is that any of the blocks in PieFed are completely visible to, and under the control of the admins of the instance. So, ultimately, it is just an out-of-the-box default, but the instance admins always have ultimate control over moderation/federation choices. This Tesseract stuff is taking those powers away from the admins.
Rimu, it would be good if you could just remove all light themes
You might be surprised to learn that rimu is actually a light mode user. They exist! I always feel blinded whenever I have to use my wife's computer or phone for something since she uses light mode as well.
there is a work-in-progress page for Piefed that a contributor is working on
Yeah...sorry for the delay on this one. I have been absolutely slammed with irl work and haven't had time to do much of anything recently. This is also why my actual contributions to PieFed have dried up the past couple weeks. I swear I haven't forgotten about this, and I think the new structure will make this contribution a lot easier as I don't have to replicate a lot of what existed for lemmy already.
You might have enabled low bandwidth mode. On that same page of your settings, just above the theme selection, make sure the low bandwidth mode is unchecked.
Yeah, there was recently a case where somebody was doxxed in the modlog. At that moment, there really wasn't anything that you can do about it. So, being able to have some control over modlog visibility is a way to prevent abuses like that.
No. Anonymous voting used to be in Piefed, but was removed in favor of not federating votes as a user setting instead. Vote manipulation is a thing and this obscures it too much.
Looks like the only real difference is that pylova stores the information in the
data-bs-original-titleattribute instead of thetitleattribute.One note about this after I have used it for a little bit after experimenting is that the vote score text seems like it is a target for tapping to cast a vote. Though, that might just be my fat-fingering things as I am prone to do on mobile. I have also struggled to get the hover text to show up in the past on mobile, so I sympathize with this post.
You can kind of hack this using custom css in your profile. I just tried this and confirmed that it worked, but I couldn't quite get the alignment just right. Basically, the info is there on the element, but it is in the
titleattribute. So, you have to make the existing content not visible (without hiding the entire element) by setting the font size to 0. Then, you pull out the title and stick it in there in its place.One note is that the
--font-size-16is the default. If you have changed your font preferences to be bigger or smaller, you can try changing the number on that css variable to be bigger or smaller. Here is a list of the possible values that are defined in the stylesheet:I was able to replicate your problem. I was able to make a post with other apps successfully.
Based on the error message, either Interstellar is sending an incorrect post type, or piefed is doing some schema checking beyond the officially documented api. I won't be able to look at it until tomorrow probably, so perhaps @rimu@piefed.social or @jwr1@kbin.earth will be able to look into it sooner.
From Sal on matrix:
I'm traveling, so can't really provide much input. However there is some more discussion in a relevant codeberg issue: https://codeberg.org/rimu/pyfedi/issues/1115
First of all, let's dispense with the conspiratorial thinking here:
The monetization links in these posts are for the artist, nothing to do with any instance/software. Also, the user making this post is on a lemmy instance, and the community it has been posted to is on a lemmy instance. Nothing about the monetization here has anything to do with piefed other than that you saw it from a piefed instance.
Are you sure you are viewing the
Subscribedview on the home page? As far as I can tell, it seems to be working correctly for me and isn't showing posts from communities that I am not subscribed to.You have a couple options for how to prevent these posts from showing up in the future in places like the All or Popular front pages:
I am not sure what is broken to cause that to pop up all the time, but you can remove it with a bit of custom css added to your profile:
I am on mobile and can't really verify in the codebase that this won't also hide any other potential flashed alerts that might show up at this position. I tried to be quite specific with the css selector to avoid a false positive match.
You can post from the masto-verse to lemmy/piefed/mbin communities, but you have to format your toot in just the right way. Essentially you need three parts:
@anime@ani.social)I mentioned ani.social since that is the instance I tend to use lemmy the most often. As an example of a post made from mastodon to a lemmy community, you can see here. That post is what led me to look up how to do it correctly.
PieFed and mbin both allow users to follow individual masto accounts, so toots can federate over even if they aren't formatted in exactly the right way. However, lemmy is more strict about it needing to be structured in a way that it can interpret what goes where and to what community the post should belong.
Not easily like that. The communities in a feed need to be specified individually instead of using wildcard notation in that way.
If you are looking for all the communities on an instance, you can use the advanced search on the communities page. As an example, this link should show all the communities local to ani.social that your home instance (piefed.zip) knows about.
A kind of different alternative is that you can look at all the posts created by the users of a particular instance. That can be done by choosing the instance of interest from your home instance's instances page (link in the footer of the page). I hope you were able to follow that confusing instance of a sentence. In any case, click the instance of interest and then there is an option to view information about that instance.
Continuing the example from above, this page is what clicking ani.social takes you to. From there you can browse the users, posts, and communities local to that instance (as seen from your home instance).
One clarifying point about the posts from a particular instance is that it is all the posts created by users of that instance, even if they community that post belongs to is not from that instance. Additionally, it does not include posts made to communities belonging to that instance if the user is remote to that instance.
36:29 - I don't remember who contributed the dev docker compose, but I use it for local development. The main difference that I use it for is that it maps all the source files from your folder and uses the flask development web server (instead of gunicorn). This means that you can tweak python/css/template files locally and then your flask will reload itself and automatically reflect those changes. It makes iterating things a lot quicker compared to doing something like rebuilding an image each time.
I added it in
/user/settingsat one point so that you don't need to relog to turn low bandwidth mode on/off.FYI, next version of PieFed has an "Unban All" button for clearing all domain bans to try to make this easier.
Screenshot from my instance:
PieFed has a default list of domains/instances that are blocked when you do a fresh install for a brand new instance. A critical difference between PieFed and the Tesseract blocks is that any of the blocks in PieFed are completely visible to, and under the control of the admins of the instance. So, ultimately, it is just an out-of-the-box default, but the instance admins always have ultimate control over moderation/federation choices. This Tesseract stuff is taking those powers away from the admins.
You might be surprised to learn that rimu is actually a light mode user. They exist! I always feel blinded whenever I have to use my wife's computer or phone for something since she uses light mode as well.
Yeah...sorry for the delay on this one. I have been absolutely slammed with irl work and haven't had time to do much of anything recently. This is also why my actual contributions to PieFed have dried up the past couple weeks. I swear I haven't forgotten about this, and I think the new structure will make this contribution a lot easier as I don't have to replicate a lot of what existed for lemmy already.
You might have enabled low bandwidth mode. On that same page of your settings, just above the theme selection, make sure the low bandwidth mode is unchecked.
Yeah, there was recently a case where somebody was doxxed in the modlog. At that moment, there really wasn't anything that you can do about it. So, being able to have some control over modlog visibility is a way to prevent abuses like that.
Nothing hardcoded about it. This is all editable in the UI by any admin for their instance, no code editing required.
No. Anonymous voting used to be in Piefed, but was removed in favor of not federating votes as a user setting instead. Vote manipulation is a thing and this obscures it too much.