Blaze

Hello,

It’s more of a meta discussion, but any chance you could reach out to the [email protected] mod? They just posted a half 2025 thread with quite a few comments: https://lemmy.ml/post/31205768

I know you’re banned on .ml, but you could maybe ping them here, or create a thread on [email protected]

cross-posted from: https://vger.social/post/20512447

I'm excited to announce that Voyager now has experimental support for logging in with Piefed! You can try it out today on:

• iOS Testflight
• Android Play Open Testing
• beta.vger.app

This will roll out to the official app stores and vger.app soon(tm), once I’m confident there are no major regressions. If you prefer not to switch to beta builds, just hang tight.

Please note that Piefed support is EXPERIMENTAL! There are still many things that don't work quite right, which I'm hoping to improve over the coming weeks.

The basics including scrolling home/all/local, viewing posts, blocking, commenting and voting should work well. However there are some known issues:

• Can't sign up for a Piefed account in-app, only log in with an existing one
• Subscribed communities list is empty (should be fixed soon!)
• Inbox tab doesn't load
• Comment search doesn't work
• Profile upvoted/downvoted doesn't load
• No moderation tools
• Mark as read doesn't persist
• Creating/editing posts is currently untested
• ...probably a bunch of other stuff too, please let me know below!

Behind the scenes, this interoperability is made possible thanks to aeharding/threadiverse, a new library I am working on to normalize various threadiverse-software APIs. It's open source so any project use it, but it's under heavy development right now. What's cool about this is in the future, adding support for mbin, or whatever else is possible!

Again, feel free to try it out and let me know if there are any more issues to be documented and fixed.

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

>

