Fosstodon

0 posts0 participants0 posts today

OldCoderThread: Pleroma This is an exchange between the <a class="hashtag" href="https://dansu.org/tag/pleroma" rel="nofollow noopener noreferrer" target="_blank">#Pleroma</a> lead developer and myself related to <a class="hashtag" href="https://dansu.org/tag/rss" rel="nofollow noopener noreferrer" target="_blank">#RSS</a> support. ==== Date: July 13, 2024 09:19pm PT To: Pleroma developers Cc: Fossies Subject: Re: Possible Pleroma patch Jens, it might make sense to add Pleroma-BE aka Pleroma Backend to Fossies. Mark Felder, to whom this email is addressed, is one of the lead developers. Note: If you add Pleroma-FE aka Pleroma Frontend as well, the two codebases should be registered as separate projects. Mr. Felder, thanks for responding. 1. I looked at the existing approaches to RSS for Pleroma. It appeared that none would work presently. So, I wrote a new posting tool today. It's presently a single-file Perl script that uses XPath to parse RSS and/or Atom feeds and the Pleroma API to post individual items. GUIDs stored in small external DBs are used to prevent redundant posts. Posts are sorted in reverse chronological order. High-volume feeds are set to unlisted so as to avoid filling up the timelines. Note: That part is hardcoded on a per-feed basis and not autodetected. 2. I'm CC'g Dr. Jens Schleusener of Fossies. I wrote the tool in part because I thought that <a class="hashtag" href="https://dansu.org/tag/fossies" rel="nofollow noopener noreferrer" target="_blank">#Fossies</a> should have a <a class="hashtag" href="https://dansu.org/tag/fediverse" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a> presence. 3. I've compiled and run Pleroma since 2020 or 2021. It's formally a part of my Linux distro (Laclin). However, I hadn't learned Elixir until today. So, I may not be qualified to make significant changes for a while. However, the points quoted below are appreciated. 4. I'd like to encourage the Pleroma group to continue work despite the relatively small market share of the project. I ran Mastodon for a while before Pleroma and it was simply too heavy. I feel that Pleroma is an important alternative. Docker or Podman could be used to simplify setup for less technical would-be self-hosts. 5. I can't comment on Akkoma yet except to say that it might be in the interest of both groups to provide robust migration paths in both directions. Regards, Robert (the Old Coder) On 07/13/2024 08:18 PM, Mark Felder wrote: > > I had an RSS bot written in Python that I used for posting from a bot account and it was very useful, so RSS client functionality is interesting to me > > It might be cleanest to put the logic of whether or not to try backfilling in the Oban worker in lib/pleroma/workers. When it gets these jobs, just return :ok. The unique job constraint should prevent it from wasting resources. > > Another thought I have is to do it in the Card module where the caching logic lies and have it always put in a nil cache entry for these which will prevent it from trying to make any backfill jobs ==== Mr. Felder was responding to the following letter from me to the Pleroma group: Date: July 13, 2024 08:00pm PT To: Pleroma developers Subject: Possible Pleroma patch I'm not submitting this patch as a pull request because the change should probably be done differently. I've added RSS support to my Pleroma instance. In my view, RSS is a must-have feature. I've been looking forward to having Google News in my instance and it's working now. I've also added Fossies to support the developer of that project. However, if I set "ignore_hosts" in "prod.secret.exs" to include "news.google.com", the setting is ignored. The result is that I end up with numerous copies of the Google News panel. The existing "ignore_hosts" code is present and debug statements show that it runs. However, that code has no effect. The patch below fixes the problem for me. But how would you approach this fix? Note: If you'd like to see this change [and RSS] in action, the link is: <a href="https://dansu.org/@News" rel="nofollow noopener noreferrer" target="_blank">https://dansu.org/@News</a> By the way, I've been running Pleroma for 4 to 5 years. But I've only started to tweak my instance seriously this year. Regards, Robert (the Old Coder) --- pleroma-git.old/lib/pleroma/web/rich_media/card.ex +++ pleroma-git/lib/pleroma/web/rich_media/card.ex def get_by_url(url) when is_binary(url) do - if @config_impl.get([:rich_media, :enabled]) do + host = <a href="http://URI.parse(url).host" rel="nofollow noopener noreferrer" target="_blank">URI.parse(url).host</a> + if @config_impl.get([:rich_media, :enabled]) and +host not in @config_impl.get([:rich_media, :ignore_hosts], []) +do def get_or_backfill_by_url(url, opts \\ []) do - if @config_impl.get([:rich_media, :enabled]) do + host = <a href="http://URI.parse(url).host" rel="nofollow noopener noreferrer" target="_blank">URI.parse(url).host</a> + if @config_impl.get([:rich_media, :enabled]) and +host not in @config_impl.get([:rich_media, :ignore_hosts], []) +do (end of document)

