[-] Blaze@lemmy.dbzer0.com 1 points 12 hours ago

Like I said, I can’t force you to see it. The fact that you think it would mean re-engineering the whole platform means you aren’t getting it. It’s almost literally the suggestion of least effort, it’s largely an organizational change that encourages instances not to cope with more responsibility than they can deal with by encouraging decoupling the current structure into two more specialized ones.

You make this about me, but nobody else sees it. As you said, content instance are possible today (admins just have to disable their registrations), but nobody does that.

[-] Blaze@lemmy.dbzer0.com 2 points 12 hours ago

I've had situations where it was useful, and managed to get unbanned (I was apparently talking about the Fediverse too much)

[-] Blaze@lemmy.dbzer0.com 5 points 22 hours ago* (last edited 22 hours ago)

@unruffled@lemmy.dbzer0.com , can we ask OPs to distinguish between temporary suspensions and permanent bans when posting in this community?

[-] Blaze@lemmy.dbzer0.com 3 points 22 hours ago
[-] Blaze@lemmy.dbzer0.com 1 points 1 day ago* (last edited 1 day ago)

Being a dedicated content instance provider would also inherently imply dedicating that instance to a certain, more controlled type of content. An authentication instance might want to cater to a geography, which will probably decide to interact with the rest of the world and to provide adequate verification and certification mechanisms. A content instance might want to cater to a geography or a subject, resulting in specialized participation, with certification and verification based on the content, not the user.

Those control mechanisms were available to lemm.ee. There's a reason most active instances mostly defederate from certain instances.

You keep seeing monolithic instances that congregate the most communities as a plus. That’s a negative in my perspective on the fediverse. It shouldn’t be competing reddit clones with the one having the most communities winning out.

I don't, I'm the one regularly pushing for more decentralization of communities (https://reddthat.com/post/20197120 , e.g. !privacy@lemmy.dbzer0.com vs !privacy@lemmy.ml)

But I would rather have instances use the tools they currently have (and hopefully more will come with Piefed development catching up) rather than trying to re-engineer the whole platform when some instances don't use the existing moderation tools.

[-] Blaze@lemmy.dbzer0.com 8 points 1 day ago

This is a community ban, not an instance one

[-] Blaze@lemmy.dbzer0.com 4 points 2 days ago

Feeds don't really completely solve fragmentation, as comments are still attached to a single community, and you don't see them in a single view.

To completely solve fragmentation, you need a consolidated view of comments as well

https://piefed.zip/post/100161

All comments from 5 crossposts in a single view

[-] Blaze@lemmy.dbzer0.com 11 points 2 days ago

Being able to search in a community is already a good improvement

[-] Blaze@lemmy.dbzer0.com 11 points 2 days ago

I'm surprised they're still around. That's some dedication for a platform they say they despise

20
Star Trek lego? (i.imgur.com)
1

cross-posted from: https://piefed.social/post/956553

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 > >

>

>

104
submitted 3 weeks ago by Blaze@lemmy.dbzer0.com to c/android@lemdro.id

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

As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it's more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.

19

!communitypromo@lemmy.ca

27

!movies@piefed.social

57

!fedigrow@lemmy.zip

1
125
submitted 4 weeks ago* (last edited 4 weeks ago) by Blaze@lemmy.dbzer0.com to c/meta@lemm.ee
9
submitted 4 weeks ago by Blaze@lemmy.dbzer0.com to c/movies@lemm.ee
172
submitted 1 month ago* (last edited 4 weeks ago) by Blaze@lemmy.dbzer0.com to c/fediverse@lemmy.world
179
submitted 1 month ago* (last edited 1 month ago) by Blaze@lemmy.dbzer0.com to c/fediverse@lemmy.world

cross-posted from: https://discuss.tchncs.de/post/37857048

chore: set default instance to lemmy.zip, remove lemm.ee

Thank you for all your work!

49
submitted 1 month ago by Blaze@lemmy.dbzer0.com to c/meta@lemm.ee

cross-posted from: https://lemmy.dbzer0.com/post/45876492

Context: I tried to use the Piefed migration feature to migrate !barcelona@lemm.ee to !barcelona@piefed.social

https://piefed.social/c/barcelona now exists, with all the existing posts there, as well as the icon and description.

It even moved some subscribers (there are around 100 now), from what I understand those were Piefed subscribers that got automatically moved.

The one caveat is that from Lemmy instances, the community doesn't have show old posts (see https://lemm.ee/c/barcelona@piefed.social), but if you were restarting a community from scratch you wouldn't have access to your old posts anyway.

This ensure that at least the posts are transferred to a community on an active instance, which is probably the main concern for lemm.ee communities at the moment.

view more: next ›

Blaze

joined 2 years ago