[-] [email protected] 3 points 7 hours ago

Yeah this is likely effecting most new PieFed instances.

[-] [email protected] 3 points 7 hours ago* (last edited 7 hours ago)

a vision towards atmosphere and quality

Yes, it does, that's why I've put the emphasis I have on blocking and moderation features. Some of my ideas, like filtering out comments that just say "This", later proved to be kinda oppressive in some people's eyes so there's a difficult balancing act there when we start to do social engineering. As if the technical engineering wasn't hard enough already.

It might be interesting to tweak the 'Hot' algo to boost posts where the OP is involved in the discussion on the post...

[-] [email protected] 5 points 8 hours ago

Ah so that's why we have that setting how it is. Good to know.

I've changed it back now. We'll need something smarter for the bold words issue.

[-] [email protected] 5 points 1 day ago

Turn on the captions, he explains a lot of things.

[-] [email protected] 22 points 1 day ago* (last edited 1 day ago)

But usage is not going downwards. Check these stats out: https://fediverse.observer/stats

MAU has been steady at 1.1 million since this time last year.

Within the fediverse there are some platforms that are losing ground and some that are growing.

282
submitted 2 days ago by [email protected] to c/[email protected]
[-] [email protected] 5 points 2 days ago* (last edited 2 days ago)

Unrelated but sorta: there's also these errors in the console, because Cloudflare is trying to inject a bunch of analytics and tracking which PieFed's CSP is blocking:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).

None of the “sha512” hashes in the integrity attribute match the content of the subresource at “https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015%E2%80%9D. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. register
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. node.js:417:1
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).

None of the “sha512” hashes in the integrity attribute match the content of the subresource at “https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015%E2%80%9D. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”.

[-] [email protected] 5 points 2 days ago

Jerry your Cloudflare is getting in the way. When I go to feddit.online and run this JS in my browser dev tools I get a 403 and a bunch of gibberish from Cloudflare in my console:

fetch('/api/alpha/user/login', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    username: 'testuser',
    password: 'secretpassword'
  })
})
  .then(response => response.text())
  .then(text => {
    console.log('Raw response:', text);
    try {
      const json = JSON.parse(text);
      console.log('Parsed JSON:', json);
    } catch (err) {
      console.error('Failed to parse JSON:', err);
    }
  })
  .catch(error => console.error('Fetch error:', error));


<div class="cf-section cf-wrapper">
        <div class="cf-columns two">
          <div class="cf-column">
            <h2 data-translate="blocked_why_headline">Why have I been blocked?</h2>

            <p data-translate="blocked_why_detail">This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.</p>
          </div>

          <div class="cf-column">
            <h2 data-translate="blocked_resolve_headline">What can I do to resolve this?</h2>

            <p data-translate="blocked_resolve_detail">You can email the site owner to let them know you were blocked. Please include what you were doing when this page came up and the Cloudflare Ray ID found at the bottom of this page.</p>
          </div>
        </div>
      </div><!-- /.section -->


93
submitted 2 days ago by [email protected] to c/[email protected]
[-] [email protected] 7 points 2 days ago

1600 users, 948 monthly active. https://piefed.social/about

Across all instances, about 1500 mau and rising.

37
submitted 3 days ago* (last edited 3 days ago) by [email protected] to c/[email protected]
[-] [email protected] 5 points 3 days ago

Disappointing to see such slop so heavily upvoted just because it fits what people want to see.

[-] [email protected] 6 points 4 days ago* (last edited 4 days ago)

The only wasted part is when you know it's over but still continue.

But even then there is a lot to learn from that.

18
submitted 1 week ago by [email protected] to c/[email protected]

Votes are no longer using an alt profile so instead you now have the choice of federating your votes or not. Please go to https://piefed.social/user/settings and see the 'Federate votes' checkbox. It should be showing the opposite of what you had for the 'Vote privately' checkbox that was there before, however the behavior and tradeoffs are really quite different so you might want to revisit that decision.

Whatever you choose there, you can still override that on a case-by-case basis by holding down your mouse button on the voting controls ("long press" on a touch device) of a post/comment.

If this is all news to you, please see https://piefed.social/post/979325 and https://piefed.social/post/956572

51
submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]

A way for people to screen out AI generated content, similar how people can screen out nsfw content already.

It works the same as the nsfw filter except underneath it's an integer instead of a Boolean.

Content authors will flag their content as AI-generated, on a sliding scale from 0 (no AI) to 100 (completely AI generated. Intermediate values could be used too although this amount of nuance may be confusing for some.

Users will be able to set a "AI generated threshold" which filters out content above that threshold. At the UI level this could be presented as a checkbox but maybe a slider would be good.

Mods need to be able to set the AI level on content, as they do now with NSFW content.

Communities will have an AI-gen value too, which is automatically applied to all content within. Instance admins can override this value too, for local or remote communities.

Thoughts?

9
submitted 1 week ago by [email protected] to c/[email protected]
53
submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]