• Performance Optimizations: >
  • Fixed slow API comment/list endpoint (https://codeberg.org/rimu/pyfedi/issues/883) >
  • Added community total_subscriptions_count column (https://codeberg.org/rimu/pyfedi/issues/881) >
  • Optimized API user sorting (https://codeberg.org/rimu/pyfedi/issues/880) >
  • Performance improvements for community sorting (https://codeberg.org/rimu/pyfedi/issues/879) >
  • Home page performance improvements - reduce reliance on redis and optimize jinja templates >
  • CORS >
• Security & Bug Fixes: >
  • Fixed find_instance_id bug >
  • Added CSRF token protection on various forms >
  • Fixed user reputation update DB deadlocks (https://codeberg.org/rimu/pyfedi/issues/752) >
• UI/UX Improvements: >
  • Bootstrap 5 upgrade (https://codeberg.org/rimu/pyfedi/issues/810) >
  • Mega menu implementation - merge Topics and Feeds into one huge "Communities" menu >
  • Theme updates and CSS improvements >
  • Add your own CSS to PieFed - https://piefed.social/c/piefed_css >
  • Import latest language updates from translation team >
  • Markdown-based CMS so admins can create static pages >
  • Make https://piefed.social/rules using CMS >
• Admin Tools: Database migration fixes, config checking, various admin panel enhancements > >

freamon (45+ commits) >

>

• API Development: >
  • Implemented resolve_object endpoint for generic object resolution (https://codeberg.org/rimu/pyfedi/issues/729) >
  • Added API rate limiting and verification endpoints >
  • Enhanced API comment/list performance work (https://codeberg.org/rimu/pyfedi/issues/883) >
  • resolve_object API functionality (https://codeberg.org/rimu/pyfedi/issues/729) >
  • Lots to do with moderators in the API >
• Federation Improvements: >
  • Fixed community federation issues >
  • Enhanced mod management via API (https://codeberg.org/rimu/pyfedi/issues/814) >
  • Improved ActivityPub compatibility >
  • Federate community bans and user blocks >
• Database & Infrastructure: >
  • Fixed initial DB setup issues (https://codeberg.org/rimu/pyfedi/issues/862) >
  • Improved migration handling >
  • Enhanced query performance >
• Project coordination and pull request reviews > >

wjs018 (25+ commits) >

>

• User Interface Enhancements: >
  • Blocking/unblocking disambiguation for local vs remote users (https://codeberg.org/rimu/pyfedi/pulls/892) >
  • Added seamless bookmark management with HTMX (https://codeberg.org/rimu/pyfedi/pulls/864) >
  • Community page redesign and sidebar improvements (https://codeberg.org/rimu/pyfedi/pulls/806) >
  • Added domains to posts in feeds (https://codeberg.org/rimu/pyfedi/pulls/807) >
  • Communities page redesign >
• Content Features: >
  • Implemented spoiler flair with image blurring (https://codeberg.org/rimu/pyfedi/pulls/759) >
  • Better blockquote and code block styling (https://codeberg.org/rimu/pyfedi/pulls/818) >
  • Inline spoiler text support (https://codeberg.org/rimu/pyfedi/pulls/788) >
  • Text blurring in post previews >
• Admin Features: >
  • Community creation restrictions for admins (https://codeberg.org/rimu/pyfedi/pulls/816) >
  • Additional admin settings panel (https://codeberg.org/rimu/pyfedi/pulls/797) >
  • Low quality community filtering (https://codeberg.org/rimu/pyfedi/pulls/820) >
  • Do not automatically add piefed.social to trusted instances > >

JollyDevelopment (8 commits) >

>

• Moderation Tools: Find and ban user feature for community moderation (https://codeberg.org/rimu/pyfedi/issues/857) >
• Feed Management: >
  • Fixed feed auto-follow functionality (https://codeberg.org/rimu/pyfedi/issues/856) >
  • Feed icon upload fixes (https://codeberg.org/rimu/pyfedi/issues/829) >
  • Enhanced feed link handling (https://codeberg.org/rimu/pyfedi/pulls/849) > >

h3ndrik (12 commits) >

>

• Fix things rimu broke: >
  • Restored user notes after rewrite (https://codeberg.org/rimu/pyfedi/pulls/790) >
  • Restored user flair functionality after rewrite >
• Forms & Security: >
  • Added missing CSRF tokens to polls and other forms (https://codeberg.org/rimu/pyfedi/pulls/870) >
  • Made donate page editable via CMS (https://codeberg.org/rimu/pyfedi/issues/830) >
• Notifications: Fixed scheduled post notifications (https://codeberg.org/rimu/pyfedi/pulls/867) > >

Neshura (5 commits) >

>

• More accurate server overload warning (https://codeberg.org/rimu/pyfedi/pulls/871) >
• Feed Management: >
  • Fixed feed deletion performance issues (https://codeberg.org/rimu/pyfedi/pulls/886) >
  • Fixed feed owner unsubscribe issue (https://codeberg.org/rimu/pyfedi/pulls/885) >
• Documentation: Updated INSTALL.md > >

karasugawasu (1 commit) >

>

• Internationalization: Added ruby annotation support for Japanese text (https://codeberg.org/rimu/pyfedi/pulls/865) > >

sleeping-miyagi (several commits) >

>

• Various video embedding improvements and fixes > >

quokkau (2 commits) >

>

• UI Fixes: Fixed chat avatar sizing issues (https://codeberg.org/rimu/pyfedi/pulls/825) > >

supakaity (1 commit) >

>

• Registration: CAPTCHA is optional (https://codeberg.org/rimu/pyfedi/pulls/735) > >

fxomt (1 commit) >

>

• Theming: Updated fxomt theme > >

>

>

Very noob review

• built quality is solid
• touches are easy to remap thanks to https://caniusevia.com/
• the keycaps are very nice (and kind of made me realize how lower quality the one of the Anne Pro II were)

I was also lucky to got it half price (around 100€ total instead of 200€), so very happy!

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

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

The design is based on the excellent Dactyl keyboard, generated with https://ryanis.cool/cosmos/ and it runs the excellent qmk firmware. It is handwired:

and I have also made a palm support using inkscape and openscad

All printed on a reprap prusa i3 derivative.

This helps me use my computer with less pain, so I want to call out all the wonderful projects and people who contribute to them which made it possible.

Total cost? $60 aud, amortised filament ~15 bucks worth maybe? and a lot of my time haha.

[email protected]:

• 692 users / month
• 878 subscribers
• active mods

[email protected]:

• 445 users / month
• 196 subscribers
• inactive mod

I would suggest to consolidate to the first one, open for discussion.

cross-posted from: https://lemmy.nz/post/24413447

Extensive passenger data has been sold to the US Government by major airline companies including Delta, United Airlines, and American Airlines, new documents reveal.

US travellers' domestic flight records, including their names, full itineraries, and financial details were sold to Customs and Border Protection (CBP).

CBP is a part of the Department of Homeland Security (DHS). They said they acquired the data to track people of interest's air travel.

The documents, obtained by 404 Media, showed that passenger information was sold through a data broker that major airlines including Delta, American Airlines and United Airlines collectively own.