I wish I had #fediverse (#mastodon#pleroma#akkoma#friendica#hubzilla#iceshrimp#snac#lemmy#mbin#kbin#piefed ) #client , I mean like #ELK#lmst#pl-fe #phanpy#tooty#sengi#pinafore#halcyon . That would allow me to sort my subscription feed & browse sorted feed, to see ONLY relevant posts (on topic updates follow-up's?).
Well, the mastodon feature of "LISTS" tries something similiar by allowing to make a sorted list of people\subscription, sorted by your custom category/topic. But it doesn't include #tags. Each #tag must be browsed separately, individually, manually, and there is no feature of list of tags in mastodon.
Lemmy, mbin, kbin, piefed and other #reddit#forum like #activitypub implementations allow you to have topics-threads, but each thread does not replicate very well across multiple servers/instances. Can't be easely crossposted ( by pinging multiple category-bots). And doesn't replicate & easily-searchable as classic mastodon #tags.
Other things I don't like:
twitter like reposts. they make you feel you subscribed not to the original "reposter" friend, but to "reposted content" that you never subscribed for. the #f2f p2p architecture of #scuttlebot (#scuttlebutt) kinda eliminates that, they don't have nor show reposts. you see there only original posts, original content, of friends you follow. Kinda helps to slow down the mind from informational overflow. You can opt out to see posts of friend's friends, if you want more. Tags are also supported there.
threads consist only of information aggretator url sharing in reddit like clones. Without having OP OC like in bbs|AgoraRoad , they just silo you to clickbait to other web sites.
Trying out different front-ends for #Mastodon… as I'm finding the stock web client, whilst it does everything I want in a UI I'm happy to use, has a shockingly bad memory leak. If I leave it on the home feed for a day or so, by the end of the day the UI tab is consuming >5GB RAM and pushing everything out into swap.
That's bad on my laptop which has 8GB… it's even worse on the tablet with 4GB.
I gave #Elk a try on their hosted instance, looks promising, but when I try to build it on #NodeJS v22 to host it here, the post-install scripts try to feed the NodeJS binary a raw #TypeScript program, and of course it barfs not knowing how to interpret that. Had a look at the Dockerfile for it and the base container, no clues there… so that rules out Elk.
I'm giving #Phanpy a try now. Building it wasn't difficult, however I had to dig a bit down further in the README.md to realise I needed to set some environment variables before calling npm run build (notably PHANPY_WEBSITE="${ABSOLUTE_URL}", or else it won't run when you deploy it).
Not liking the fact that boosting or favouriting is a two-click (three-click for boosts actually) process, but that is my principle gripe for now. Other than that, things seem to be reasonably responsive, so we'll see how this goes. If I can get away from needing to keep top open sorting by resident memory usage and periodically killing the worst offender (which more often than not, is the Mastodon tab)… that's a plus.
This majestic bull elk standing in a natural setting, in Yellowstone National Park. The elk is prominently featured with its impressive antlers—often referred to as a "rack"—which are large and symmetrical, showcasing the animal's strength and maturity. Its coat is a rich brown, blending beautifully with the earthy tones of the landscape. https://pixels.com/featured/bull-elk-bill-gallagher.html
This majestic bull elk is standing in a natural setting within Yellowstone National Park. The elk is prominently featured with its impressive antlers—often referred to as a "rack"—which are large and symmetrical, showcasing the animal's strength and maturity. Its coat is a rich brown, blending beautifully with the earthy tones of the landscape.
The background suggests a serene, open meadow, possibly during early morning or late afternoon light, which adds a warm glow to the scene. The elk appears calm yet alert, embodying the wild elegance of North America's largest deer species.
Please read the migration notes carefully for instructions on how to upgrade to this version. This version contains several very long migrations so you will need to be patient when upgrading, and backup your database first!!
Thanks for reading! :gtspat:
Release highlights:
Status edit support: one of our most-requested features! You can now edit your own statuses, and see instance edit history from other accounts too (if your instance has them stored).
Push notifications: probably the second most-requested feature! GoToSocial can now send push notifications to clients via their configured push providers.
You may need to uninstall / reinstall client applications, or log out and back in again, for this feature to work. (And if you're using Tusky, make sure you've got ntfy installed).
Global instance css customization: admins can now apply custom CSS across their entire instance via the settings panel.
Domain permission subscriptions: it's now possible to configure your instance to subscribe to CSV, JSON, or plaintext lists of domain permissions.
Each night, your instance will fetch and automatically create domain permissions (or permission drafts) based on what it finds in a subscribed list.
See the domain permission subscription documentation for more information.
Trusted-proxies helper: instances with improperly configured trusted-proxies settings will now show a warning on the homepage, so admins can make sure their instance is configured correctly.
Better outbox sorting: messages from GoToSocial are now delivered more quickly to people you mention, so conversations across instances should feel snappier.
Log in button: there's now a login button in the top right of the instance homepage, which leads to a helpful page about clients, with a link to the settings panel. Should make things less confusing for new users!
Granular stats controls: with the instance-stats-mode setting, admins can now choose if and how their instance serves stats via the nodeinfo endpoints. Existing behavior from v0.17.0 is the default.
Maintenance router will now be used while your instance is starting up / running migrations. It serves a nice status page informing visitors to wait while migrations complete. Less admin anxiety! Stuff is working!
inspired by #Elk to display icons on recognized profile links
screenshot of a profile with testflight and codeberg icons on the respective links
Detected text:
12:05< Homefedicatfedicatjoined June 7, 20241,404 posts146 followers follows 67website vfedicat.com/A TestFlighttestflight.apple.com/join/b6Ga…A Codebergcodeberg.org/technicat/fedicatme vphilipchu.com/The official account for the fedicat fediverseios client available on testflight. I try toinclude other fediverse stuff to keep itinteresting.fedicatfedicatNow on #departuresdepartures.to/apps/16062#departuras10/26/2024
Digital art of an elk/deer hybrid man with white short hair, laying down on the floor. He has his left leg raised high in the air and is looking towards the viewer smiling. He is wearing a red cardigan hoodie over a white colored shirt, a pair of jeans with rolled up sleeves, and red converse shoes.
@kevinrothrock I like #Elk and #Phanpy both, the timeline is better in Phanpy but posting better in Elk right now, and switching between accounts. But I can use both at the same time.