jwr1

As the title says, several users have noticed issues with their posts and comments not federating. The pattern seems be that there are issues if you are posting to a Lemmy server that's on v0.19.5 (for example, federation to lemmy.world seems to be working fine, they're only on v0.19.3). Please be patient while we investigate.

Additionally, incoming federation seems to be working just fine, so you shouldn't notice a lack of posts or comments or anything like that.

Edit: please see my comment about the fix down below

...

...

...

...

This server is now running Mbin v1.7.0. Let me know if you run into any issues.

Here are the user-facing changes listed below (copied from here):

• Full federation with PeerTube: threads are created for new uploads, synced likes, dislikes and comments
• Direct messages will work across servers now, supporting lemmy instances (mastodon private mentions are not working, yet). We added a button on the profile page of users as well
• we completely redesigned the messages view to resemble a chat interface
• Pinning and unpinning entries will now federate
• We now support push notifications. They can be enabled on the notifications page (/settings/notifications). If you do not see a button for enabling push notifications, that usually means that your browser does not support them
• New supported languages: Brazilian Portuguese, Danish, Filipino, Galician
• Modlog changes:
  • the instance wide modlog now includes the magazine in which the moderator action occurred
  • adding and removing a moderator are now shown in the modlog
• creating threads on magazines can now be restricted to moderators and we added support for remote magazines that already have this setting enabled
• Add a cake day display on the profile page and the user popup
• we increased the cookie lifetime, so you do not have to login as regular as before (7 days -> 3 weeks)
• you can now hide the related panels via the appearence settings
• there are now notifications for reports
  • created: admins, global mods, magazine mods
  • approved: reported user
• When editing a thread that is posted to a remote magazine hosted on an mbin instance the edit will now correctly federate
• We updated the federation page. It now shows federated, defederated and dead instances. It also shows the software and the version of it the instance is running on
• When editing your profile or a magazines profile, your changes should be visible on remote instances nearly instantly
• we show a leaf icon next to users and magazines which have been active for less than 30 days now
• when editing a thread you can now edit all fields
• fix the aggressive fetching of the URL field when editing it

Copied from linked post:

I'm very happy to announce the release of htmx 2.0. This release ends support for Internet Explorer and tightens up some
defaults, but does not change most of the core functionality or the core API of the library.

Note that we are not marking 2.0 as latest in NPM
because we do not want to force-upgrade users who are relying on non-versioned CDN URLs for htmx. Instead, 1.x will
remain latest and the 2.0 line will remain next until Jan 1, 2025. The website, however, will reference 2.0.

Major Changes

• All extensions have been moved out of the core repository to their own repo
  and website: https://extensions.htmx.org. They are now all versioned individually and can be developed outside of
  the normal (slow) htmx release cadence.

  • Most 1.x extensions will work with 2.x, however the SSE extension did have a break and must be upgraded.
  • The older extensions remain in the /dist/ext directory so as to not break the URLs of CDNs like unpkg, but please
    move to the new extension URLs going forward

• We removed the deprecated hx-sse and hx-ws attributes in favor of the extensions, which were available and
  recommended in 1.x.

• HTTP DELETE requests now use parameters, rather than form encoded bodies, for their payload (This is in accordance w/ the spec.)

• We now provide specific files in /dist for the various JavaScript module styles:

  • ESM Modules: /dist/htmx.esm.js
  • AMD Modules: /dist/htmx.amd.js
  • CJS Modules: /dist/htmx.cjs.js
  • The /dist/htmx.js file continues to be browser-loadable

• The hx-on attribute, with its special syntax, has been removed in favor of the less-hacky hx-on: syntax.

Minor Changes

• We made some default changes:
  • htmx.config.scrollBehavior was changed to 'instant' from 'smooth'
  • As mentioned previously, DELETE requests now use query parameters, rather than a form-encoded body. This can
    be reverted by setting htmx.methodsThatUseUrlParams to the value ['get'],
  • htmx.config.selfRequestsOnly now defaults to true rather than false

Features

Not much, really:

• The selectAndSwap() internal API method was replaced with the public (and much better) swap() method
• Web Component support has been improved dramatically
• And the biggest feature of this release: the website now supports dark mode! (Thanks @pokonski!)

A complete upgrade guide can be found here:

htmx 1.x -> 2.x Migration Guide

If you require IE compatibility, the 1.x will continue to be supported for the foreseeable future.

kbin.earth now has 102 users (and 61 monthly active users at the moment)! I know this isn't a lot compared to the other big fediverse servers, but I still think it's a milestone to celebrate. Additionally, according to FediDB, kbin.earth is actually the 3rd most active Mbin server, behind kbin.run and fedia.io!

As a way to celebrate, I thought we should give kbin.earth its own icon. Attached to this post are the (very) rough drafts of a few icon designs I came up with. Please comment which ones you prefer and what kind of improvements/changes you think could be made. If you'd like, feel free to come up with your own designs too. (Also, as a disclaimer, I did take some inspiration from lemmy.world's icon.)

For me personally, I think 2 & 5 have too much color, so I'd say they're my least favorite. Honestly, I think I'd prefer either 1, 4, or 7.

This post doesn't directly affect kbin.social users, but it is relevant. It discusses some of the potential pros/cons of Kbin and the pros/cons of Mbin, and also the direction the kbin.earth server is heading.