Due to difficulties making private voting a viable reality , we've been playing around with an alternative approach: public/private votes becomes "federated votes" where you can choose whether to send your vote off to other instances or whether it only counts locally and doesn't get federated.

There are obvious drawbacks to casting a vote that doesn't federate. But this avoids all the issues with which instances to trust (and who decides that) and avoids the distrust generated by all these sockpuppets with weird names running around and the need to explain in difficult technical detail why we're doing that, no it's not vote manipulation, don't ban / defederate us, etc etc

The video shows how the user interface could work. Basically there is a setting in your profile that determines whether your votes federate and an optional override you can use on a case-by-case basis.

There is an assumption here that people will generally choose one mode (public or private) and stick with that for most of their votes. The popup will only be used rarely so the extra clicks and the waiting involved won't be much of an issue.

Thoughts?

36
submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]

PieFed has a chat room now, at https://chat.piefed.social/

We're using Zulip for this, which is an interesting combination of forum / chat room with strong support for threaded discussions.

You can use your piefed.social login with chat.piefed.social, BUT you need to use your email address instead of your user name. Use the same password.

The login details used by chat.piefed.social are synced with piefed.social when you log in to piefed.social or when you set a new password in your settings so if you haven't done either of those recently then log out of piefed.social and log back in.

You can also just make an account at https://chat.piefed.social/register/ if you don't have a piefed.social account.

This chat.piefed.social does not replace our Matrix rooms, it is an additional option for those who don't use Matrix.

42
submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]

PieFed has a chat room now, at https://chat.piefed.social/

We're using Zulip for this, which is an interesting combination of forum / chat room with strong support for threaded discussions.

You can use your piefed.social login with chat.piefed.social, BUT you need to use your email address instead of your user name. Use the same password.

The login details used by chat.piefed.social are synced with piefed.social when you log in to piefed.social or when you set a new password in your settings so if you haven't done either of those recently then log out of piefed.social and log back in.

You can also just make an account at https://chat.piefed.social/register/ if you don't have a piefed.social account.

This chat.piefed.social does not replace our Matrix rooms, it is an additional option for those who don't use Matrix.

3
KDE Plasma 6.4 is out (thelibre.news)
submitted 1 week ago by [email protected] to c/[email protected]

I don't normally get too excited by new releases but this one packs in a lot of great stuff!

110
submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/[email protected]

See the install instructions to get the latest release. Switch to the "v1.0.x" git branch to run this release rather than the latest code.

Existing instances:

git pull  
git checkout v1.0.0  
./deploy.sh or ./deploy-docker.sh  

PieFed usage has been growing very fast lately, with many communities moving to piefed.social from lemm.ee and several new instances such as piefed.ca, piefed.blahaj.zone, and more .

With this increased attention a light has been shone on many previously ignored parts of PieFed so we've been hard at work closing the gaps and incorporating new ideas from new people. Also it has become necessary to begin doing proper releases so instances have a more stable place to park themselves without being exposed to the constant turmoil that comes from running bleeding-edge code in production.

Due to feedback from a wider audience than before, some of the idiosyncratic features that I built because of my personal obsessions have been made optional and OFF by default, such as the 4chan meme filter, meme communities being flagged as 'low quality' and so on. Private voting has fundamental issues and could be removed soon, I'll make a separate post about that.

The API is now in use and the mobile app Interstellar works with it well. Other apps are working on PieFed compatibility too. Again a lot of work went in there to get it ready for prime time.

To sum up - leading up to this release the last few weeks have showed intensive development with major focus on performance optimization, UI/UX improvements and enhanced federation capabilities. We made significant progress on API development, moderation tools, and overall platform stability.

Below is an incomplete list of some things we've worked on in June. Sorry to those whose work I overlooked, it's been a deluge.

rimu (178+ commits)

freamon (45+ commits)

wjs018 (25+ commits)

JollyDevelopment (8 commits)

h3ndrik (12 commits)

Neshura (5 commits)

karasugawasu (1 commit)

sleeping-miyagi (several commits)

  • Various video embedding improvements and fixes

quokkau (2 commits)

supakaity (1 commit)

fxomt (1 commit)

  • Theming: Updated fxomt theme

13
submitted 2 weeks ago by [email protected] to c/[email protected]

Cmon Japan, get it together.

view more: next ›

rimu

0 post score
0 comment score
joined 2 years ago
MODERATOR OF