tk, to fediverse
@tk@bbs.kawa-kun.com avatar

Should I go trenchless or tankless for my instance? :blobfoxthinkgoogly:

technicat, to mastodon
@technicat@iosdev.space avatar

I've tested with , , , , , , , , , , and and can't say it works perfectly, but it works!

realcaseyrollins, to conservative in New filings reveal FBI authorized use of DEADLY FORCE when they raided Mar-a-Lago
@realcaseyrollins@noauthority.social avatar

@LookBehindYouNowAndThen Report it to the mods. I'm on and I think he's on , so there's nothing I can do.

But I'm a freedom of speech homie so I wouldn't complain about it too much; if the speech offends you, you should be able to block or mute him yourself on your end.

utzer, to fediverse
@utzer@soc.utzer.de avatar

Really sad that does not have good photo support, I really would love to just swipe through photos sometimes or have a timeline that just contains posts with photos.

There is only that comes close to what I wait for since 2015 to happen in the , but not really close. It seems to be very easy idea, but probably impossible to program or implement. 😔😢

Really sad.

linuxine, to fediverse

Dammit voilà que mon est tout cassé, je n'ai rien touché mais il n'accède plus aux notifications et aux interactions parce qu'un serveur dans la liste ne répond pas on dirait, ça vous est déjà arrivé ? 🤔

apps, to fediverse
@apps@toot.fedilab.app avatar

has been updated to 1.2.0

  • Detects instance limits
  • Timezone is stored in session
  • Fix issues
  • Fix polls not removed when hidden
  • Three new languages (pl, uk and ru)
  • Works with PHP 8.2+ (with Symfony 7+)
  • Installation possible with

https://plan.fedilab.app/

glukozavr, to mastodon
@glukozavr@mastodon.gamedev.place avatar

Am I correct, assuming that @tootapp is dead app? On AppStore no updates for a year and I seems not to find any activity around it anymore.

Which client would be the most versatile to work with and maybe some other services with iOS app and alive?

tk, to fediverse
@tk@bbs.kawa-kun.com avatar
sengi_app, to mastodon
@sengi_app@mastodon.social avatar

Small of what next update might bring. 😉

Still lots of work to do, and it's clearly not really fun stuff. But I know some of you will be happy to get it. 🙂

(If you want to get it sooner, buy me some coffee via my patreon!)

light theme preview

crossgolf_rebel, to fediverse

Fediverse-Serie: Pleroma & Akkoma: Einfache Kommunikation im Fediverse - GNU/Linux.ch

Pleroma und Akkoma gehören wegen ihrer Einfachheit zu den beliebtesten Diensten im Fediverse. Gegenüber Mastodon bieten sie default 5000 Zeichen und einige weitere Funktionen.

Herkunft und Einbindung ins Fediverse
Pleroma und dessen Fork Akkoma gehören einerseits neben Mastodon, Calckey/Firefish, Misskey, Foundkey und GoToSocial nicht nur wegen des Aussehens und Handlings zu der Sparte der twitterähnlichnen Microbloggingdienste im Fediverse. Es unterscheidet sich andererseits recht deutlich insbesondere von Mastodon, wobei das klassische Aussehen doch recht ähnlich ist - aber davon später mehr.

Wenn Du gerne eine Art Mastodon mit richtigen Microblogging-Möglichkeiten haben willst, dann würde ich tatsächlich stark zu Pleroma oder Akkoma raten!
Pleroma/Akkoma ist ähnlich wie Mastodon, aber übersichtlicher und mit mehr Funktionen: Es kann zusätzlich längere Posts (default bis 5000 Zeichen Länge) und Textformatierungen wie Markdown, "schöne Links", Zitate, Aufzählungslisten u.v.m. (was allerdings wie alle Textformatierungen nicht von Mastodon, aber von allen anderen Diensten dargestellt wird)....

https://gnulinux.ch/fediverse-serie-pleroma-akkoma-einfache-kommunikation-im-fediverse

ueckueck, to fediverse German
@ueckueck@dresden.network avatar