Alexandre DulaunoyIf you are looking for nice gems in <a href="https://paperbay.org/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a>, there is the very old and the well maintained fossies.org website.🔗 <a href="https://fossies.org/" rel="nofollow noopener noreferrer" target="_blank">https://fossies.org/</a>maintained by Dr. Jens SchleusenerA great resource, easy to read and without a single bit of advertising.<a href="https://paperbay.org/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://paperbay.org/tags/directory" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#directory</a> <a href="https://paperbay.org/tags/software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#software</a> <a href="https://paperbay.org/tags/freesoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freesoftware</a> <a href="https://paperbay.org/tags/fossies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fossies</a>

tallshipDo you recall the recent socalled "unconference", FediForum?<a href="https://fediforum.org/about/" rel="nofollow noopener noreferrer" target="_blank">https://fediforum.org/about/</a>Charging money (not necessarily a bad thing) for an event that required <a href="https://social.sdf.org/tags/FOSSies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSSies</a> to install some kind of proprietory skin over <a href="https://social.sdf.org/tags/Zoom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Zoom</a> to attend, instead of <a href="https://social.sdf.org/tags/dogfooding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dogfooding</a> with <a href="https://social.sdf.org/tags/BBB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BBB</a>/Greenlight or alike - not a good look.Same folks: <a href="https://lists.w3.org/Archives/Public/public-swicg/2023Mar/0124.html" rel="nofollow noopener noreferrer" target="_blank">https://lists.w3.org/Archives/Public/public-swicg/2023Mar/0124.html</a>One noted only as a <a href="https://social.sdf.org/tags/CryptoBruh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CryptoBruh</a>, the others not <a href="https://social.sdf.org/tags/OG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OG</a> <a href="https://social.sdf.org/tags/fedizens" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedizens</a> either, now playing capture the flag with <a href="https://social.sdf.org/tags/eee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#eee</a>? WTF, Chuck? Your thoughts?<a href="https://social.sdf.org/tags/tallship" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tallship</a>⛵.

tallship@xpil <a href="https://fosstodon.org/tags/Dropbox" class="mention hashtag" rel="tag">#Dropbox</a>????Why not <a href="https://fosstodon.org/tags/NextCloud" class="mention hashtag" rel="tag">#NextCloud</a> (there are plenty of free instances) or <a href="https://fosstodon.org/tags/Syncthing" class="mention hashtag" rel="tag">#Syncthing</a> my friend?<a href="https://fosstodon.org/tags/FOSSies" class="mention hashtag" rel="tag">#FOSSies</a> should be <a href="https://fosstodon.org/tags/dogfooding" class="mention hashtag" rel="tag">#dogfooding</a>. You no can haz <a href="https://fosstodon.org/tags/Cheezburgerz" class="mention hashtag" rel="tag">#Cheezburgerz</a>? 🍔<a href="https://fosstodon.org/tags/tallship" class="mention hashtag" rel="tag">#tallship</a> <a href="https://fosstodon.org/tags/FOSS" class="mention hashtag" rel="tag">#FOSS</a> ⛵.

tallship<a href="https://mastodon.sdf.org/@toddpresta" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@toddpresta</a> <a href="https://techhub.social/@Techmeme" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Techmeme</a> No, this was actually taken by a guy who was with <a href="https://mastodon.sdf.org/tags/Linus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linus</a> when they left a <a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> convention in <a href="https://mastodon.sdf.org/tags/Japan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Japan</a> for lunch.Just to agitate us <a href="https://mastodon.sdf.org/tags/FOSSies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSSies</a>, good ole <a href="https://mastodon.sdf.org/tags/Redmond" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redmond</a> decided to schedule their public launch of <a href="https://mastodon.sdf.org/tags/Windows_7" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows_7</a> so that it coincided with the date of the convention, and set up a kiosk across from the convention center lolz.Someone joked about it with Linus and he promptly ran over to the kiosk so they could snap this pic of him in good humor.<a href="https://mastodon.sdf.org/tags/tallship" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tallship</a> <a href="https://mastodon.sdf.org/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> ⛵.

