[-] andrew_s@piefed.social 4 points 2 hours ago* (last edited 2 hours ago)

Nice. The thumbnail image reminded me of an Open Pandora, which similarly looked like a chunky DS and ran Linux (it was mostly intended for playing emulated games). The Pandora was never that repairable though, in the sense that it was mostly a system on a chip.

Before I even looked, I thought that I bet this device is more expensive than I'd assume - the crowdfunding site is listing prices roughly between $1000 and $1500.

[-] andrew_s@piefed.social 22 points 2 hours ago

It's an obscure skill, but once you've learned how to quickly sex doughnuts, there's money to be made from it.

[-] andrew_s@piefed.social 5 points 3 hours ago

PieFed has some design principles, including being accessible on lower-end devices and for those with unreliable bandwidth, which mean that it's default UI is never going to look like apps which involve downloading a sizable chunk of Typescript.

I'm okay with its look. Partly because it's themeable, and there's a theme called 'Card Shadow' which looks more modern imo. And partly because Lemmy can feel quite slow showing 20 posts at a time, whereas PieFed throws 100 at a time. And also because there will eventually be an API, allowing people to view it how they want (similar to Lemmy - lemmy-ui is maybe not that great, but there's other frontends which I think are an improvement)

[-] andrew_s@piefed.social 4 points 3 hours ago

That's a different Jerry! (Jerry Bell)

[-] andrew_s@piefed.social 2 points 9 hours ago

I'd probably mind less if I were younger. Those in the industry are not the only ones trying to "survive 'till '25" - I'm having to make healthier life choices just to make sure I get to see season 2 of Andor.

[-] andrew_s@piefed.social 5 points 10 hours ago

It's nothing like 15 minutes, but Lemmy doesn't federate posts instantly either. At a guess, there's a per-remote-instance worker that sleeps for a bit, then sends everything that's accumulated while it was sleeping. It's most noticeable when you're linked to only one other instance, and you still have to wait before getting anything. The advantages are that it's better to open a network connection, send a bunch of stuff, then close it, rather than opening and closing it for every activity, and it's more efficient to just send an Edit, rather than a Create and then an Edit if they both occurred close to one another.

For Threads, there's the additional advantage in that it means they can offer the equivalent of 'undo send' (like in Gmail), since deleting a non-federated post is easier and more reliable than deleting a federated one. But 15 minutes is crazy high - like the Source says, it makes a nonsense out of trying to do things like comment on a live event.

(In contrast to the above, PieFed will send this Note out instantly. It's all a trade-off between the pros and cons of different approaches, innit)

[-] andrew_s@piefed.social 6 points 1 day ago

He's posted before that Day 1 sales covered the cost the device itself, so a decent chuck of everything after that will have been pure profit. It was probably always doomed, what with YouTube being YouTube, so it doesn't look like he's too shaken up about it.

[-] andrew_s@piefed.social 9 points 1 day ago

All the links in this post already have that attribute, so I guess it's already added.

[-] andrew_s@piefed.social 5 points 1 day ago

HBO Max, for the brief period of time it existed, had a more fitting 'bumper'. Hacks, which started out as a 'Max Original' still had it in season 3, but The Penguin, which was a Max Original until it wasn't, has the fuzzy version (I've had players that struggle with it a bit, but I doubt HBO gives a shit about the quality of my experience pirating their stuff)

[-] andrew_s@piefed.social 54 points 5 days ago

One witness complained that the security was concerned about food and beverages being brought into the theater, but did not catch Loibl's guns.

Sounds about right.

Also, the issue of obsessive fans is currently being highlighted by the plight of Chappel Roan, who now seems uncomfortable with the level of fame that she'd previously strived for.

[-] andrew_s@piefed.social 19 points 6 days ago

Hello sorcerer. Please erase "Man, I feel like a woman" by Shania Twain. It annoys me anyway, but it not like it makes being a woman sound especially inspiring either ("Colour my hair, do what I dare" - woah, slow down there Shania!). Thanks.

[-] andrew_s@piefed.social 26 points 6 days ago

Germans no doubt have a single compound word for Annoyed-I-Am-Asked-To-Be.

26
17
submitted 3 months ago* (last edited 3 months ago) by andrew_s@piefed.social to c/star_wars@lemmy.world
221
349
Sad Train Station (files.mastodon.social)
1

There's more than one way to do this, of course. For group-based forums like piefed, I think the most promising way is to automatically create a local community for each person that someone wants to follow. Incoming activity is then put into the appropriate community, and so you have a consistent UI of UserA has posted to technology@wherever, and UserB has posted to [UserB's community]@piefed.social. This avoids the '2 websites in 1' look that can happen when a site wants to display both lemmy-like communities and mastodon-like microblogs.