Ückück und das Fediverse - meine neue Kolumne bei @gnulinux

Ein neues Projekt steht an und ich freue mich sehr. Ab diesem Monat werde ich regelmäßig für GNU/Linux.ch über das Fediverse schreiben, mal spezielle Projekte vorstellen, mal von Veranstaltungen berichten, mal einen Blick auf die Meta-Ebene vagen - es gibt jedenfalls genug zu berichten, dass ich eine Weile beschäftigt bin :D

Mehr dazu erfahrt ihr in diesem Ankündigungs-Artikel der Redaktion:
https://gnulinux.ch/wzs-ueckueck-und-das-fediverse

Die Kolumne wird ab dem 6. Mai 2024 an jedem 1. Montag im Monat erscheinen.

saria, to fediverse
@saria@social.saria.fun avatar

Just upgraded #Pleroma, which I’d been putting off for a while.

I had been using the packaged, “OTP”, version of Pleroma, but it turned out the package is ancient, and it required an older cryptography library. Because I’d upgraded to a newer version of #Ubuntu, the older crypto library had been removed and replaced with a newer version.

I found all this out when I tried to upgrade and got an error, searched for the error text, and found the bug report with a detailed explanation of the problem and solution.

So, I just backed up my instance, removed the OTP version of Pleroma, and re-installed it directly from the source repository.

The whole process took maybe half an hour, and no more than 10 or so commands. Basically:

  1. Stop Pleroma (so it’s not running while trying to backup/update): sudo systemctl stop pleroma.
  2. Backup my instance.
    1. First make a place to store the backup: mkdir -p ~/backup/pleroma. I made it (temporarily!) world-writable to make things easier: chmod 777 ~/backup/pleroma.
    2. Backup the database: sudo -Hu postgres pg_dump -d pleroma --format=custom -f /home/saria/backup/pleroma/pleroma.pgdump.
    3. Backup the configuration: sudo cp /etc/pleroma/config.exs /home/saria/backup/pleroma.
  3. Delete the Pleroma installation (actually, just put it to one side for now, just in case): sudo mv /opt/pleroma /home/saria/backup/pleroma/old-installation and sudo mv /etc/pleroma /home/saria/backup/pleroma/old-configuration.
  4. Adjust stuff that differs between the OTP installation and the source installation.
    1. Update the pleroma user’s home directory: sudo usermod -d /var/lib/pleroma pleroma (Here I got an error that the pleroma user was still running process 758. No problem, just sudo kill 758, then retry.)
    2. Make the “new” locations: sudo mkdir - /opt/pleroma /var/lib/pleroma. (I think /var/lib/pleroma already existed, and was storing images and uploads, which was fine.)
    3. Make the pleroma user the owner of those locations: sudo chown -R pleroma: /opt/pleroma /var/lib/pleroma.
  5. Change to the pleroma direcory: cd /opt/pleroma.
  6. Download pleroma: sudo -Hu pleroma git clone -b stable <a href="https://git.pleroma.social/pleroma/pleroma" rel="ugc">https://git.pleroma.social/pleroma/pleroma</a> /opt/pleroma.
  7. Build pleroma.
    1. Get the dependencies: sudo -Hu pleroma mix deps.get.
    2. Run the build: sudo -Hu pleroma MIX_ENV=prod mix pleroma.instance gen.
  8. Configure pleroma.
    1. Copy the generated configuration file: sudo -Hu pleroma mv config/generated_config.exs config/prod.secret.exs.
    2. Edit the configuration file config/prod.secret.exs, copying all the important stuff (passwords, salts, personal settings) from the old file at /home/saria/backup/pleroma/old-configuration/config.exs.
  9. Run the database migration: sudo -Hu pleroma MIX_ENV=prod mix ecto.migrate.
  10. Restart Pleroma: sudo systemctl start pleroma. I discovered (using sudo systemctl status pleroma) that Pleroma would not start. I realised that was because the systemd service file was still trying to start the old, OTP version. So I replaced the service file with the one from the source installation (sudo cp -f /opt/pleroma/installation/pleroma.service /etc/systemd/system/pleroma.service) and tried again. Now I got an error from systemd because the service file had changed, telling me I had to do systemd daemon-reload. So I did sudo systemd daemon-reload, and tried to start Pleroma again. Success! 🦸🏾‍♀️