tallship<a class="u-url mention" href="https://freeradical.zone/@koherecoWatchdog" rel="nofollow noopener noreferrer" target="_blank">@koherecoWatchdog</a> <a class="u-url mention" href="https://hispagatos.space/@rek2" rel="nofollow noopener noreferrer" target="_blank">@rek2</a> Yes indeed, and I see nothing wrong, or perhpas, "little wrong", with those who insist in participating in that deprecated legacy silo merely posting exit links toward their primary Fediverse accounts. Giving people a roadmap to the newer, hipper, drive in diner is a good thing, right? I do believe that censorship at Twatter includes any posts to <a href="http://joinmastodon.com" rel="nofollow noopener noreferrer" target="_blank">joinmastodon.com</a> - according to <a class="u-url mention" href="https://mastodon.social/@Gargron" rel="nofollow noopener noreferrer" target="_blank">@Gargron</a> , IIRC. I could have that wrong, maybe he was citing a censor ban applied at Faceplant instead. With that, I think it's safe to assume that the powers that be in those deprecated, legacy monolithic silos are quite aware of, and perceive the Fediverse as a threat to their very existence. For that matter, They've got this whole blueskycommunity thing going on that more and more is becoming painfully cognizant that <a class="hashtag" href="https://pleroma.cloud/tag/p2p" rel="nofollow noopener noreferrer" target="_blank">#P2P</a>, <a class="hashtag" href="https://pleroma.cloud/tag/federating" rel="nofollow noopener noreferrer" target="_blank">#Federating</a>, and other <a class="hashtag" href="https://pleroma.cloud/tag/desoc" rel="nofollow noopener noreferrer" target="_blank">#DeSoc</a> technologies with truly <a class="hashtag" href="https://pleroma.cloud/tag/nomadic_identities" rel="nofollow noopener noreferrer" target="_blank">#nomadic_identities</a> are emerging faster than they'll ever be able to protect themselves against. I've heard some speak of the dangers of dilution, what with all of these various <a class="hashtag" href="https://pleroma.cloud/tag/decentralized" rel="nofollow noopener noreferrer" target="_blank">#decentralized</a> schemas now onboarding, but I tend to just think that these are merely "at the moment" items of concern that will be addressed in good time by the same cadre of innovative <a class="hashtag" href="https://pleroma.cloud/tag/fossies" rel="nofollow noopener noreferrer" target="_blank">#FOSSies</a> developing connector technologies and protocols to bridge the gaps between these free (as in beer OR freedom - I like both) networks :) The biggest problem we have, in all of this, is not technical capbilities, functionality, or stability, but rather, the same problem that lingered on for years in the "When is it going to be the year of Linux on the Desktop?" question - the allure to normies that beautification of UX offers... It's gotta be <a class="hashtag" href="https://pleroma.cloud/tag/pretty" rel="nofollow noopener noreferrer" target="_blank">#pretty</a>. There's no functionally sound reason for that (and it may not even have to be very good), but it does nevertheless have to be pretty in order to attract the masses. It's gotta be pretty ;) <a class="hashtag" href="https://pleroma.cloud/tag/tallship" rel="nofollow noopener noreferrer" target="_blank">#tallship</a> <a class="hashtag" href="https://pleroma.cloud/tag/vger" rel="nofollow noopener noreferrer" target="_blank">#Vger</a> <a class="hashtag" href="https://pleroma.cloud/tag/privacy" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> <a class="hashtag" href="https://pleroma.cloud/tag/portability" rel="nofollow noopener noreferrer" target="_blank">#portability</a> <a class="hashtag" href="https://pleroma.cloud/tag/sso" rel="nofollow noopener noreferrer" target="_blank">#SSO</a> <a class="hashtag" href="https://pleroma.cloud/tag/did" rel="nofollow noopener noreferrer" target="_blank">#DID</a> <a class="hashtag" href="https://pleroma.cloud/tag/foss" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> ⛵ . <a href="https://pleroma.cloud/media/7828c65b5187dbf1c9b5805f141cd0e807a6eb858bbd6ed97c44ed3bee9dc5e7.jpg?name=twitter_fail-002.jpg" class="" rel="nofollow noopener noreferrer" target="_blank">twitter_fail-002.jpg</a>

Recent searches

Search options

Administered by:

Server stats:

#fossies