I haven't done too much work on it, in case this idea gets shot down in flames. So far, what I've got is:

  1. A user searches for another remote user, e.g. @freamon@pixelfed.dk

  2. When they're found, the user is offered the opportunity to create a 'Follower Community' (for want of a better name. I've been using 'fan club', but that's maybe a bit naff)

  3. The community is created, formatted from the profile id, so [https://pixelfed.dk/users/freamon](https://pixelfed.dk/users/freamon) becomes [https://piefed.social/c/pixelfed_dk_users_freamon](https://piefed.social/c/pixelfed_dk_users_freamon)

  4. A follow request is sent to the remote user (from the user doing the search, or a dedicated bot account, maybe)

  5. Incoming activity will just be to activitystreams and followers, so there won't be any matches in 'to', 'cc' or 'audience'. In that case, 'attributedTo' is looked at, using the same conversion as above: so something from [https://pixelfed.dk/users/freamon](https://pixelfed.dk/users/freamon) will be sent to [https://piefed.social/c/pixelfed_dk_users_freamon](https://piefed.social/c/pixelfed_dk_users_freamon) if it already exists.

  6. The posts will show in the community like any other. Other users can then subscribe to the community in the normal way, and get updates whenever the remote actor publishes something for their followers.

  7. Posts from Mastodon would need another post-type to look their best (something that simulates how they look over there). Posts from Pixelfed already display well using Masonry:
    On pixelfed:

    On piefed:

  8. Post replies and upvotes (maybe) should make their way back to remote user, the same way they do if they'd actually made a post in a local community.

Random thoughts:
There would need to be an Undo Follow sent if the community was deleted.
A local community called c/pixelfed_dk_users_freamon looks a bit ungainly, but there's likely a way communities like this could be rendered as something like [SELF] in the homepage feed.
I realise pixelfed are planning to implement Groups, but that hasn't really worked out for mastodon, so we'll see how it goes. I think the ability to follow individuals will still be useful.
The remote user could be made a moderator for the local community, and it set to 'mod posts only' so it would only contain stuff from them.
This approach doesn't require any database changes.

I've just bashed this together for now - looking to get your thoughts before I continue ...

1
submitted 6 months ago* (last edited 6 months ago) by andrew_s@piefed.social to c/piefed_meta@piefed.social

Lemmy's spoiler format is

VISIBLE
HIDDEN 1
HIDDEN 2

As described here

The regex I've come up with is :{3} spoiler\s+?(\S.+?\n)(.+?)\n:{3}

It won't do spoilers inside spoilers, but that's a pretty niche case.

The changed code is viewable on GitHub

Any thoughts or suggestions for the regex before I create the PR?

I'm assuming that if I create a PR, and if they accept it, they'll (eventually) release a version with it in, and the line in pyfedi's requirements.txt can get version bumped. This seems like the 'proper' way to do it, but it's a bit long-winded, so maybe there's a better way to do it.

2

I've been thinking about what to do about cross-posts (e.g. where the same link is uploaded to both fediverse@lemmy.world and fediverse@lemmy.ml).

In terms of them being annoying, I don't yet know what to do about that.

My progress so far, and what it requires:
The Community table has an extra field (xp_indicator), for the field which determines if something is a cross-post or not. It defaults to URL, but it could be the title for communities like AskLemmy.
The Post table has an extra field (cross_posts), which is an array of other post ids (Note: this would lock PieFed into using Postgresql)
New posts, for local and ActivityPub, are checked to see if they are a cross-post, and the relevant posts are updated. This also happens for local edits and AP Update. In the DB, the posts in the screenshot looks like:

-[ RECORD 1 ]----------------------------------------------------------
id          | 27
title       | Springtime Ministrone
url         | https://www.bbcgoodfood.com/recipes/springtime-minestrone
cross_posts | {28,29,30}
-[ RECORD 2 ]----------------------------------------------------------
id          | 28
title       | Springtime Ministrone
url         | https://www.bbcgoodfood.com/recipes/springtime-minestrone
cross_posts | {27,29,30}
-[ RECORD 3 ]----------------------------------------------------------
id          | 29
title       | Springtime Ministrone
url         | https://www.bbcgoodfood.com/recipes/springtime-minestrone
cross_posts | {27,28,30}
-[ RECORD 4 ]----------------------------------------------------------
id          | 30
title       | Springtime Ministrone
url         | https://www.bbcgoodfood.com/recipes/springtime-minestrone
cross_posts | {27,28,29}

In the UI, posts with cross-posts get an extra icon, which when clicked bring you to another screen (similar to 'other discussions' in Reddit)

In terms of hiding duplicate posts from the feed, I don't yet know. If it was up to the back-end, it would require some extra DB activity that might be unacceptable speed-wise. This update would mean though, that a future API could provide a response similar to Lemmy for posts, so apps/frontends could merge duplicates the same way some of them do for Lemmy. Likewise, if there was a 'Hide posts marked as read' feature, it could regard any post ids in the cross_posts field as also being Read.

I have to wait a few days until the quota on my ngrok account resets (something in the Fediverse went crazy, I'd guess), so I thought I'd share here in the meantime. Also, it means the PR doesn't come out of the blue, and it can be discussed beforehand.

(also: it turns out I can't spell 'minestrone')

view more: next ›

andrew_s

joined 6 months ago
MODERATOR OF