As you can see, I ran into some hiccups, but the documentation and error messages were clear enough that I was able to fix stuff and move on.

Now, I am no expert on any of this stuff! I know literally nothing about Erlang or Elixir (the languages/tools/whatever that Pleroma is made with). But as you can see, if you take the time to carefully read the documentation, and understand what each step is actually doing, it’s really not that hard! 💪🏾

@selfhosted

fediverseobserver, to fediverse

Found 4 new servers and 11 servers died off since 3 hours ago.

22,758 servers checked. 13,059,649 Total Users with 1,574,993 Active Users today. Check out the stats!

New servers found:

penaz.cloud a server from Portugal
corteximplant.net a server from Germany
sk.240517.xyz a server from Private
ap.jmuk.org a server from United States

Help others find a home, send them to fediverse.observer

fediverseobserver, to fediverse

Found 2 new servers and 11 servers died off since 3 hours ago.

22,748 servers checked. 13,059,649 Total Users with 1,574,993 Active Users today. Check out the stats!

New servers found:

sk.240517.xyz a server from Private
ap.jmuk.org a server from United States

Help others find a home, send them to fediverse.observer

fediverseobserver, to fediverse

Found 2 new servers and 8 servers died off since 3 hours ago.

22,751 servers checked. 14,024,641 Total Users with 1,574,993 Active Users today. Check out the stats!

New #fediverse servers found:

sk.240517.xyz a #sharkey server from Private
ap.jmuk.org a #pleroma server from United States

Help others find a home, send them to fediverse.observer

fediverseobserver, to fediverse

Found 1 new servers and 7 servers died off since 3 hours ago.

22,751 servers checked. 14,024,641 Total Users with 1,574,993 Active Users today. Check out the stats!

New servers found:

ap.jmuk.org a server from United States

Help others find a home, send them to fediverse.observer

coloco, to threads Spanish
@coloco@mstdn.social avatar
freakazoid, to mastodon
@freakazoid@retro.social avatar

While folks are thinking of leaving , just a friendly reminder that let a known TERF (Alex Gleason) join the project and only kicked him out because of conflict over code.

kalisz79, to random Polish
@kalisz79@pol.social avatar

To nie jest trochę to co już mamy dzięki wspólnemu logowaniu do różnych usług na pol.social via @ftdl ? :)
https://thenewstack.io/one-login-towards-a-single-fediverse-identity-on-activitypub/

m0bi13, (edited )
@m0bi13@pol.social avatar

@kalisz79 @ftdl

Dobrym podejściem są też web-aplikacje starające się integrować wiele profili z różnych serwisów. Np. , który ostatnio integruje i (jego Media-firt UI jest świetne).

Podobnie na integruje profile z różnych usług: Mastodon, , Pixelfed, , , .

Takie podejście mi się podoba :)

Innym tematem jest uparte trzymanie się przez Mastodona obsługi jedynie typu Note (i ułomne wyświetlanie Article). A ponieważ Mastodon dominuje w , nie rozwija się (tak jak mogłoby) wsparcie dla innych typów treści : image, video, audio, artist, album, track, playlist. De facto obrazki czy filmiki albo audio to po prostu załączniki do typu Note, bo Masto tak ma i nic innego nie wyświetli :/

Więc IMO pole do rozwoju jest ogromne, nie trzymajmy się kurczowo jednego konta (to wymysł marketingowców budujących silosy), zostańmy przy jeden login do wielu usług, jeśli już musimy ;)

fediverseobserver, to fediverse

Found 2 new servers and 5 servers died off since 3 hours ago.

22,803 servers checked. 14,002,928 Total Users with 1,584,651 Active Users today. Check out the stats!

New servers found:

grass9.com a server from Singapore
fsebugoutzone.org a server from United States

