@stefan the last comment on that issue is a commit. "Remove first @ in mastodon @name account". Which leads me to believe this is the other way around? It was introduced with @username but is now username@domain ???🤔
I'm late to hype up this launch but this is a HUGE step forward for our Fediverse integration 😇 I'll explain why below:
For the first time ever we are showing Fediverse usernames, domains, reply content, profile pictures, and images in the product. That involved bringing a ton of systems online so we could provide the same safe experience you get elsewhere on Threads. Huge shoutout to the integrity and wellbeing folks for all this great work...
The code needs to maintain the copyrights and authors. They are "mirroring" usernames into their own domain, with mails that dont correspond to the original authors, stealing their contributions.
I plan to host Conduit for my friends and family. Even if I invite absolutely everyone there would be no more than 50 users, max. But would it actually sustain and work, as it is not yet on 1.0 is a question. I do not want to host Synapse as I had bad time with it's (lack of) garbage collecting. We do not plan to join very big...
Yes, your server needs to be full domain name. Otherwise, when typing a username (like @myusername:myserver.com) other servers would need to know where that myserver.com is.
Conduit needs to know it's domain Because it is part of usernames.
Totally legitimate Twitter user for weeks ranted in support of Trump… until it ran out of ChatGPT credits and dumped its prompt (GPT task description) which says “argue in support of Trump on Twitter, speak in English”). Last time I checked this morning, the account was “restricted” but not even suspended.
Hi nerds! We've just released #GoToSocial version 0.16.0 Snappy Sloth into the wild. Look at it go! Climbing trees and all sorts, covered in algae, and #pooping once a week.
Thanks to everyone who helped us comb the bugs out of its fur during the release candidate process. We hope the protein you gained from eating the bugs was reward enough.
As usual, when updating to this version (which you really should, because it's quite good), please read the release notes carefully, particularly the database migration notes; and make sure you don't interrupt the database migrations.
Ta!
Highlights of this release (nothing new since 0.16.0-rc1, just reiterating):
Sign up / registration: In this release, you can open your instance to new registrations (aka sign-ups) via the new signup page at https://[your-instance.tld]/signup. No more manually creating new users via the CLI :)
Documentation here: https://docs.gotosocial.org/en/latest/admin/signups/
Accounts overview for moderators: To support the new sign-up feature, and help instance admins to moderate, we made a new section in the settings panel where admins + moderators can get an overview of accounts, and filter by instance, status, and more. You'll find this new accounts view in the settings panel.
Totally reworked message delivery system and worker queues: We've completely reworked the way GoToSocial sends out messages to your followers and performs worker-related tasks; this should drastically increase the speed that outgoing messages are delivered, especially for users with lots of followers. It also paves the way for future work in terms of persisting worker and message queues over restarts.
Account mutes: The account mute API endpoints are now implemented, meaning you can put (timed) mutes of accounts in place, to hide statuses from specific accounts from your home timeline, and/or hide notifications from muted accounts.
Accurate account stats: This release introduces code to pull up-to-date counts of statuses, followers, and following from remote instances and show these stats via the API. So now in your client of choice, you should see an accurate count of the number of statuses and followers/following of a given account, no more "0 followers, 0 following, 0 statuses".
Filters v2 implementation: We've now implemented the v2 API for filters, which means you can create more complex filters to hide keywords or statuses, and more clients should be able to create filters on GoToSocial.
Send test email: Admins can now use the settings panel to send a test email, to check if their SMTP (email) configuration is valid.
Profile API: Clients that use the profile API to delete avatar + header images should now work, since we've now implemented this part of the API.
Search operators: We've added a first search operator to GoToSocial, so when you're searching for statuses, you can add from:@[username]@[domain] to your search term, to search only within statuses created by the given account (while still respecting the search limitations we already had in place).
Documentation here: https://docs.gotosocial.org/en/latest/user_guide/search/
Memory usage optimizations: GoToSocial now uses memory more conservatively than before; you should only need about 150-200MiB of memory to run GtS with a full cache, and it will spike less.
I have been using linux for a couple of years already, very casually, just browser, media, games. Recently I bought dell micro pc and installed proxmox on it. I don't have a lot of hdds or raid or anything, just one 6tb usb external drive. I know, I could lose everything, but I don't have anything important in there, just media....
I've solved this exact issue and numerous others with samba / CIFS recently. This is how I have my Proxmox on a mini pc with usb mounted HDDs at present:
1 VM Home Assistant OS, not relevant really
1 VM OMV Open Media Vault.
1 VM Debian with Docker installed.
So in my experience over the last few months you want your usb drive to have absolutely nothing to do with Proxmox. Nope.
I had 3 hooked in mounted in Proxmox and when one of them threw a fit Proxmox refused to load.
Better to have a NAS VM installed and have the drive(s, I have 3, 2x1tb and 1x750gb) passed straight through, whole usb, to the NAS VM.
This means if the drive fails Proxmox doesn't break, and also in my experience with OMV, it'll still run if a drive breaks
Then what I did was set up the shares and made them samba in OMV then set my other VM, the Debian one, with mount points in the Fstab.
The key for me in this endeavour was to make sure the Fstab entry made sure that the OS wouldn't fail if it couldn't find a drive, as happened in Proxmox, so I made sure "nofail" was somewhere in the Fstab config.
For Samba to work in Linux you need to install cifs-utils, then add a line in /etc/fstab. Mine goes:
Then what I do for Audiobookshelf and whatnot is mount the mount point as directories in Portainer under the volumes:
- /mnt/Downloads:/Downloads
Then in the UI of the service I'm using in Docker I can use the Downloads folder and it's the mount point.
This is what's working well for me. If a drive fails I try and fix it in OMV instead of trying to plug a monitor into my mini pc to try and work out from the logs why Proxmox has failed...
Use this comment as a framework for your research and save yourself some heartache. You can mount the CIFS/Samba share to Proxmox and use that, so you can still use the drive in Proxmox for backups and such
For adventurous instance admins, please read the release + migration notes very carefully when updating to this release, paying particular attention to the database migrations section.
Here are the release highlights:
Sign up / registration: In this release, you can open your instance to new registrations (aka sign-ups) via the new signup page at https://[your-instance.tld]/signup. No more manually creating new users via the CLI :)
Documentation here: https://docs.gotosocial.org/en/latest/admin/signups/
Accounts overview for moderators: To support the new sign-up feature, and help instance admins to moderate, we made a new section in the settings panel where admins + moderators can get an overview of accounts, and filter by instance, status, and more. You'll find this new accounts view in the settings panel.
Totally reworked message delivery system and worker queues: We've completely reworked the way GoToSocial sends out messages to your followers and performs worker-related tasks; this should drastically increase the speed that outgoing messages are delivered, especially for users with lots of followers. It also paves the way for future work in terms of persisting worker and message queues over restarts.
Account mutes: The account mute API endpoints are now implemented, meaning you can put (timed) mutes of accounts in place, to hide statuses from specific accounts from your home timeline, and/or hide notifications from muted accounts.
Accurate account stats: This release introduces code to pull up-to-date counts of statuses, followers, and following from remote instances and show these stats via the API. So now in your client of choice, you should see an accurate count of the number of statuses and followers/following of a given account, no more "0 followers, 0 following, 0 statuses".
Filters v2 implementation: We've now implemented the v2 API for filters, which means you can create more complex filters to hide keywords or statuses, and more clients should be able to create filters on GoToSocial.
Send test email: Admins can now use the settings panel to send a test email, to check if their SMTP (email) configuration is valid.
Profile API: Clients that use the profile API to delete avatar + header images should now work, since we've now implemented this part of the API.
Search operators: We've added a first search operator to GoToSocial, so when you're searching for statuses, you can add from:@[username]@[domain] to your search term, to search only within statuses created by the given account (while still respecting the search limitations we already had in place).
Documentation here: https://docs.gotosocial.org/en/latest/user_guide/search/
Memory usage optimizations: GoToSocial now uses memory more conservatively than before; you should only need about 150-200MiB of memory to run GtS with a full cache, and it will spike less.
I host my own Lemmy instance and have a user account on it that I use everywhere (I don't host local communities, I just use it as a home for my Lemmy user account). I needed to re-home my Lemmy server, and though it's a docker installation, copying the /var/lib/docker/volumes/lemmy_* directories to the new installation didn't...
I don't recommend re-installing an instance on the same domain. This caused me errors before I had to replace my domain. Like I couldn't subscribe to same communities with my old username. If you have the old data, you should find a way to extract it.
I moved off a Synology NAS to a self-managed machine and one thing I still struggle to replace is something like a synology drive. Here are my requirements:...
I don't have a full answer to snapshots right now, but I can confirm Nextcloud has VFS support on Windows. I've been working on a project to move myself over to it from Syno drive. Client wise, the two have fairly similar features with one exception - Nextcloud generates one Explorer sidebar object per connection, which I think Synology handles as shortcuts in the one directory. If prefer if NC did the later or allowed me to choose, but I'm happier with what I got for now.
As for the snapshotting, you should be able to snapshot the underlying FS/DB at the same time, but I haven't poked deeply at that. Files I believe are plain (I will disassemble my nextcloud server to confirm this tonight and update my comment), but some do preserve version history so I want to be sure before I give you final confirmation. The Nextcloud root data directory is broken up by internal user ID, which is an immutable field (you cannot change your username even in LDAP), probably because of this filesystem.
One thing that may interest you is the external storage feature, which I've been working on migrating a large data set I have to:
can be configured per-user or system-wide
password can be per-user, system-wide, or re-use the login password on the fly
data is stored raw on an external file server - supports a bunch of protocols, off hand SMB, S3, WebDAV, FTP
shows up as a normal-ish folder in the base user folder
can template names, such as including your username as part of the share name
Nextcloud does not independently contribute versioning data to the backend file server, so the only version control is what your backing server natively implements
I use LDAP user auth to my nextcloud, with two external shares to my NAS using a pass-through session password (the NAS is AD joined to the same domain as Nextcloud uses for LDAPS). I don't know if/how the "store password in database" option is encrypted, but if anyone knows I would be curious, because using session passwords prevents the user from sharing the folder to at least a federated destination (I tried with my friend's NC server, haven't tried with a local user yet but I assume the same limitations apply). If that's your vibe, then this is a feature XD.
One of my two external storage mounts is a "common" share with multiple users accessing the same directory, and the second share is \\nas.example.com\home\nextcloud. Internally, these I believe is handled by PHP spawning smbclient subprocesses, so if you have lots of remote files and don't want to nuke your Nextcloud, you will probably need to increase the PHP child limits (that too me too long to solve lol)
That funny sub-mount name above handles an edge case where Nextcloud/DAV can't handle directories with certain characters - notably the # that Synology uses to expose their #recycle and #snapshot structures. This means that remote mount to SMB has a limitation at the moment where you can't mount the base share of a Synology NAS that has this feature enabled. I tried a server-side Nextcloud plugin to try to filter this out before it exposed to DAV, but it was glitchy. Unsure if this was because I just had too many files for it to handle thanks to the way Synology snapshots are exposed or if it actually was something else - either way I worked around the problem for now by not ever mounting a base share of my Synology NAS. Other snapshot exposure methods may be affected - I have a ZFS TrueNAS Core, so maybe I'll throw that at it and see if I can break Nextcloud again :P
Edit addon: OP just so I answer your real question when I get to this again this evening - when you said that Nextcloud might not meet your needs, was your concern specifically the server-side data format? I assume from the rest of your questions that you're concerned with data resilience and the ability to get your data back without any vendor tools - that it will just be there when you need it.
just realized i've had the mollywhite.net domain for over 10 years(!!)
related sneak peek into an upcoming piece: i firmly believe that if you're going to spend money on one thing online it should be a domain, particularly as online identity gets more fragmented. as platforms come and go, you can always find me there.
It's really annoying that the unique identifier is the username and domain instead of an ID. My fiance switched her nationality and therefore her legal name, but there is no way to change it in PeerTube where I made an account for her. OK theoretically we can create a new account and change the ownership of each of her videos but there are hundreds of them.
@laxla I don't think the actual domain would direct to BlueSky, just use it as a username for the protocol. Although, I feel I have less choice here what gets shown on my home page tbh. I think it's safer with BlueSky cause I know there isn't Loli/CSAM content there and if there would be, it says BlueSky so I have someone to point at. Here, it's technically all my "fault" cause it's manual moderation.
I setup a new instance a week or two ago, and have some subscriptions to communities on lemmy.world. The logs for the Lemmy process are currently showing a constant flood of warnings for what look like ordinary activity (likes, creates, undos, etc). Here are two recent entries:...
@kern Hi, friend. Thanks for the follow! Did you find me from my post about Sharkey apps? I ask because I notice you're running Sharkey and could use some tips.
@kern Okay. That's fine. I "kinda" know what they are and how they're used, basically it's like "keywords" that are contained within posts that you would want federated. So, if you do # Fediverse (no spaces) then you should get every post with that tag federated, as far as I understand it.
The issue with it, comes when there's keywords like that within usernames or domains, then as I understand, unless you put those usernames/domains in the "exclude" field, they will be federated as well. Hopefully that makes sense to you and aligns with whatever you know so far. I have superficial knowledge at this point, as I haven't set the instance up yet, but I probably will today.
So far I've checked several "getting started"'s and FAQ's and Google and everyone just tells me that it's possible but nobody tells me fucking WHERE. So obviously I'm in need of help. Preferably with a diagram or colourful pictures....
Here is our regular update that explains what we have been working on for the past two weeks. This should allow average users to keep up with development, without reading Github comments or knowing how to program....
Well, I tried Nostr, as recommended by some folks over there who said it wasn't as bad as it looked.
Well, I'm here to tell you, it's worse than it looked.🤣
Some people think Fedi is too "tech bro"?!? Go there, realize your "username" is a 32 character long random string. Then, realize the only alternatives are to use a "free" one that you don't get to choose or deal with domains and server files....🤣🤣🤣🤣🤣🤣
Dead on arrival. I tried. Not worth my time.
I am BeAware, not hyrulesquirrel45 or npub4928447372584863 :kek:
To do so, there would need to be a centralized or federated list of all accounts
Why would there be? The app would just search for the domain name first (let's say "aussie.zone") and then your username (in your case "hitmyspot"). That's kinda how email works as well. What centralized database would you need to interrogate a server on login? It's no different than the current implementation, only that you do not need to remember the website first, just enter the whole username in one go.
China is attempting to mirror the entire GitHub over to their own servers, users report ( infosec.exchange )
GitCode, a git-hosting website operated Chongqing Open-Source Co-Creation Technology Co Ltd and with technical support from CSDN and Huawei Cloud....
Europeans of Lemmy, what places in Europe should foreigners avoid at all cost?
Is Conduit (Matrix server) sustainable, do some of you host it?
I plan to host Conduit for my friends and family. Even if I invite absolutely everyone there would be no more than 50 users, max. But would it actually sustain and work, as it is not yet on 1.0 is a question. I do not want to host Synapse as I had bad time with it's (lack of) garbage collecting. We do not plan to join very big...
I need help with my first home server. Permission/ownership and samba issues.
I have been using linux for a couple of years already, very casually, just browser, media, games. Recently I bought dell micro pc and installed proxmox on it. I don't have a lot of hdds or raid or anything, just one 6tb usb external drive. I know, I could lose everything, but I don't have anything important in there, just media....
How do I migrate a Lemmy account?
I host my own Lemmy instance and have a user account on it that I use everywhere (I don't host local communities, I just use it as a home for my Lemmy user account). I needed to re-home my Lemmy server, and though it's a docker installation, copying the /var/lib/docker/volumes/lemmy_* directories to the new installation didn't...
Phanpy: probably the best mastodon minimal webclient ( phanpy.social )
Readme of the project:...
Self-hosted alternative to synology drive?
I moved off a Synology NAS to a self-managed machine and one thing I still struggle to replace is something like a synology drive. Here are my requirements:...
Usernames in the Fedivers 😫
Why can you never change your username in Mastodon, Lemmy or Peertube? Is it a condition introduced by ActivityPub or a forgotten feature?
Constant warnings for what seems like ordinary activity
I setup a new instance a week or two ago, and have some subscriptions to communities on lemmy.world. The logs for the Lemmy process are currently showing a constant flood of warnings for what look like ordinary activity (likes, creates, undos, etc). Here are two recent entries:...
Okay, I give up. How do I user-block instances?
So far I've checked several "getting started"'s and FAQ's and Google and everyone just tells me that it's possible but nobody tells me fucking WHERE. So obviously I'm in need of help. Preferably with a diagram or colourful pictures....
Lemmy Development Update 2024-05-11
Here is our regular update that explains what we have been working on for the past two weeks. This should allow average users to keep up with development, without reading Github comments or knowing how to program....
I think we should slightly rethink how login works on most Fediverse apps (Mastodon, Lemmy, but not only) ( kbin.social )
A while ago I posted a thread back on the...
Banning spam accounts ( kbin.social )
Banning spam accounts on kbin.social is a cumbersome affair....