Help others find a home, send them to fediverse.observer

maegul, (edited ) to ghost
@maegul@hachyderm.io avatar

I think the and federations pose interesting questions about what platforms can and should be.

Do we actually want blogs and feeds of blogs folded into a mastodon/microblog social feed?

Do we want to read and comment on blogs on mastodon?

Do we want all the diversity of the fediverse fed into a single platform's UI and hope that it works well?

Are we worried that some choices by our platform or instance admin might hinder this process?

I'm rather skeptical.

1/

mima,

@maegul

I think the fedi needs to be more about clients/apps than it is currently.

Agreed, and I kinda touched on this earlier about how the should've simply been a frontend where people just use their main fedi account instead of having to create another account for forums in a link aggregator... ​:sagume_think:​

Tbh all the implementations in the first place should've been backends first and foremost. Why should I not be able to have 's frontend in or ? And the other way around too. This does mean that we will have to all agree on a common client API and MastoAPI will dominate, but I'd rather have Mastodon dictate client API than fediverse implementations. ​:seija_coffee:​

RE: https://makai.chaotic.ninja/notes/9s85trbv7h

fediverseobserver, to fediverse

Found 3 new servers and 7 servers died off since 3 hours ago.

22,847 servers checked. 13,977,480 Total Users with 1,593,606 Active Users today. Check out the stats!

New servers found:

vanilla.choco.ink a server from Private
majestic12.airforce a server from Luxembourg
fioredon.ysizuku.com a server from South Korea

Help others find a home, send them to fediverse.observer

mima, to lemmy

Tbh I think the like and would make a lot more sense if they were simply frontends and perhaps a backend too but just for the forums themselves. IOW, no accounts live in Lemmy or kbin, all users post from their preferred account instead.

Sure you can already technically do that from your or or whatever fedi you're in, but that means using whatever app you're on right now, which almost certainly means it's not a UI. Not ideal at all.

If I had any good programming skills I'd make it so that the link aggregator is merely a client that uses the Mastodon (with extensions too) and Misskey APIs, treat (almost) all actors as their own forums or subs, and each post would be a boost from said actor. Users authenticate from their preferred fedi account. Voting would be tallied by few special actors, which internally receive votes via direct messages (the app will make this transparent, but this also means you can technically vote without the app if you know the exact command), which will effectively make votes secret to non-admins like in . Users can also choose which vote counters they want to rely from.

This would make the fediverse-powered link aggregator very flexible and minimal, imo. It may look janky but that's the general idea I have. ​:seija_coffee:​

RE: https://mementomori.social/users/owen/statuses/112285464236904945

fastfinge, to fediverse
@fastfinge@social.interfree.ca avatar

I don't use them, but just for fun, I decided to try and on . They both fail differently. First off, both require that you log out or authorization won't work. But if you log out then log in again while authorizing, they will. But at that point, will just crash. The error in the log says it's trying to do something with Pleroma that it doesn't implement. Tweesecake, on the other hand, pretends to work. It loads the messages and mentions buffers just fine. Then it adds exactly 160 items to the home buffer, all of them blank. If you leave it open, new items will stream into the home buffer. They, also, will be blank. I didn't expect either client to work; I just find the wildly differing failures amusing.

aldi80s, to Vivaldi
@aldi80s@mastodon.social avatar

I made the way to delete some cookies from then cdrom.tokyo came back.

Tried to make a post with a gif image in. Suddenly cracked down and got blank. Had to delete the cookies again. Just sent some text, took some seconds to post.

Why it takes too long time for a post?
Why it fails when I upload an gif?

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • tacticalgear
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • Durango
  • cubers
  • Youngstown
  • mdbf
  • slotface
  • rosin
  • ngwrru68w68
  • kavyap
  • GTA5RPClips
  • provamag3
  • ethstaker
  • InstantRegret
  • Leos
  • normalnudes
  • everett
  • khanakhh
  • osvaldo12
  • cisconetworking
  • modclub
  • anitta
  • tester
  • megavids
  • lostlight
  • All magazines